чт, 7 окт. 2021 г. в 12:49, Willy Tarreau <[email protected]>: > On Thu, Oct 07, 2021 at 11:30:54AM +0500, ???? ??????? wrote: > > > Just thinking about something, given that the new API was already > adopted > > > by BoringSSL and will probably be at some point in time by LibreSSL, > would > > > it not be better to have a single macro "HA_SSL_USE_API_V3" or > something > > > like this that we set based on the various libs' versions, and rely on > this > > > one for all other defines ? I think it could significantly simplify the > > > porting to other libs and avoid a real mess with version numbers > > > everywhere. > > > > > > > even BoringSSL states "it adopted upstream changes", it is different in > > details, for example ERR_func_error_string > > is not deprecated in BoringSSL. > > > > Well, there might be a common divisor of course. I'll keep an eye on it > :) > > > > as for this particular patch, it is openssl specific (at least now) > > OK. I'll let the SSL maintainers deal with this. >
I set up Fedora Rawhide builds. Fedora now uses openssl-3.0.0, all builds are bloody murder: fedora_clang (#1657157053) · Jobs · Ilya Shipitsin / haproxy-ci-playground · GitLab <https://gitlab.com/chipitsine/haproxy-ci-playground/-/jobs/1657157053> > > Thanks! > Willy >
