Support clients running in AT_SECURE context#129
Merged
Conversation
When a client application runs in a secure execution context (e.g., setuid, where getauxval(AT_SECURE) is non-zero), environment variables like GSSPROXY_SOCKET are ignored to prevent security issues. This change allows these clients to work by automatically constructing a program-specific socket name (e.g., <default_socket>.<program_name>) when AT_SECURE is detected. The mechanism interposer now checks if this socket is accessible to decide whether to enable gssproxy. Documentation is updated to guide users on configuring the service for this specific socket. Assisted-by: Gemini <gemini@google.com> Signed-off-by: Simo Sorce <simo@redhat.com>
Member
Author
|
Tested by reported and confirmed working, so ... merging. |
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.
When a client application runs in a secure execution context (e.g., setuid, where getauxval(AT_SECURE) is non-zero), environment variables like GSSPROXY_SOCKET are ignored to prevent security issues.
This change allows these clients to work by automatically constructing a program-specific socket name (e.g., <default_socket>.<program_name>) when AT_SECURE is detected. The mechanism interposer now checks if this socket is accessible to decide whether to enable gssproxy. Documentation is updated to guide users on configuring the service for this specific socket.
Fixes: #127