GSSNTLMSSP(8)

✨ GSSNTLMSSP ✨

okay bestie, gather round, because this is the manual page for gssntlmssp β€” the GSSAPI NTLM Security Service Provider mechanism πŸ’…


🌸 SYNOPSIS 🌸

gssntlmssp_v1 2.16.840.1.113730.3.8.15.X
                                                                                     /usr/lib64/gssntlmssp/gssntlmssp.so
                                                                                     [options]

yes the spacing is unhinged, no I did not do that, it's literally how it ships 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

So like, gssntlmssp is a GSSAPI NTLM mechanism β€” and what that means, bestie, is it lets you do NTLM authentication from inside GSSAPI programs. That's it, that's the whole vibe. It slots in, it authenticates, it slays. ✨


πŸŽ€ ENVIRONMENT VARIABLES πŸŽ€

not me about to list every single one of these in order, because we do not skip, we do not summarise, we are thorough πŸ‘‘

  • NTLM_USER_FILE β€” a file that holds users and their password hashes. The formats it accepts are the one Heimdal uses for its NTLM backend, and the samba password file format. Two formats, both iconic πŸ’–
  • NETBIOS_COMPUTER_NAME β€” sets the NETBIOS (that's the short) Computer name that goes into the NTLM packets πŸ“¦
  • NETBIOS_DOMAIN_NAME β€” sets the NETBIOS (again, short) Domain name used in the NTLM packets 🏰
  • NTLMUSER β€” sets the NTLM User name used for authentication when the security context gets initiated 🫑
  • USER β€” the default source for the User name used on initiation of the security context. (yes, plain USER, she's lowkey famous) πŸ‘‘
  • LM_COMPAT_LEVEL β€” the LM Compatibility Level that gets enforced during security context negotiation. Default level is 3 ⭐
  • GSSNTLMSSP_DEBUG β€” the name of a file to send debug logs to. Give her a filename and she'll spill everything πŸ“πŸ’€
  • GSSNTLMSSP_WB_TLS_CTX β€” okay this one is the wordiest, stay with me. This variable controls whether thread local contexts are used for winbindd communication, or whether a single process context is used instead. Setting the value to 0 disables per-thread contexts. And why would you do that? Because creating Winbindd contexts is an expensive operation, so this doubles as an optimization for applications that can insure a single thread is used, or that already handle their own locking. Default behavior is to create a context for each thread β€” and you can restore that default by setting the environment variable back to the value 1. Yes. 0 off, 1 on. We love a binary 🧚

🌈 SEE ALSO 🌈

gssapi(8).

(one friend, but she's a good one πŸ’œ)


πŸ’œ AUTHORS πŸ’œ

GSS-NTLMSSP β€” http://ssimo.org/gss-ntlmssp


lowkey a public service announcement: this is the GSSAPI NTLM mechanism manual p situation, brought to you by GSS-NTLMSSP, dated 07/24/2025, and filed under GSSNTLMSSP(8). periodt. πŸ’…βœ¨
πŸ“¦ where this page comes from