SASLPLUGINVIEWER(8)

πŸ“¦
version 2.1.28 Β· 2 versions
  • 2.1.28 Β· debian bookworm, debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 2.1.27 Β· ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’… SASLPLUGINVIEWER β€” bestie edition πŸ’…

okay so real talk: this is saslpluginviewer from the System Manager's Manual section (that's section 8, iykyk β€” admin tools only, no casuals). she's the one you call when your SASL setup is acting up and you need to figure out what's actually loadable. πŸ¦‹


✨ NAME ✨

saslpluginviewer β€” list loadable SASL plugins and their properties πŸ’–

like literally just… shows you the plugins. that's the whole job. and she eats. πŸ‘‘


🌸 SYNOPSIS 🌸

pluginviewer [-a] [-s] [-c] [-b min=N,max=N] [-e ssf=N,id=ID] [-m MECHS]
[-x AUXPROP_MECH] [-f FLAGS] [-p PATH]

(and yes, she answers to both saslpluginviewer and pluginviewer β€” same girl, different name tag ✨)


πŸŽ€ DESCRIPTION πŸŽ€

okay so saslpluginviewer is your troubleshooting bestie if you're a server administrator and your SASL installation is giving… unclear energy. 😭

she can list the loadable plugins β€” meaning the ones that are properly configured, no half-set-up nonsense here β€” on both the client side and the server side, plus she can pull up the auxprop plugins too. three whole friend groups. slay. πŸ’…


⭐ OPTIONS ⭐

  • -a β€” list auxprop plugins. the auxprop girlies get their moment. 🫢
  • -s β€” list server authentication (SASL) plugins. server side representation fr fr. πŸ”₯
  • -c β€” list client authentication (SASL) plugins. client side, also iconic. ✨
  • -b min=N1,max=N2 β€” list client authentication (SASL) plugins. this one's about the strength of the SASL security layer, in bits. min=N1 says what the minimum strength you'll accept is (and lowkey 1 means integrity protection, that's the floor bestie). max=N2 says the maximum strength you'll use. so basically: only SASL mechanisms that support a security layer with strength M where N1 <= M <= N2 will show up. everyone else? not invited. πŸ’€
  • -e ssf=N,id=ID β€” assume an external security layer (like TLS, you know her) is installed with N-bit strength. the ID is the authentication identity that the external security layer is using. so you're telling her "hey, there's already a security layer here, factor that in". 🌈
  • -m MECHS β€” limit the listed SASL plugins to only the ones in the MECHS list (that's a space separated list, mind you, not commas, don't embarrass yourself πŸ™ˆ).
  • -x AUXPROP_MECHS β€” limit the listed auxprop plugins to the one listed in the AUXPROP_MECHS list (again, space separated). yes the original says "the one" singular, we're keeping it exactly as she is, no notes. πŸ’œ
  • -f FLAGS β€” set security flags. FLAGS is a comma separated list of one or more of these security flags:
    • noplain β€” SASL mechanism doesn't send the password in the clear during authentication 🚫
    • noactive β€” require protection from active attacks πŸ›‘οΈ
    • nodict β€” require mechanisms that are secure against passive dictionary attacks πŸ“–
    • forwardsec β€” require forward secrecy πŸ”
    • passcred β€” require mechanisms that can delegate client credentials 🎫
    • maximum β€” require all the security flags. all of them. the whole buffet. πŸ‘‘
  • -p PATH β€” specifies a colon-separated search path for plugins. where she should go looking. 🧚

πŸ” SEE ALSO πŸ”

  • rfc4422 β€” Simple Authentication and Security Layer (SASL)

(the source material, the blueprint, the origin story ✨)


πŸ’– quick vibe check: every flag here is doing real work, so don't just mash them all together and hope for the best. -b and -e are the ones that actually change what gets filtered, so read those carefully bestie.

CMU SASL Β· Apr 10, 2006

that's the whole page, bestie β€” go forth and troubleshoot, you've absolutely got this. slay πŸ’…βœ¨