Tighten kinit file permissions#63916
Merged
Merged
Conversation
The Kerberos kinit client for database access temporarily writes a certificate (and its key and corresponding CA) to a temporary directory with world-reabable (and writable) permissions. The permissions on the parent directory are correctly restricted to the current user only, so there is no exploit possible, this change just adds defense in depth by restricting the file permissions as well.
zmb3
added
backport
no-changelog
github-actions
Bot
added
database-access
Tener
approved these changes
Feb 18, 2026
gabrielcorado
approved these changes
Feb 18, 2026
public-teleport-github-review-bot
Bot
removed the request for review
from greedy52
Contributor
Collaborator
Author
Contributor
cthach
pushed a commit
that referenced
this pull request
Feb 20, 2026
The Kerberos kinit client for database access temporarily writes a certificate (and its key and corresponding CA) to a temporary directory with world-reabable (and writable) permissions. The permissions on the parent directory are correctly restricted to the current user only, so there is no exploit possible, this change just adds defense in depth by restricting the file permissions as well.
danielashare
pushed a commit
that referenced
this pull request
Feb 23, 2026
The Kerberos kinit client for database access temporarily writes a certificate (and its key and corresponding CA) to a temporary directory with world-reabable (and writable) permissions. The permissions on the parent directory are correctly restricted to the current user only, so there is no exploit possible, this change just adds defense in depth by restricting the file permissions as well.
mmcallister
pushed a commit
that referenced
this pull request
Apr 28, 2026
The Kerberos kinit client for database access temporarily writes a certificate (and its key and corresponding CA) to a temporary directory with world-reabable (and writable) permissions. The permissions on the parent directory are correctly restricted to the current user only, so there is no exploit possible, this change just adds defense in depth by restricting the file permissions as well.
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
3 participants
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.
The Kerberos kinit client for database access temporarily writes a certificate (and its key and corresponding CA) to a temporary directory with world-reabable (and writable) permissions.
The permissions on the parent directory are correctly restricted to the current user only, so there is no exploit possible, this change just adds defense in depth by restricting the file permissions as well.