Hi Berin,
well, first of all I would like to thanks you for all the work and tests done!
I 'll ckeck the new CVS version, but I have a last question: With this solved bug, will be possible now to validate a XML signed with XSEC against IAIK toolkit ?
I mean if the returned Xsec hash will be the same in both toolkits when exists the base64Binary type in the schema....
Again, thank you very much!
Cheers,
Ivan
>-<
This email has been digitally signed. You can verify its authenticity by installing Safelayer's Root Certificate:
http://ca.safelayer.com/install_root.html
>-<
IMPORTANT NOTICE: This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender. The opinions expressed within this communication are not necessarily those expressed by Safelayer Secure Communications.
| Berin Lautenbach <[EMAIL PROTECTED]>
03/08/2004 13:07
|
To: [EMAIL PROTECTED] cc: Subject: Re: XmlDsig error with base64Binary Type |
Ivan,
> 1. Your IAIK sample uses an XPath-Filter that according to my read
> should be the same as an enveloping transforms - but for some reason the
> xsec library is not outputting attributes when canonicalising. This
> looks like a bug in the library, and would explain why the IAIK sample
> does not validate.
There *was* a bug in the library. There was a case where attribute
nodes would get dropped from the input nodeset that is passed to the
xpath-filter transform. I've checked a fix into CVS and the CVS code
now validates the IAIK sample as OK.
Cheers,
Berin
smime.p7s
Description: S/MIME Cryptographic Signature
