News for hackers. Stuff that matters.
Re:LibreSSL 3.2.0 – TLS 1.3 by tialaramex on Monday June 01, 2020 @11:16AM (#23379422)
This item from their change list:

> Use non-expired certificates first when building a certificate chain.

.. Is relevant to the recent expiry of Sectigo's old "AddTrust" root. If your library cheerfully assembles a trust path with the expired root and then concludes the certificate isn't valid because the root is expired you're pointlessly inconvenienced compared to a library that can use the same raw materials to discover a working trust path with no expired certificates.

Re:LibreSSL 3.2.0 – TLS 1.3 by notaplumber on Monday June 01, 2020 @11:45AM (#23379795)
Re:LibreSSL 3.2.0 – TLS 1.3 by user5994461 on Monday June 01, 2020 @12:21PM (#23380227)
Would be nice to patch openssl and python to skip expired certificates too when there is a newer one available.
Re:LibreSSL 3.2.0 – TLS 1.3 by mperham on Monday June 01, 2020 @03:11PM (#23382445)
I believe this was fixed in openssl 1.1.1 but there are millions of devices still on 1.0.x
Re:LibreSSL 3.2.0 – TLS 1.3 by EdwardDiego on Monday June 01, 2020 @07:37PM (#23385394)
Yeah, we're seeing it in coworkers still running OSX Mojave (albeit with older LibreSSL instead of OpenSSL) using the default curl. Catalina users seem okay though.