rpc.svcgssd(8)

πŸ“¦
version 2.9.1 Β· 2 versions
  • 2.9.1 Β· alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 2.6.1 Β· ubuntu jammy
, in alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– rpc.svcgssd β€” the server-side rpcsec_gss daemon πŸ’–

okay bestie so this is rpc.svcgssd(8), and it lives in the System Manager's Manual section (section 8, the big-girl system admin section, we love her). she's a daemon, she's got main character energy, and she handles the security vibes for you. let's get into it. ✨


🌸 NAME 🌸

rpc.svcgssd β€” server-side rpcsec_gss daemon πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

rpc.svcgssd [-n] [-v] [-r] [-i] [-f] [-p principal]

that's it. that's the whole vibe check. πŸ¦‹


✨ DESCRIPTION ✨

okay so first of all, the rpcsec_gss protocol? it gives you a way to use the gss-api generic security api to provide security for protocols that use rpc β€” and yes, especially nfs, the girlies know. 🫢

but here's the thing: before any rpc requests can be exchanged using rpcsec_gss, the rpc client has to first establish a security context with the rpc server. like, you gotta introduce yourself before you start talking, that's just manners. πŸ’–

and the linux kernel's implementation of rpcsec_gss? she cannot do it alone. she depends on the userspace daemon rpc.svcgssd to handle that context establishment on the rpc server side. iconic teamwork, no cap. πŸ‘‘

the daemon communicates with the kernel using files in the proc filesystem. that's the gossip channel, iykyk. πŸ“βœ¨


🌈 OPTIONS 🌈

  • -f β€” runs rpc.svcgssd in the foreground and sends output to stderr instead of to syslogd. staying in the front like a main character. πŸ’…
  • -v β€” increases the verbosity of the output. and yes, you can specify it multiple times β€” stack it, queen. πŸ“ˆ
  • -r β€” if the rpcsec_gss library supports setting debug level, this increases the verbosity of the output. also specifiable multiple times. πŸŽ€
  • -i β€” if the nfsidmap library supports setting debug level, this increases the verbosity of the output. you guessed it: specifiable multiple times. 🌸
  • -p β€” use principal instead of the default nfs/FQDN@REALM. custom name, custom energy. ✨
  • -n β€” use the system default credentials (host/FQDN@REALM) rather than the default nfs/FQDN@REALM. sometimes you just gotta show up as yourself. πŸ’–

πŸ¦‹ CONFIGURATION FILE πŸ¦‹

some of the options you can slap on the command line can also be controlled through values set in the [svcgssd] section of the /etc/nfs.conf configuration file. it's giving options-on-options. the values recognized include:

  • principal β€” if set to system this is equivalent to the -n option. if set to any other value, that value is used like the -p option.
  • verbosity β€” value which is equivalent to the number of -v.
  • rpc-verbosity β€” value which is equivalent to the number of -r.
  • idmap-verbosity β€” value which is equivalent to the number of -i.

so you can either yell your flags at the terminal or whisper them into a config file. both are valid. πŸ™ˆ


πŸ’œ SEE ALSO πŸ’œ

rpc.gssd(8), β€” yes there's a trailing comma, she came that way, we respect her. πŸ’…


πŸ‘‘ AUTHORS πŸ‘‘

the literal legends who built this:

  • Dug Song <dugsong@umich.edu>
  • Andy Adamson <andros@umich.edu>
  • Marius Aamodt Eriksen <marius@umich.edu>
  • J. Bruce Fields <bfields@umich.edu>

ate and left no crumbs, fr fr. πŸ”₯


bestie reminder: this is from the System Manager's Manual, dated 12 Jan 2007. old money, timeless slay. πŸŽ€

and that's the whole page, mwah πŸ’‹ go establish some security contexts responsibly, ily, bye! πŸ¦‹βœ¨πŸ’–