Removes single line from known_hosts file

rhost() { if [[ $1 =~ ^[0-9]+$ ]]; then sed -i "$1"d ${HOME}/.ssh/known_hosts; else echo "rhost [n]"; fi }
Quickly remove the conflicting line (key) from current users known_hosts file when there is an SSH host conflict. Very nice when you get tired of writing out full commands. Ideally you would place this into your .bash_profile Usage: rhost [n] Example: rhost 33 (removes line 33 from ~/.ssh/known_hosts) Function assumes the $HOME exists, you could alternatively use "~/.ssh/known_hosts" Mac OSX likes a space for sed -i "$1" d

By: lowjax
2013-08-01 21:10:34

What Others Think

You have a much simpler command to clean up the know_hosts file: ssh-keygen -R hostname
jld · 416 weeks and 6 days ago
I cant stand "ssh-keygen -R hostname". IMO. When you are denied access because of conflicting keys, you don't necessarily have the IP/Host available cleanly. You either have the previous SSH command to pull the IP/Host, or go back to what you referenced earlier. Takes time, click, keys, effort. Instead this command allows you to input the line number of the offending key, the one useful tidbit from the denied SSH attempt. Example: ssh me@hostname Outputs : blah blah blah failed, offending key on line 12 rhost 12 ssh me@hostname
lowjax · 416 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: