MUNGE(1)
π MUNGE β the MUNGE credential encoder, bestie edition π
okay so welcome to the munge(1) manual page, from the MUNGE Uid 'N' Gid Emporium (yes that's literally what it's called, iconic name, no notes) π
β¨ NAME β¨
munge β the MUNGE credential encoder π
πΈ SYNOPSIS πΈ
munge [OPTION]...
π¦ DESCRIPTION π¦
So here's the vibe, bestie: the munge program creates an MUNGE credential that contains the UID and GID of the calling process. That's the whole point of it, that's its main character energy. π«Ά
And because that's not enough slay, you can also encapsulate additional payload data (up to 1 MB) in there as well. Then you can pass that returned credential to another process, and that process can validate its contents (like, for example, via the unmunge program β¨). Which means an unrelated and potentially remote process can figure out the identity of the calling process. fr fr, that's the whole trick.
By default, payload input is read from stdin and the credential is written to stdout. Defaults, we love them. π
π OPTIONS π
-h,--helpβ shows you a summary of the command-line options. ur lil cheat sheet π-L,--licenseβ displays license information π-V,--versionβ displays version information β-n,--no-inputβ discards all input for the payload. bye bye payload π-s,--stringstring β takes the input payload from the specified string π-i,--inputpath β takes the input payload from the specified file π-o,--outputpath β writes the credential out to the specified file πΎ-c,--cipherstring β specify the cipher type, either by name or by number π-C,--list-ciphersβ displays a list of supported cipher types π-m,--macstring β specify the MAC type, either by name or by number ποΈ-M,--list-macsβ displays a list of supported MAC types π-z,--zipstring β specify the compression type, either by name or by number ποΈ-Z,--list-zipsβ displays a list of supported compression types π-u,--restrict-uiduid β specify the user name or UID that's allowed to decode the credential. This gets matched against the effective user ID of the process requesting the credential decode π-U,--uiduid β specify the user name or UID under which to request the credential. This requires root privileges or theCAP_SETUIDcapability. so like, powerful, respect it π-g,--restrict-gidgid β specify the group name or GID that's allowed to decode the credential. This gets matched against the effective group ID of the process requesting the credential decode, AND against each supplementary group of which the effective user ID of that process is a member. yes, all of them π«Ά-G,--gidgid β specify the group name or GID under which to request the credential. This requires root privileges or theCAP_SETGIDcapability π-t,--ttlseconds β specify the time-to-live, in seconds. This controls how long the credential stays valid once it has been encoded β³ A value of0selects the default TTL. A value of-1selects the maximum allowed TTL. And heads up bestie:mungedcan impose a maximum allowable TTL for all credentials which may be smaller than this value. so like, don't get too attached to ur number π-S,--socketpath β specify the local socket for connecting withmungedπ
π EXIT STATUS π
The munge program returns a zero exit code when the credential is successfully created and returned. π
On error, it prints an error message to stderr and returns a non-zero exit code. that's the sad path, we don't talk about it π
π§ AUTHOR π§
Chris Dunlap <cdunlap@llnl.gov> π
π COPYRIGHT π
Copyright (C) 2007-2025 Lawrence Livermore National Security, LLC. Copyright (C) 2002-2007 The Regents of the University of California.
MUNGE is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
Additionally for the MUNGE library (libmunge), you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
yes the licensing section is long and yes you should still read it, it's giving responsible queen π
π«Ά SEE ALSO π«Ά
remunge(1), unmunge(1), munge(3), munge_ctx(3), munge_enum(3), munge(7), munged(8), mungekey(8).
and that's the page, bestie!! πβ¨ this was munge-0.5.18, dated 2026-02-10, and it's the MUNGE(1) page β go forth and encode some credentials, u absolute icon ππ
π¦ where this page comes from
- arch rolling: munge 0.5.18-2 Β· GPL-3.0-or-later AND LGPL-3.0-or-later
- fedora 43: munge 0.5.18-1.fc43 Β· GPL-3.0-or-later AND LGPL-3.0-or-later
- fedora 44: munge 0.5.18-1.fc44 Β· GPL-3.0-or-later AND LGPL-3.0-or-later
- nixpkgs unstable: munge 0.5.18
- Copyright (C) 2007-2025 Lawrence Livermore National Security, LLC
- Copyright (C) 2002-2007 The Regents of the University of California
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms