On 2026/02/06 13:22:12 Christopher Schultz wrote: > Michael, > > On 2/5/26 2:03 PM, Michael Osipov wrote: > > Hi Mark, > > > > On 2026/02/05 16:40:18 Mark Thomas wrote: > >> All, > >> > >> I think the niggles with the last releases have been ironed out and the > >> deprecation warnings in 2.0.x have been fixed so I am planning on > >> tagging 1.3.x and 2.0.x shortly. I'm thinking tomorrow to give folks a > >> chance to get any other changes they have been considering in before I tag. > > > > Thank you for fixing the compiler warnings for pre-OpenSSL 3 APIs. I tried > > again to test with LibreSSL (Bug 64862). It does not compile (anymore). I > > think at some point we need stop lying to us and our users that we provide > > LibreSSL support as best effort. It should at least compile. Unless someone > > is willing to do the ifdefs we should rather drop support for it. > > I think tcnative 2.0 (which requires OpenSSL 3 or later) isn't going to > be able to support LibreSSL for a while. Either LibreSSL needs to > provide API compatibility, or tcnative does. > > Essentially undoing all the recent changes to remove deprecation > warnings in OpenSSL is definitely possible, then hiding those things > behind #ifdefs when LibreSSL is being used. > > The good news about doing that is most of these API incompatibilities > are constrained to within a few small functions, so, for now, things > shouldn't get out of hand. > > On the other hand, we recently removed a lot of code that was > backward-compatible with ancient OpenSSL precisely because the #ifdefs > were getting out of hand. > > tcnative 1.3.x still does compile against LibreSSL. I'll try to give it > a test this time around, both with OpenSSL and LibreSSL.
I'd personally say that for the past couple of years almost no user stepped up to have decent LibreSSL support, we can't do it. Therefore, we should be safe to remove it. No one of us is testing actively. I have given up at some point years ago although I never used LibreSSL. M --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
