<- Back
Comments (67)
- capitol_Finally encrypted client hello support \o/
- caycepHow is OpenSSl these days? I vaguely remember the big ruckus a while back, was it Heartbleed? where everyone to their horror realized it was maybe 1 or 2 people trying to maintain OpenSSL, and the OpenBSD people then throwing manpower at it to clear up a lot of old outstanding bugs. It seems like it is on firmer/more organized footing these days?
- georgthegreathttps://www.haproxy.com/blog/state-of-ssl-stacksAccording to this one should not be using v3 at all..
- NeywinyGood to see const more prevalent. Too often I have to add that in to libraries for embedded. Possibly I believe in const by default but it is what it is at this point
- ge96Just in time for the suckerpinch video
- rwmjCompared to OpenSSL 3 this transition has been very smooth. Only dropping of "Engines" was a problem at all, and in Fedora most of those dependencies have been changed.
- yjftsjthsd-hAs a complete non-expert:On the one hand, looks like decent cleanup. (IIRC, engines in particular will not be missed).On the other hand, breaking compatibility is always a tradeoff, and I still remember 3.x being... not universally loved.
- bensyversonI just updated to 3.5x to get pq support. Anything that might tempt me to upgrade to 4.0?
- jmclnxI wonder how hard it is to move from 3.x to 4.0.0 ?From what I remember hearing, the move from 2 to 3 was hard.
- theowawayoh no not another breaking ABI change
- pixel_poppingMythos is coming for yaaaaa (just kidding).