News for hackers. Stuff that matters.
Re:The Art of Command Line by Karunamon on Monday June 15, 2015 @09:29PM (#9723301)
Depends on your circumstances, really. If you're in an environment with lots of VM's floating around, being created, destroyed, and so on, dealing with SSH's paranoia (why can't I just dismiss a warning about a host/key mismatch instead of having to edit .known_hosts?) quickly becomes an exercise in frustration for dubious security benefit. (If the enemy is on your LAN and able to manipulate your DNS, you've already lost)

On your home box, sure. But let's not pretend there's not a reason for the option to exist.

Re:The Art of Command Line by DDub on Tuesday June 16, 2015 @05:38AM (#9724676)
I use an alias to select when to, and not to, use host keys;

alias ssht='ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no'

ssht floaty.vm # does not use host key checking

ssh my.bastion.host # validates host key

Really I ought to get SSHFP records populated when my vm's are created...

Re:The Art of Command Line by jamespo on Tuesday June 16, 2015 @06:02AM (#9724772)
In these environments you can use server certificates

https://www.digitalocean.com/community/tutorials/how-to-crea...

Re:The Art of Command Line by richardwhiuk on Tuesday June 16, 2015 @04:51AM (#9724504)
In which case, just use telnet. Seriously.