W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2001

Re: C14N Argument

From: merlin <merlin@baltimore.ie>
Date: Thu, 26 Jul 2001 10:11:12 +0100
To: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
Cc: "Dournaee, Blake" <bdournaee@rsasecurity.com>, "'John Boyer'" <JBoyer@PureEdge.com>, "Joseph M. Reagle Jr." <reagle@w3.org>, w3c-ietf-xmldsig@w3.org
Message-Id: <20010726091112.ED3F243BCB@yog-sothoth.ie.baltimore.com>

Another use for explicit c14n is after an XSLT transform
(whose output is an implementation-dependent stream).
Here, an explicit C14n transform is also necessary.


>I think your argument works only for the default Canonical XML that
>strips comments. If you want to retain comments or to use Exclusive
>XML Canonicalization, or use some other canonicalization/serialization
>some place where you are going from a node set to an octet stream then
>you need to specify it explicitly.
>From:  "Dournaee, Blake" <bdournaee@rsasecurity.com>

Baltimore Technologies plc will not be liable for direct,  special,  indirect 
or consequential  damages  arising  from  alteration of  the contents of this
message by a third party or as a result of any virus being passed on.

In addition, certain Marketing collateral may be added from time to time to
promote Baltimore Technologies products, services, Global e-Security or
appearance at trade shows and conferences.

This footnote confirms that this email message has been swept by
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.
Received on Thursday, 26 July 2001 05:12:49 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:36 UTC