Fix warnings about strict host key checks
This rephrases misleading warnings about known hosts, removing them entirely for versions where the default behaviour is secure.
This commit is contained in:
parent
3f319bd63d
commit
8013c78a96
|
|
@ -88,14 +88,6 @@ The key has to be in PEM format.
|
|||
|
||||
### Known hosts
|
||||
|
||||
:::warning
|
||||
|
||||
If you don't add one or more public keys into the secret, any server's public key will be trusted and added. (`ssh -o
|
||||
stricthostkeychecking=yes` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
`false`.
|
||||
|
||||
:::
|
||||
|
||||
Fleet supports injecting `known_hosts` into an SSH secret. Here is an example of how to add it:
|
||||
|
||||
Fetch the public key hash (taking Github as an example)
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ The key has to be in PEM format.
|
|||
:::warning
|
||||
|
||||
If you don't add one or more public keys into the secret, any server's public key will be trusted and added. (`ssh -o
|
||||
stricthostkeychecking=yes` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
stricthostkeychecking=no` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
`false`.
|
||||
|
||||
:::
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ The key has to be in PEM format.
|
|||
:::warning
|
||||
|
||||
If you don't add one or more public keys into the secret, any server's public key will be trusted and added. (`ssh -o
|
||||
stricthostkeychecking=yes` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
stricthostkeychecking=no` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
`false`.
|
||||
|
||||
:::
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ The key has to be in PEM format.
|
|||
:::warning
|
||||
|
||||
If you don't add one or more public keys into the secret, any server's public key will be trusted and added. (`ssh -o
|
||||
stricthostkeychecking=yes` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
stricthostkeychecking=no` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
`false`.
|
||||
|
||||
:::
|
||||
|
|
|
|||
|
|
@ -83,14 +83,6 @@ The key has to be in PEM format.
|
|||
|
||||
### Known hosts
|
||||
|
||||
:::warning
|
||||
|
||||
If you don't add one or more public keys into the secret, any server's public key will be trusted and added. (`ssh -o
|
||||
stricthostkeychecking=yes` will be used), unless you install Fleet with chart value `insecureSkipHostKeyChecks` set to
|
||||
`false`.
|
||||
|
||||
:::
|
||||
|
||||
Fleet supports injecting `known_hosts` into an SSH secret. Here is an example of how to add it:
|
||||
|
||||
Fetch the public key hash (taking Github as an example)
|
||||
|
|
|
|||
Loading…
Reference in New Issue