Timeline for Public key for SSH over the internet differs from a key for SSH over the LAN
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2016 at 22:16 | vote | accept | UTF-8 | ||
| Apr 1, 2016 at 22:16 | |||||
| Apr 1, 2016 at 6:29 | comment | added | garethTheRed |
If you run ss-keygen -H (without the -f option) then it will permanently convert all IP addresses to their hash equivalent in the know_hosts file. Maybe you did this (accidentally) in the past. The hash of the server's public key should be passed to you by some out-of-band method such as talking to the server admin, or publishing it on a secure website etc.
|
|
| Mar 31, 2016 at 15:05 | comment | added | UTF-8 |
Somehow I get exactly the same as with -H: pastebin.com/Fcxswkin Is the AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAgUNwcHmVBowUoKvi9iLtoKifh/9qKAj6BNfQsYzYuoXtlYEnTUVLn4XpMYJ9+TMwL23ZDnmJuz8noKK3rFrYg= part the public key? Because this is the same whether I access via internet or via lan. Can I figure out whether the fingerprint ed:47:24:c6:4e:c1:ca:99:d9:77:59:8f:01:12:85:cd is correct before adding the key to the known hosts file? It seems like a bad idea to first say "Oh, yeah, it's alright." and then go check whether this is true and if it's not to delete the entry.
|
|
| Mar 31, 2016 at 7:02 | history | answered | garethTheRed | CC BY-SA 3.0 |