Add krb5_keytab for specifying a Kerberos client keytab - #74
Draft
grawity wants to merge 1 commit into
Draft
Conversation
Current MIT Kerberos versions support automatically obtaining client tickets from a keytab without the need for external kinit/k5start.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Current MIT Kerberos versions support automatically obtaining client tickets from a keytab without the need for external
kinit/k5start. Unfortunately nslcd prevents this by clearing its environment, and setting the keytab globally via krb5.conf is not always desirable.It would be great if nslcd could be configured to preserve certain environment variables (also for #40), but I went for the simpler option of only setting the specific envvar.
Since the goal here was to let libkrb5 handle everything, I didn't go as far as implementing the "manual" kinit-like ticket acquisition via krb5_init_creds_set_keytab(). Not sure if that's useful.