Live data from Hacker News

OpenSSH 6.8 released

lists.mindrot.org

1–10 of 44 posts

Re: OpenSSH 6.8 released

#5

The --without-openssl option is particularly attractive on Linux systems if you distrust openssl's code.

It is, but please note that OpenSSH uses very little of OpenSSL's code. None of the serious bugs lately had any impact on OpenSSH.

Re: OpenSSH 6.8 released

#7
post #6

The --without-openssl option is particularly attractive on Linux systems if you distrust openssl's code.

What functionality do you lose if you build it with that option?

From the article:

    Disables and removes dependency on OpenSSL. Many features,
    including SSH protocol 1 are not supported and the set of crypto
    options is greatly restricted. This will only work on systems
    with native arc4random or /dev/urandom.
I haven't dug into the source code, but I'd wager that the crypto options that remain are Ed25519, ChaCha20-Poly1305, etc. (Don't quote me on this, however.)

Re: OpenSSH 6.8 released

#8
post #5

The --without-openssl option is particularly attractive on Linux systems if you distrust openssl's code.

It is, but please note that OpenSSH uses very little of OpenSSL's code. None of the serious bugs lately had any impact on OpenSSH.

That's probably very reassuring.

I personally don't share this belief that openssl is bad (in fact, for PHP developers, openssl is preferable to libmcrypt which has been abandoned since 2007), I just know it's a common sentiment of infosec people. :)

Re: OpenSSH 6.8 released

#9
post #2

I was hoping for U2F but I guess it's not ready yet. :)

Chrome has access to USB and its own code to handle U2F devices. This would require your SSH client to have the same capabilities.

This might work well on Linux/BSD machines, but likely not on OSX due to stagnant unix utility updates and Windows because... well, not a real Unix. Would probably require a heavy wrapper around Putty. Not sure if cygwin and friends would ever work either.

Re: OpenSSH 6.8 released

#10
I submitted a very detailed bug report[0] a while ago, which can lead to a DoS (albeit in a very specific setting). I don't expect anyone to rush to fix it, but I'm surprised that there isn't even a comment about it. Is there another place it needs to be reported in?

[0] https://bugzilla.mindrot.org/show_bug.cgi?id=2265

Post reply on HN