XMLSec 1.3.1-rc1 #659
Replies: 1 comment 13 replies
-
|
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.) |
Beta Was this translation helpful? Give feedback.
-
|
great! anything else that you need for LO? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
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). |
Beta Was this translation helpful? Give feedback.
-
|
I don't think NSS has the fallback. I believe this renaming in NSS broke binary compatibility for NSS. |
Beta Was this translation helpful? Give feedback.
-
|
That would be sad ... |
Beta Was this translation helpful? Give feedback.
-
The XMLSec 1.3.1 release includes the following changes:
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.
Beta Was this translation helpful? Give feedback.
All reactions