[xmlsec] XMLSec with OpenSSL 3.x
aleksey at aleksey.com
Tue May 17 16:14:28 UTC 2022
The real migration to OpenSSL 3.x was much more complex than expected.
BIG THANKS to David Bailey (snargit) for creating the PR for the
which I forked here to add small polishing:
The work is now merged in the master. There are still a few things that
needs to be done:
1) Custom engines are deprecated in OpenSSL 3 and are disabled in the
build against OpenSSL 3. I will need to think about best ways to migrate
2) I want to add automatic builds against OpenSSL 3 since the code is
However overall, the OpenSSL 3 build is working and ready for testing!
Thanks a lot, David!
On 3/25/22 1:10 PM, Aleksey Sanin wrote:
> First, I love patches :) Second, I was planning to look into it sometime
> this year. So far, it's indeed a lot of "deprecated" warnings but
> I believe everything works. The work is to replace direct structures
> access with macros (for old version) or function calls (for newer
> versions). Functionality didn't change really so I don't believe it's
> super urgent.
> On 3/25/22 10:40 AM, Soós András wrote:
>> Hi Aleksey,
>> The XMLSec library is now compatible with OpenSSL 1.1.x. I would like
>> to know when the XMLSec library will be compatible with the OpenSSL
>> 3.x version. Yesterday I tried to compile the XMLSec 1.2.30 with
>> OpenSSL 3.0.2. It worked fine, but I got a lot of compiler warnings
>> about using deprecated functions and structures. Others have already
>> inquired about the compatibility, or am I the first one? Refactoring
>> the program code is not a little work, I know, because I’m in a same
>> project with our own codes. The XMLSec library is a very important
>> part of our work, and we plan to keep it for long time to come.
>> Thank you in advance if you have any encouraging answer.
>> Best regards
>> András Soós
> xmlsec mailing list
> xmlsec at aleksey.com
David Bailey <notifications at github.com>
More information about the xmlsec