mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-08-16 11:37:04 +02:00
Code Issues Projects Releases Wiki Activity

Clarify that backend authors can specify that all or no values are sealwrapped (#13813)

Browse Source 
* Clarify that backend authors can specify that all or no values are sealwrapped rather than the vague statement that all values _may_ be seal wrapped

* typo
This commit is contained in:
Scott Miller 2022-01-27 15:30:55 -06:00 committed by GitHub
parent 06137630b9
commit d783db1667
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/docs/enterprise/sealwrap.mdx
View File

@ -74,8 +74,8 @@ backend with the `seal_wrap` configuration value set to `true`. (This value
cannot currently be changed later.) cannot currently be changed later.)
A given backend's author can specify which values should be seal-wrapped by A given backend's author can specify which values should be seal-wrapped by
identifying where CSPs are stored. If no specific CSPs are identifiable, all identifying where CSPs are stored. They may also choose to seal wrap all or none
data for the backend may be seal-wrapped. of their values.
To see the current list of seal-wrapped data per backend type, see the latest To see the current list of seal-wrapped data per backend type, see the latest
audit letter and updates in the FIPS 140-2 Compliance section above. audit letter and updates in the FIPS 140-2 Compliance section above.