GSS-Proxy configuration file for mod_auth_gssapi #81
Conversation
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
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.
For packaging purposes, it makes sense for mod_auth_gssapi to provide its own gssproxy configuration file. This way, gssproxy avoids being in a situation where a user mentioned in the config file may not exist.
On a related note, this will not work on Debian because Debian calls its apache user "www-data". (It also has a different UID than Fedora's - 33 vs. 48.) We could make it work with autoconf magic, but I'm not sure whether that's worth the effort.