$ rpm -ql openoffice.org-core | grep xmlsec /usr/lib/openoffice.org1.9.92/program/libxmlsec1-nss.so /usr/lib/openoffice.org1.9.92/program/libxmlsec1-nss.so.1 /usr/lib/openoffice.org1.9.92/program/libxmlsec1-nss.so.1.2.6 /usr/lib/openoffice.org1.9.92/program/libxmlsec1.so /usr/lib/openoffice.org1.9.92/program/libxmlsec1.so.1 /usr/lib/openoffice.org1.9.92/program/libxmlsec1.so.1.2.6 /usr/lib/openoffice.org1.9.92/program/libxmlsecurity.so /usr/lib/openoffice.org1.9.92/program/libxsec_xmlsec.so /usr/lib/openoffice.org1.9.92/program/resource/xmlsec680en-US.res We have a libxmlsec1 package in the distro - is there a reason it can't be used?
Yes.
There are a pile of patches which Sun added about which I've hassled sun and our libxmlsec maintainer (DV) about upstreaming into the mainstream libxmlsec for months and months. There's been grindingly slow progress, and it's the mainstream libxmlsec is still not a drop in replacement. More reachable is replacing the db3 libraries with our system db4 if https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=153231 and https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=153230 got done.
OK, I saw: The new XML Security Library 1.2.8 release merges OpenOffice.org changes to xmlsec-mscrypto and xmlsec-nss into main xmlsec source tree. but we don't package 1.2.8 yet. (The reason this came up is that in anaconda, xmlsec1-openssl was pulling in OO.o-core for its libxmlsec1.so.1 dependency; while it probably shouldn't do that, I was curious if we could make the problem go away in this way.)
For the record, as of 1.2.8 there are four methods not merged into xmlsec1 http://www.aleksey.com/pipermail/xmlsec/2005/002631.html