- From: Rich Salz <rsalz@datapower.com>
- Date: Fri, 13 Jun 2003 12:19:32 -0400
- To: Aleksey Sanin <aleksey@aleksey.com>
- CC: TAMURA Kent <kent@trl.ibm.com>, w3c-ietf-xmldsig@w3.org
>Thanks for reporting. We developed a high-performance version >of c14n code after interop tests, and it introduced the problem. >We'll fix it. Tamura-san, We also found a problem. Signatures contained in a SOAP message like this: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" ...> <SOAP:Header xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" ...> </SOAP:Header> <SOAP:Body xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" ...> </SOAP:Body> </soapenv:Envelope> Did not work. We had to use the exact same NS prefix: <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" ...> <SOAP:Header> ... </SOAP:Header> <SOAP:Body> ... </SOAP:Body> </SOAP:Envelope> I think this is related to the C14N problem Aleksey reported. What do you think? /r$ -- Rich Salz, Chief Security Architect DataPower Technology http://www.datapower.com XS40 XML Security Gateway http://www.datapower.com/products/xs40.html XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
Received on Friday, 13 June 2003 12:19:48 UTC