Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • You might want to double-check the "in the clear" statement. RFC 4253 (among others) state that the two systems involved in an ssh connection first exchange identification strings. Immediately afterwards they exchange keys and an encryption algorithm and key will be negotiated during the key exchange. When encryption is in effect, all packet payloads must be encrypted. All this happens before you ever see a login: prompt. Commented Nov 7, 2013 at 17:36
  • You are correct, updating answer. Commented Nov 7, 2013 at 17:57
  • "I STRONGLY (and I can't make that bold enough). Suggest you allow only PublicKey based authentication for any ssh servers that you have running on the internet." --> unfortunately it is not my responsibility to choose what method, it is external providers sFTP who choose what is the best for them and we have to fit their choices. Some providers also have firewall rules to enable only our (and others authorized companies) IP(s). Commented Nov 8, 2013 at 8:55
  • "So the key you generate on your local machine can have (and does by default) a password to decrepit it" --> I guess you are talking about the passphrase here. I made the distinction between password (to connect to the remote server) and the passphrase (to enable key extraction). Commented Nov 8, 2013 at 8:57