On 11/11/2004, at 10:19, Centeno Martinez, Fernando wrote:
Hello
I was testing the new xml security version 1.2, and I've found a
strange thing.
I was verifying a file. This file had got an incorrect signature with
previous versions, and now with the new version the verify says the
signature is
Hello,
which URI reference is correct?
example:
I have file in absolute path "c:\work\test.txt"
XMLsec couldn't find the file, if URI looks like
URI="file:///work/test.txt".
The exception is "Original Exception was java.io.FileNotFoundException:
\\work\test.txt (The network path was not found)"
Hello,
when trying to decrypt document that has element,
I get an NumberFormatException at XMLCypher.newEncryptionMethod()
line 2502
I think instead of:
if (null != keySizeElement) {
result.setKeySize(
Integer.valueOf(keySizeElement.getNodeValue()).intValue());
}
It should be:
if (null
You are right. This is a bug. It has been fixed now.
Thanks,
Vishal
Anton Krasovsky wrote:
Hello,
when trying to decrypt document that has element,
I get an NumberFormatException at XMLCypher.newEncryptionMethod()
line 2502
I think instead of:
if (null != keySizeElement) {
result.setKeySize(
We just upgraded to the xmlsec 1.2 RC1 release and started noticing
problems with the exclusive c14n implementation. In particular SAML
assertion signature validation started to fail after the assertion was
sent over the wire (using axis).
The assertion when initially generated declared several red
