Comments on: removing outdated ssh fingerprints from known_hosts with sed or … ssh-keygen

By: Alex

Alex — Thu, 03 Jun 2010 11:33:00 +0000

Nice idea.

I usually do a

“vi .ssh/known_hosts +46″

if I got the message. vi will jump to the line 46 already and I press dd, then save.

Alex

By: Albert

Albert — Sat, 29 May 2010 01:33:08 +0000

If you using Openshh on Windows. The “know_host” files is at:
C:\Document and Settings\”User”\.ssh
notice I put “User” Where computer user should be.
once in “.ssh” you will see “know_host”
you can open “know_host” with Wordpad just right click ->open with ->choose “Wordpad”

By: Minh Nguyen

Minh Nguyen — Wed, 24 Mar 2010 14:50:28 +0000

wow.. this is great article.

Thanks a lot
-minh

By: Carl

Carl — Mon, 15 Feb 2010 22:52:30 +0000

Kudos for the use of sed! Some lightweight implementations of ssh like dropbear do not have utilities for key management, so the use of core-utils or busybox applets like sed are essential skills for many system administrators. Thanks for the article.

– Carl

By: user

user — Fri, 24 Apr 2009 20:00:07 +0000

thanks a lot man… believe it or not this has been bugging me for a years. but editing it with vim was always the quickest way… until now…

By: EMa

EMa — Sat, 16 Aug 2008 12:09:14 +0000

Thanks for the post.

I used the sed command to remove automatic all COMPROMISED fingerprints from the known_hosts file. http://umija.org/umija:encrypt:ssh

EdMa

By: GZ

GZ — Fri, 11 Jul 2008 15:41:21 +0000

Thanks! With the whole open SSL weak key issue, this is just what I needed after applying updates!

By: ccm

ccm — Thu, 05 Jun 2008 08:40:17 +0000

@Asuka: thank you, you are right of course.

By: Asuka Kenji

Asuka Kenji — Thu, 05 Jun 2008 06:38:34 +0000

I think:

ssh-keygen -R localhost

at line 9 in your second example should read:

ssh-keygen -R secrethost

instead.

By: ccm

ccm — Thu, 29 May 2008 09:38:25 +0000

@John: It counts human-friendly beginning from “1″. It is therefore compatible to sed and common editors showing line numbers.