clarify cloud based use case for hypothetical non-tofu ssh
This commit is contained in:
parent
51721ffdc0
commit
cbe658b7ae
@ -317,7 +317,7 @@ Host key verification failed.
|
||||
</p>
|
||||
<hr/>
|
||||
<p>
|
||||
Because of the case for absolute simplicity, I think if anything,
|
||||
Because of the case for absolute simplicity, I think that in a cloud based use-case
|
||||
it might even make sense to remove the TOFU and make the ssh client even less user friendly; requiring the
|
||||
expected host key to be passed in on every command by default
|
||||
would dramatically increase the security of real-world SSH usage.
|
||||
|
Loading…
Reference in New Issue
Block a user