2 ms·
Eh... bad advice in general, but awesome advice for the case he's using it in. Like he says in the post: Don't set these values for hosts that you actually care
by peterwwillis 15y ago
Eh... bad advice in general, but awesome advice for the case he's using it in. Like he says in the post: Don't set these values for hosts that you actually care about.
- JoachimSchipper 15y agoOr hosts that you use passwords on that you actually care about. Or hosts that have access to a network you care about. Or... There's just too much that can go wrong.
- atakan_gurkan 15y agoI think "hosts that you care about" captures them all. Yes, there is too much that can go wrong, but for this tiny case the advice is useful. Let me quote GJ Sussman: "It is OK if it is not user-friendly, I am not a user".
- yock 15y agoIt doesn't seem like a good idea at all. SSH caches those keys because computers are more capable of flawlessly comparing long strings of random characters than humans are. The cache is so that you, presumably a human, don't need to compare the reported host key to its known value each time you connect. I understand his specific application, and why it works for him, but including it as advice for the general SSH-consuming public is nuts.