Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

OpenID
or
Sign in Register

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

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.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

Remove invalid key from the known_hosts file for the IP address of a host

Terminal - Remove invalid key from the known_hosts file for the IP address of a host
ssh-keygen -R `host hostname | cut -d " " -f 4`
2009-09-23 14:58:28
User: flart
Functions: cut hostname ssh ssh-keygen
5
Up
Down
Remove invalid key from the known_hosts file for the IP address of a host

Quick shortcut if you know the hostname and want to save yourself one step for looking up the IP address separately.

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
ssh-keygen -R $(dig +short host.domain.tld)
2012-01-19 15:08:50
User: atoponce
Functions: dig ssh ssh-keygen
Tags: ssh dig ssh-keygen
2
Up
Down
Remove invalid key from the known_hosts file for the IP address of a host

Quick shortcut if you know the hostname and want to save yourself one step for looking up the IP address separately.

Comments (0) | Add to favourites | Report as malicious
for HOSTTOREMOVE in $(dig +short host.domain.tld); do ssh-keygen -qR $HOSTTOREMOVE; done
2012-01-19 15:57:10
User: bibe
Functions: dig ssh-keygen
Tags: ssh dig ssh-keygen
0
Up
Down
Remove invalid key from the known_hosts file for the IP address of a host

Works for multiple hosts (such as www.google.com) and/or wrong hosts.

Show sample output | Comments (0) | Add to favourites | Report as malicious

Know a better way?

If you can do better, submit your command here.

What others think

nice! because I always delete the wrong line in the known_hosts file upon key errors, ever since the hostnames started being hashed by default. This is great, although I wonder if this will get each and every instance since the hosts' key may be listed under three different names: (1) the bare hostname, such as "bob", (2) the FQDN, such as "bob.example.com", or (3) the IP address. I'm guessing ssh-keygen just deletes entries corresponding to exactly what the input was.

Comment by bwoodacre 239 weeks and 1 day ago

@bwoodacre

Exactly. You need to run 'ssh-keygen -R' for every instance of the host in the known_hosts file.

It's nevertheless more comfortable than editing it by hand IMO :-)

Comment by flart 239 weeks ago

Repeat after me: avoid backticks, they're evil ...

Comment by assarbad 113 weeks and 1 day ago

Your point of view

You must be signed in to comment.

Related sites and podcasts