Repository navigation
Restrict config file permissions - #1045
Merged
Merged
Conversation
graygilmore
approved these changes
Sep 23, 2026
EvilGenius13
approved these changes
Sep 24, 2026
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.
Summary
Addresses internal Vault issue #80288, which reported that Theme Kit creates password-bearing config files that can be read by other local users.
Config files can contain theme passwords, but newly created files were opened with
0644permissions. This changes the create mode to0600so new config files are only readable and writable by the owner.Security impact
This fixes a local file-permissions vulnerability for newly created config files. Existing config files are not modified by this change.
Testing
go test ./src/env/go test ./...