What has been planned for a long time now, prior to the infamous heartbleed fiasco of OpenSSL (which does not affect SSH at all), is now officially a reality - with the help of some recently adopted crypto from DJ Bernstein. OpenSSH now finally has a compile-time option to no longer depend on OpenSSL, the option `make OPENSSL=no` has now been introduced for a reduced-configuration OpenSSH to be built without OpenSSL.
The result would leave you with no legacy SSH-1 baggage at all, and on the SSH-2 front with only AES-CTR and chacha20+poly1305 ciphers, ECDH/curve25519 key exchange and Ed25519 public keys.
[Editor's Note: This appears to be very much a Work-in-Progress, so might not be available for your distro or via standard repositories.]
(Score: 2) by frojack on Thursday May 01 2014, @08:43PM
The TFA is somewhat misleading and hypish. (Intentionally, I suspect).
OpenSSL via libssl were virtually NEVER actually used in mainstream SSH, and you were NOT at risk this whole time.
The feature to use libssl was for third party authentication mechanisms typically found in managing remote/virtual machines via a web browser interface [fedoraproject.org].
It never was mainstream use, and I will bet you a dollar you never ever used it.
No, you are mistaken. I've always had this sig.