GSSPROXY(8)
β¨ GSSPROXY(8) β gssproxy, the GssProxy Daemon β¨
okay bestie, buckle up, we're looking at a page from the GssProxy Manual pages and it's genuinely so good π
πΈ NAME πΈ
gssproxy β the GssProxy Daemon, aka the little guy holding all your GSSAPI credentials together π
π¦ SYNOPSIS π¦
gssproxy [options]
like, that's it. that's the whole vibe. no cap.
π DESCRIPTION π
so gssproxy hands you a daemon whose entire job is managing access to GSSAPI credentials. it's giving gatekeeper, but in a helpful way π«Ά
and here's the thing β gssproxy is actually a two-piece set (iconic duo behavior, fr fr):
- the
gssproxydaemon itself, which gets configured by thegssproxy.conf(5)file - a GSSAPI interposer plugin, and that one's
gssproxy-mech(8)
both. at the same time. matching outfits. π
π OPTIONS π
this is the main character section, let's go:
-D,--daemonβ become a daemon after starting up. like, it does the work first and then commits to the daemon lifestyle β¨-c,--configβ point at a specific config file to use as the main config file (it gets read before the rest of the config directory). the default is to use/etc/gssproxy/gssproxy.conf. want the tea on config file syntax and options? consult thegssproxy.conf(5)manual page π-C,--configdirβ pick a non-default config dir. files named like"##-foo.conf"(so: starting with two digits and a dash, and ending in.conf) get read in numeric order from this directory, plus the config file itself. the default is/etc/gssproxy. and again, for the deets on config file syntax and options, go read thegssproxy.conf(5)manual page π-d,--debugβ turn on debugging. literally identical to--debug-level=1π--debug-level=β turn on debugging at whatever level you specify:0= no logging at all (silence, a vibe)1= basic debug logging2= more verbosity, including more detailed credential verification π3and above =KRB5_TRACEoutput gets logged. but ifKRB5_TRACEwas already set in the execution environment, then the trace output goes to its value instead. sneaky, ik
-i,--interactiveβ run in the foreground, do not become a daemon. it's staying right here with you π-u,--userproxyβ rungssproxyin userproxy mode. this mode ignores configuration files entirely and listens on a socket at$XDG_RUNTIME_DIR/gssproxy/default.sockinstead. want the full lore on how this mode behaves? it's in the project documentation π¦-s,--socketβ set a custom default socket name. this socket gets used by all sections that don't define an explicit socket of their own π₯--syslog-statusβ enable extra logging to syslog β¨--versionβ print the version number and exit. bye π
π SIGNALS π
SIGTERM/SIGINTβ tells GssProxy to gracefully terminate all of its child processes and then shut down. calm, polite, no mess π«ΆSIGHUPβ request a reload of all configuration forgssproxy. and bestie, listen: if there's an error in the config files, the existing configuration does not get replaced. but if there's a problem applying the new configuration,gssproxywill exit. so like, be careful π
π SEE ALSO π
gssproxy.conf(5) and gssproxy-mech(8). go read your siblings, iykyk π
β AUTHORS β
GSS-Proxy β https://github.com/gssapi/gssproxy
periodt. that's the whole page, no notes π
and a cute little sign-off for the end: this one came from GSS Proxy, dated 11/01/2026, and it's filed right under GSSPROXY(8) πΈβ¨
π¦ where this page comes from
- arch rolling: gssproxy 0.9.3-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms