News for hackers. Stuff that matters.
Re:LibreSSL: FIPS mode is not coming back by _pmf_ on Thursday April 24, 2014 @05:34AM (#7639138)
"Fixing" it in a way that guarantees that the changes will not be pulled back into OpenSSL has the following problems:

* the fork will lag behind when new features are introduced into OpenSSL

* the fork will lag behind when new fixes for OpenSSL are implemented

This creates a permanent maintenance burden for the LibreSSL maintainers; sure they have attention now, but in 3 months nobody will give a shit any more.

Re:LibreSSL: FIPS mode is not coming back by rlpb on Thursday April 24, 2014 @07:17AM (#7639440)
Unless the rest of the world switches to using LibreSSL by default, (eg. for security reasons). Then the situation could reverse.

Given the state of the OpenSSL codebase, I think this has a greater chance of happening than most other forks.

Re:LibreSSL: FIPS mode is not coming back by _cipher_ on Friday April 25, 2014 @05:00AM (#7645406)
> "Fixing" it in a way that guarantees that the changes will not be pulled back into OpenSSL has the following problems:

> * the fork will lag behind when new features are introduced into OpenSSL

> * the fork will lag behind when new fixes for OpenSSL are implemented

> This creates a permanent maintenance burden for the LibreSSL maintainers; sure they have attention now, but in 3 months nobody will give a shit any more.

So, it's gonna be apache all over again. Where they maintained their own fork, with no security patches applied.

Or perhaps like OpenSSH, where a linux user is forced to `./configure && make && make install'.

I'm trusting your opinion, after careful reviewing of all your commits. :)

/irony off