Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Kerberos V5 (GSSAPI) #13

Open
emersion opened this issue Aug 14, 2019 · 3 comments
Open

Implement Kerberos V5 (GSSAPI) #13

emersion opened this issue Aug 14, 2019 · 3 comments

Comments

@emersion
Copy link
Owner

See https://tools.ietf.org/html/rfc4752

@simo5
Copy link

simo5 commented Dec 11, 2020

If you ever want to implement this I suggest you do it via bindings to libgssapi.so (dynamically load if present, if not present your user is definitely not using kerberos on their machine anyway).

@emersion
Copy link
Owner Author

emersion commented Dec 11, 2020

I'd rather not. I'd prefer to just provide the wire marshalling, define an interface, and letting users implement it with whatever kerberos lib they want.

@simo5
Copy link

simo5 commented Dec 11, 2020

Well on the wire there isn't much going, the meat of the SASL/GSSAPI mechanism is in calling gss_init_sec_context() repeatedly and shuffling along the binary blobs you get back. But as long as there is no intention of implementing kerberos or gssapi here all is good :-)

Just note that there are basically there "gssapi" SASL protocols that are used:
GSSAPI (traditionally on unix like systems)
GSS-SPNEGO (very similar to GSSAPI but used for compatibility with Microsoft systems)
and the new GS2 mechanism that doesn't have wide usage as far as I know.

GSSAPI and GSS-SPNEGO are very close and can share most of the machinery, they are implemented in the same plugin in cyrus-sasl for example.

HTH.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants