gss_inquire_mech_for_saslname(3)
π gss_inquire_mech_for_saslname π
okay bestie, so this one lives in the gss manual (section 3, we love a library page β¨), and it's literally the glow-up moment where a SASL mechanism name gets matched up with its actual GSS-API mechanism OID. matchmaking, but make it Kerberos π
β¨ NAME β¨
gss_inquire_mech_for_saslname β an API function, periodt π
πΈ SYNOPSIS πΈ
#include <gss.h>
OM_uint32 gss_inquire_mech_for_saslname(OM_uint32 * minor_status, const
gss_buffer_t sasl_mech_name, gss_OID * mech_type);
likeβ¦ it's giving "three arguments, one function, zero drama" π
π¦ ARGUMENTS π¦
OM_uint32 * minor_statusβ (Integer, modify) the mechanism-specific status code. it comes back changed, so it's a little gossip channel for the mechanism itself π¬const gss_buffer_t sasl_mech_nameβ (buffer, character-string, read) a buffer holding the SASL mechanism name. read-only, we're just looking, not touching πgss_OID * mech_typeβ (OID, modify, optional) the actual mechanism used. and listen β the OID you get back through this parameter is a pointer to static storage, so treat it as read-only, bestie. do NOT try to free it. like, do not. specifyNULLif you don't need it, no pressure π«Ά
π DESCRIPTION π
outputs the GSS-API mechanism OID of the mechanism that's associated with the given sasl_mech_name. that's it. that's the whole vibe β
π₯ RETURNS π₯
GSS_S_COMPLETEβ successful completion. we ate, no crumbs π β¨GSS_S_BAD_MECHβ there is no GSS-API mechanism known assasl_mech_name. it's giving "who is she? never heard of her" π
π REPORTING BUGS π
report bugs to <bug-gss@gnu.org>.
GNU Generic Security Service home page: http://www.gnu.org/software/gss/
General help using GNU software: http://www.gnu.org/gethelp/
ngl if you found a bug, tell them, they wanna know fr fr π
π COPYRIGHT π
Copyright Β© 2003-2022 Simon Josefsson.
Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved.
(translation: go off, share it, just keep the receipts π§Ύ)
π SEE ALSO π
The full documentation for gss is maintained as a Texinfo manual. If the info and gss programs are properly installed at your site, the command
info gss
should give you access to the complete manual. like, the whole lore drop π
and that's the page, bestie π«Ά this was the gss manual, version 1.0.4, page gss_inquire_mech_for_saslname(3) β main character energy, static storage, and absolutely no freeing of OIDs. mwah πβ¨
π¦ where this page comes from
- alpine 3.24: libgss-doc 1.0.4-r2 Β· ( LGPL-3.0-or-later OR GPL-2.0-or-later ) AND GPL-3.0-or-later
- debian bookworm: gss-man 1.0.4-1+deb12u2 Β· GPL-3.0-or-later
- debian trixie: gss-man 1.0.4-4 Β· GPL-3.0-or-later
- ubuntu noble: gss-man 1.0.4-1build2 Β· GPL-3.0-or-later
- ubuntu questing: gss-man 1.0.4-4
- ubuntu resolute: gss-man 1.0.4-4build1 Β· GPL-3.0-or-later
- ubuntu stonking: gss-man 1.0.4-5 Β· GPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms