News for hackers. Stuff that matters.
Re:OpenSSH Keys: A Walkthrough by jvehent on Sunday January 22, 2017 @01:28PM (#13456385)
RSA is safe. You should keep using it. Modern crypto is starting to use ECDSA because smaller key size means faster computation, but you wouldn't notice the difference in SSH anyway.

More info: https://wiki.mozilla.org/Security/Guidelines/OpenSSH

Re:OpenSSH Keys: A Walkthrough by Rafert on Sunday January 22, 2017 @01:49PM (#13456516)
The link prefers Ed25519 over RSA and uses ECDSA last where possible. It's faster and some also trust djb's work on curves over that from NIST.
Re:OpenSSH Keys: A Walkthrough by nickysielicki on Sunday January 22, 2017 @01:33PM (#13456415)
(edit: this is wrong, see below.)

> Modern crypto is starting to use ECDSA because smaller key size means faster computation, but you wouldn't notice the difference in SSH anyway.

If you're using SSH for tiny bits of text (eg: bash) you won't.

If you're using SSH to move gigabytes of binary data (eg: rsync) you might.

Re:OpenSSH Keys: A Walkthrough by ycmbntrthrwaway on Sunday January 22, 2017 @01:37PM (#13456434)
> If you're using SSH to move gigabytes of binary data (eg: rsync) you might.

No.

RSA or other asymmetric crypto is only used during connection establishment for authentication. Then symmetric key is established using DH and you use symmetric encryption to encrypt the data.

Re:OpenSSH Keys: A Walkthrough by nickysielicki on Sunday January 22, 2017 @02:38PM (#13456876)
That makes perfect sense. Apologies for spreading incorrect information, and thanks for correcting me.

I remember changing around my ssh config a while back and seeing lower speeds when rsync'ing from an older laptop. But that makes sense, I recall cranking up my DH group to 16, 4096-bit, and that was probably why it was struggling.

Re:OpenSSH Keys: A Walkthrough by throwawayish on Sunday January 22, 2017 @02:04PM (#13456626)
No, not at all.

What you do notice is using ciphers that are apt for the machine. If both ends are modern x86, for example, then you'd want to use [email protected] or [email protected] for best performance. Otherwise stick to [email protected], which is the default of recent versions.