I will get back on this. I am on something other imp work. Thanks for
cooperation.
-satish
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, August 08, 2008 2:49 AM
To: security-dev@xml.apache.org
Subject: Re: Signature validation problem - C14N
I agree. Returning null is intentional and is a performance optimization
as Raul mentions. The c14ned bytes are still being written to the output
stream.
I validated the signature with the JSR 105 API, and it is invalid. The
reference digests don't match. Here's some debugging info:
Expected
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Raul Benito
Sent: Thursday, August 07, 2008 6:06 PM
To: security-dev@xml.apache.org
Subject: Re: Signature validation problem - C14N transform returns null
Sathis,
I think that particular code is correct, it is strange because
Sathis,
I think that particular code is correct, it is strange because the
api, that the transformation and the c14n is using looks like a
pipeline one, but after profiling it I change it to a visitor one, the
problem is that in some parts of the code there are some users as
pipeline that is why I
I am facing a issue with validating the xml signature. I have enveloped
transform followed by ex-C14N. I did search xmlsec mail archive but to
no success. Then I tried with debugging the xmlsec src code:
The Reference object loops through all the configured transforms, the
http://www.w3.org/2
I am facing a issue with validating the xml signature. I have enveloped
transform followed by ex-C14N. I did search xmlsec mail archive but to no
success. Then I tried with debugging the xmlsec src code:
The Reference object loops through all the configured transforms, the
http://www.w3.org/20
