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

Fix some broken links

Browse source
This commit is contained in:
Jeff Mitchell 2017-11-14 12:26:58 -05:00
parent fc9525c727
commit 40e3883788
5 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
website/source/docs/configuration/index.html.md
View file

@ -59,7 +59,7 @@ to specify where the configuration is.
Vault is listening for API requests.
- `seal` <tt>([Seal][seal]: nil)</tt> – Configures the seal type to use for
[seal wrapping][sealwrapping] as an additional layer of data protection.
[seal wrapping][sealwrap] as an additional layer of data protection.
- `cache_size` `(string: "32000")` – Specifies the size of the read cache used
by the physical storage subsystem. The value is in number of entries, so the
@ -136,6 +136,6 @@ The following parameters are used on backends that support [high availability][h
[storage-backend]: /docs/configuration/storage/index.html
[listener]: /docs/configuration/listener/index.html
[seal]: /docs/configuration/seal/index.html
[sealwrapping]: /docs/enterprise/sealwrapping/index.html
[sealwrap]: /docs/enterprise/sealwrap/index.html
[telemetry]: /docs/configuration/telemetry.html
[high-availability]: /docs/concepts/ha.html

4
website/source/docs/configuration/seal/index.html.md
View file

@ -14,7 +14,7 @@ master key. This stanza is optional, and in the case of the master key, Vault
will use the Shamir algorithm to cryptographically split the master key if this
is not configured.
As of Vault 0.9.0, the seal can also be used for [seal wrapping][sealwrapping] to
As of Vault 0.9.0, the seal can also be used for [seal wrapping][sealwrap] to
add an extra layer of protection and satisfy compliance and regulatory requirements.
## Configuration
@ -39,4 +39,4 @@ seal "pkcs11" {
For configuration options which also read an environment variable, the
environment variable will take precedence over values in the configuration file.
[sealwrapping]: /docs/enterprise/sealwrapping/index.html
[sealwrap]: /docs/enterprise/sealwrap/index.html

2
website/source/docs/enterprise/hsm/behavior.html.md
View file

@ -73,7 +73,7 @@ and their API equivalents in the
Additionally, Vault will refuse to initialize if the option has not been set to
generate a key but no key is found. See
[Configuration](/docs/vault-enterprise/hsm/configuration.html) for more details.
[Configuration](/docs/configuration/seal/pkcs11.html) for more details.
### Rekeying

2
website/source/docs/enterprise/hsm/security.html.md
View file

@ -23,7 +23,7 @@ stored in Vault's configuration file, read access to the file should be tightly
controlled to appropriate users. (Vault's configuration file should always have
tight write controls.) Rather than storing these values into Vault's
configuration file, they can also be supplied via the environment; see the
[Configuration](/docs/vault-enterprise/hsm/configuration.html) page for more details.
[Configuration](/docs/configuration/seal/pkcs11.html) page for more details.
The attack surface of stolen PKCS#11 credentials depends highly on the
individual HSM, but generally speaking, it should be assumed that if an

2
website/source/docs/enterprise/sealwrap/index.html.md
View file

@ -10,7 +10,7 @@ description: |-
# Seal Wrap
Vault Enterprise features a mechanism to wrap values with an extra layer of
encryption for supporting [seals](/docs/configuration/seal.html). This adds an
encryption for supporting [seals](/docs/configuration/seal/index.html). This adds an
extra layer of protection and is useful in some compliance and regulatory
environments, including FIPS 140-2 environments.