Re: LibreSSL 2.3.2, 2.2.6, and 2.1.10 released

On Thu, Jan 28, 2016 at 4:33 PM, Brent Cook <busterb@gmail.com> wrote:
> We have released a number of LibreSSL updates, which will be arriving in
> the LibreSSL directory of your local OpenBSD mirror soon.
>
> LibreSSL 2.2.6 and 2.1.10 contain a single change to deprecate use of
> the SSL_OP_SINGLE_DH_USE flag. It is now enabled unconditionally.
> Thanks to Antonio Sanso for the report.

Some people have noted a lack of a CVE number here.. Antoino Sanso was
a super guy and reported this problem to us directly. At his request,
we delayed release of the fix until OpenSSL released their stuff.
The actual high severity problem in OpenSSL is not present in
LibreSSL, Nor was the CVE in question assigned to LibreSSL. - So no
CVE.

We are very happy to fix problems and make a better Codebase. However
I at least will express my doubts about the benefits of the CVE system
to the community - When the CVE is not assigned to LibreSSL, We
receive no notification of it, while the project it is assigned to
gets advance notification and controls the release timing. As such
without the CVE being
assigned to LibreSSL, and us getting a say in the timing of the
release of the information and when to roll releases, I do
not see a benefit to us or the community of our promoting someone
else's invoice numbers, when we don't get a say in when stuff is
released.

>
> LibreSSL 2.3.2, a snapshot release, contains the latest developments
> from the OpenBSD 5.9 branch. It also contains ABI/API changes, which
> will stabilize once OpenBSD 5.9 is completed. At that time, LibreSSL
> 2.3.x and 2.2.x will become the stable release branches, and we will
> drop support for the 2.1.x branch.
>
> LibreSSL 2.3.2 also has the following notable changes:
>
> * Changed format of LIBRESSL_VERSION_NUMBER to match that of
> OPENSSL_VERSION_NUMBER, see:
> https://wiki.openssl.org/index.php/Manual:OPENSSL_VERSION_NUMBER(3)
>
> * Added EVP_aead_chacha20_poly1305_ietf() which matches the AEAD
> construction introduced in RFC 7539, which is different than that
> already used in TLS with EVP_aead_chacha20_poly1305()
>
> * Avoid a potential undefined C99+ behavior due to shift overflow in
> AES_decrypt, reported by Pascal Cuoq <cuoq at trust-in-soft.com>
>
> * More man pages converted from pod to mdoc format
>
> * Added COMODO RSA Certification Authority and QuoVadis
> root certificates to cert.pem
>
> * Removed Remhve "C=US, O=VeriSign, Inc., OU=Class 3 Public Primary
> Certification Authority"
> (serial 3c:91:31:cb:1f:f6:d0:1b:0e:9a:b8:d0:44:bf:12:be)
> root certificate from cert.pem
>
> * Added support for building nc(1) on Solaris
>
> * Fixed GCC 5.x+ preprocessor checks, reported by Ruslan Babayev
>
> * Improved console handling with openssl(1) on Windows
>
> * Ensure the network stack is enabled on Windows when running
> tls_init()
>
> * Fixed incorrect TLS certificate loading by nc(1)
>
> * Added support for Solaris 11.3's getentropy(2) system call
>
> * Enabled support for using NetBSD 7.0's arc4random(3) implementation
>
> * Deprecated the SSL_OP_SINGLE_DH_USE flag, thanks to Antonio Sanso.
>
> * Fixes from OpenSSL 1.0.1q (already in earlier LibreSSL stable releases)
> - CVE-2015-3194 - NULL pointer dereference in client side certificate
> validation.
> - CVE-2015-3195 - Memory leak in PKCS7 - not reachable from TLS/SSL
>
> * The following OpenSSL CVEs did not apply to LibreSSL
> - CVE-2015-3193 - Carry propagating bug in the x86_64 Montgomery
> squaring procedure.
> - CVE-2015-3196 - Double free race condition of the identify hint
> data.
>
> See https://marc.info/?l=openbsd-announce&m=144925068504102
>
> The LibreSSL project continues improvement of the codebase to reflect modern,
> safe programming practices. We welcome feedback and improvements from the
> broader community. Thanks to all of the contributors who helped make this
> release possible.