Repository navigation
SPS security hardening - #11
Merged
Merged
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.
Security hardening for SPS (Secrets Procurement Service).
What changes
[grants]entry in the SPS config. Registrations are audited with hashed field/item and entry counts.repr;vault-set/vault-gethonour the passphrase file; written values are capped (64 KiB default, configurable); non-loopback binds need an explicit flag; new vaults use a stronger KDF (existing vaults unchanged); longer self-signed certificate validity with an expiry warning; the tool SDK refuses the fake path when a real tool credential is present.Upgrade notes