Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
posted by janrinok on Thursday May 01 2014, @12:14PM   Printer-friendly
from the its-progress dept.

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.]

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by Anthony J. Bentley on Thursday May 01 2014, @05:35PM

    by Anthony J. Bentley (2757) on Thursday May 01 2014, @05:35PM (#38566)

    OpenSSL is composed of two libraries, libssl (which implements various versions of SSL and TLS) and libcrypto (which implements various crypto primitives). Libcrypto is generally considered to be somewhat more sane than libssl; it is certainly smaller and less complex. Heartbleed only affected programs using libssl. OpenSSH uses libcrypto, but that is now optional (but likely to remain the default) due to its new elliptic curve support.