XMLSec 1.3.1-rc1

[lsh123]

The XMLSec 1.3.1 release includes the following changes:

• Added "--with-libltdl" option for ./configure to allow custom libltdl installations and deprecated "--enable-crypto-dl" option.
• Added support for cclang compiler on non-MacOSX platforms.
• (xmlsec-nss) Bumped minimum supported NSS version to 3.52.
• Several other small fixes (more details).

Please test the release candidate (signature) and let me know if you see any issues!

Aleksey

---

This discussion was created from the release 1.3.1-rc1.

[vmiklos]

Looks good on the odfsig side.

xmlsec-1.3 in libreoffice is so far not a success, but that is mainly not your fault. :-) https://bugs.documentfoundation.org/show_bug.cgi?id=155034 has more details, but in short xmlsec-1.3 uses some newer NSS symbols that seems to be not too interesting in our use-case but does cause problems when binaries are used on older distros, so at the moment we had to go back to xmlsec-1.2 for now. It's not clear to me if it makes sense to spend energy on having some --disable-whatnot switch that avoids these newer symbols or just give some time and time will fix these problems. (Just a FYI, as I feel a bit bad that you spent so much time on addressing our use-case, ans in the short-term now we don't actually use this new release due to unexpected problems.)

[lsh123]

great! anything else that you need for LO?

[vmiklos]

Not at the moment, thanks. Will try the xmlsec 1.2 -> 1.3 transition once again, after 1.3.1 is out, now that the NSS requirement is lowered.

[simo5]

I merged this PR to master -- could you please try it? as I said, the only downside is that you have to compile separately for NSS < 3.52 and NSS > 3.52 (unfortunately NSS broke the binary compatibility with this rename).

It is mostly a build time incompatibility, binary-wise it should not cause any issues (ie if you built against an older version you should be able to run against a newer one w/o problems as NSS should have internal fallback code to accept the old structure still).

[lsh123]

I don't think NSS has the fallback. I believe this renaming in NSS broke binary compatibility for NSS.

[simo5]

That would be sad ...