4 ms·
Actually, it looks like the public key can be derived from a packet capture of SSH. See https://tools.ietf.org/html/rfc4252#section-7 https://tools.ietf.org/htm
by drewbug 11y ago
Actually, it looks like the public key can be derived from a packet capture of SSH. See https://tools.ietf.org/html/rfc4252#section-7 https://tools.ietf.org/html/rfc4252#section-7
- scintill76 11y agoI think that packet is encrypted, though -- at least, it looks like that in Wireshark to me. I see key exchange packets and the following ones seem to become encrypted, before I have given ssh-agent the approval to use my key. I am mostly going off of what Wireshark's protocol decoders tell me, though, so I could be wrong.
- drewbug 11y agoYou're right, I was wrong. Sorry!
- the8472 11y agoAIUI A SSH session first performs a DH key exchange and authenticates the server. Only over that already-encrypted session will the client offer its public keys. That means the public key will not be leaked to outside observers. Combine with server-specific keys to avoid potential "try logging into my server" social engineering. This means only the server will ever learn your public key, but it has to know that already anyway. So publishing your public key does not leak any privacy bits.
- drewbug 11y agoYou're right, my bad.