MECH(5)

πŸ“¦
version 7.8.0 Β· 2 versions
  • 7.8.0 Β· alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, epel 10, epel 9, fedora 43, fedora 44, nixpkgs unstable, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 14.5 Β· freebsd 14.5
, in alpine 3.22, alpine 3.23, alpine 3.24, debian bookworm, debian trixie, epel 10, epel 9, fedora 43, fedora 44, nixpkgs unstable, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– MECH(5) β€” the file formats page, but make it cute πŸ’–

okay bestie, pull up a chair πŸŽ€ this is the File Formats Manual entry for mech and qop β€” the two little config files that tell your system which GSS-API security mechanisms and Quality of Protection values it's got installed. lowkey iconic, highkey essential, fr fr. ✨


🌸 NAME 🌸

mech, qop β€” GSS-API Mechanism and QOP files πŸ¦‹


✨ SYNOPSIS ✨

/etc/gss/mech /etc/gss/qop

two files, two vibes, one directory. πŸ’…


πŸ’œ DESCRIPTION πŸ’œ

🫢 the /etc/gss/mech file

The /etc/gss/mech file holds a whole list of the GSS-API security mechanisms that are installed on your system. every line is either:

  • a comment β€” and it's a comment if the very first character is '#', no debate, that's the rule πŸ’€
  • or a real entry with five fields, and here's what they mean:
  • Name β€” the name of this GSS-API mechanism. just its name, that's it. 🌸
  • Object identifier β€” the OID for this mechanism. yes, the long dotted number situation. πŸ”’
  • Library β€” a shared library containing the implementation of this mechanism. πŸ“š
  • Kernel module (optional) β€” a kernel module containing the implementation of this mechanism. ⚠️ heads up: not yet supported in FreeBSD. so if you're on FreeBSD, this field is giving "reserved for later" energy. 🫠
  • Library options (optional) β€” optional parameters interpreted by the mechanism. πŸŽ€ important detail: library options must be enclosed in brackets ([ ]) so they don't get confused with the optional kernel module entry. like, they literally need the bracket outfit to be recognisable. πŸ‘‘

🧚 the /etc/gss/qop file

The /etc/gss/qop file is a list of Quality of Protection values for use with GSS-API. same deal as before β€” each line is either:

  • a comment if the first character is '#' πŸ’…
  • or an entry with three fields:
  • QOP string β€” the name of this Quality of Protection algorithm. πŸ“
  • QOP value β€” the numeric value used to select this algorithm for use with GSS-API functions such as gss_get_mic(3). πŸ”₯
  • Mechanism name β€” the GSS-API mechanism name that corresponds to this algorithm. 🌈

🌟 EXAMPLES 🌟

here's a typical entry from /etc/gss/mech β€” look at it, it's so tidy:

kerberosv5      1.2.840.113554.1.2.2    /usr/lib/libgssapi_krb5.so.8    -

and here's a typical entry from /etc/gss/qop:

GSS_KRB5_CONF_C_QOP_DES         0x0100  kerberosv5

ate. no crumbs. πŸ‘‘


πŸ“œ HISTORY πŸ“œ

the mech manual page example first appeared in FreeBSD 7.0. a lil legend from way back. 🫢


πŸ’Œ AUTHORS πŸ’Œ

this manual page was written by Doug Rabson <dfr@FreeBSD.org>. thank you for your service, king. πŸŽ€


and that's the whole page, bestie!! this came from the Debian flavour of things, dated November 14, 2005 β€” yes, old enough to be a vintage icon, and it still eats. πŸ’…βœ¨ πŸ¦‹ mwah, go configure responsibly. πŸ’–

πŸ“¦ where this page comes from