On 11/06/2014 04:39 AM, Colm O hEigeartaigh wrote:
I think for DOMReference.transform you could probably use the provider object that is already available in the class...
That provider is from XMLSignatureFactory.getProvider() which typically would not contain a MessageDigest implementation.
I'm fine with adding a new property called org.jcp.xml.dsig.internal.dom.MessageDigestProvider
Please send in a patch. Thanks, Sean
Colm. On Thu, Nov 6, 2014 at 12:01 AM, kiwiwings <kiwiwi...@apache.org <mailto:kiwiwi...@apache.org>> wrote: Hi, I currently have some problems with getting our tests run through cleanly [1] This is based on a JDK problem [2] on certain distributions like ubuntu. While trying to workaround the problem, I've noticed that in DOMSignatureMethod.sign() it's possible to provide a Provider via the org.jcp.xml.dsig.internal.dom.SignatureProvider property, whereas in DOMReference.transform() it defaults to the JCE provider. If you think it makes sense to handle it the same, I'll provide a patch for using the property in DOMReference (... after finishing our release problem ...) Andi. [1] http://apache-poi.1045710.n5.nabble.com/org-apache-poi-poifs-crypt-TestSignatureInfo-failing-on-trunk-on-Java-6-td5717032.html [2] https://bugzilla.redhat.com/show_bug.cgi?id=1155012 -- View this message in context: http://apache-xml-project.6118.n7.nabble.com/Custom-Security-Provider-for-DOMReference-tp41569.html Sent from the Apache XML - Security - Dev mailing list archive at Nabble.com. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
