luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Fixed minor typo in secrets documentation page (#8856)

This commit is contained in:
Rob Taylor 2020-06-08 16:17:26 +01:00 committed by GitHub
parent 61e795c5e2
commit 76e78605a9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/pages/docs/secrets/index.mdx
View File

@ -65,7 +65,7 @@ storage. This is a lot like a [chroot](https://en.wikipedia.org/wiki/Chroot).
When a secrets engine is enabled, a random UUID is generated. This becomes the When a secrets engine is enabled, a random UUID is generated. This becomes the
data root for that engine. Whenever that engine writes to the physical storage data root for that engine. Whenever that engine writes to the physical storage
layer, it is prefixed with that UUID folder. Since the Vault storage layer layer, it is prefixed with that UUID folder. Since the Vault storage layer
doesn't support relative access (such as `../`), this makes it impossible for a doesn't support relative access (such as `../`), this makes it impossible for an
enabled secrets engine to access other data. enabled secrets engine to access other data.
This is an important security feature in Vault - even a malicious engine This is an important security feature in Vault - even a malicious engine