Backport of Vault 3992 ToB Config and Plugins Permissions into release/1.10.x #14881
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.
Backport
This PR is auto-generated from #14817 to be assessed for backporting due to the inclusion of the label backport/1.10.x.
The below text is copied from the body of the original PR.
Jira : https://hashicorp.atlassian.net/browse/VAULT-3992
Approved PR on Ent: https://github.com/hashicorp/vault-enterprise/pull/2524
Check the permissions (no write permissions for others or groups)and user (owner must be the vault process owner)of the config dir, config file, plugin directory and plugin binaries
This check is done while loading config (check config dir (and files in it ) / config file depending on the input to -config and plugin directory mentioned in the config file)
During plugin register and plugin enable, check plugin dir and plugin binary
This behavior can be disabled using an env variable VAULT_DISABLE_FILE_PERMISSIONS_CHECK (true to disable the check)
Can set uid for plugin files/directory by specifying -plugin_file_uid in config file
Can set permissions for plugin files/directory by specifying -plugin_file_permissions in config file