Skip to main content
12 events
when toggle format what by license comment
Jun 16, 2020 at 9:49 history edited CommunityBot
Commonmark migration
Apr 1, 2016 at 22:16 vote accept UTF-8
Apr 1, 2016 at 22:16 vote accept UTF-8
Apr 1, 2016 at 22:16
Apr 1, 2016 at 22:16 comment added UTF-8 I didn't realize the fingerprint is the md5 hash in hexadecimal with bytes separated by colons. Thank you!
Apr 1, 2016 at 17:50 comment added Jakuje The first command (ssh-keygen -l -E md5 -f /etc/ssh/ssh_host_ecdsa_key.pub) will give you fingerprint from Pi console and the same fingerprint you see in the prompt while accepting connection, isn't it? Where is the problem?
Apr 1, 2016 at 17:47 comment added UTF-8 The command only prints /dev/fd/63 is not a public key file.. I meant something like: I ask the Pi on the console for its fingerprint. Then (when connecting over an insecure channel) I only have to compare the fingerprint it shows me with the one I got from the Pi and can make sure I really am connecting to my Pi. Would this work or do I still need to compare the public key of the Pi with the one it saves to my known hosts file after I accepted the connection? And can I get this public key before saving it to my known hosts file?
Apr 1, 2016 at 7:14 comment added Jakuje I added a ssh-keygen command to generate fingerprint from known_hosts file. I hope it will answer your question.
Apr 1, 2016 at 7:14 history edited Jakuje CC BY-SA 3.0
added 190 characters in body
Apr 1, 2016 at 5:57 comment added Jakuje Yes. It was typo. Fixed now. You can verify it by comparing the fingerprints.
Apr 1, 2016 at 5:54 history edited Jakuje CC BY-SA 3.0
deleted 3 characters in body
Mar 31, 2016 at 23:31 comment added UTF-8 If one wants to force the new version to use the old hash, shouldn't they put "md5" there instead of "sha256"? And can I figure out whether the fingerprint is correct before adding the entry to the known hosts file?
Mar 31, 2016 at 18:56 history answered Jakuje CC BY-SA 3.0