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

Re: AW: signature portability / C14N / inherited namespaces

From: merlin <merlin@baltimore.ie>
Date: Thu, 24 May 2001 13:13:00 +0100
To: "Gregor Karlinger" <gregor.karlinger@iaik.at>
Cc: w3c-ietf-xmldsig@w3.org
Message-Id: <20010524121300.46F9044C71@yog-sothoth.ie.baltimore.com>

Hi Gregor,

r/gregor.karlinger@iaik.at/2001.05.24/14:08:19
>  I have not thought a lot about the consequences of the following idea,
>  but anyway: Should we add an additional rule both to the processing
>  rules for signature generation and validation, that the SignedInfo
>  element should be isolated from its context prior to computing
>  the canonicalized representation?

Unfortunately we can't isolate SignedInfo. An XPath/XSLT Transform
can legitimately rely on inherited namespaces. I have a queued
followup to my earlier question on this topic, I just need to
finish it.

Merlin


-----------------------------------------------------------------------------
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.
   http://www.baltimore.com
Received on Thursday, 24 May 2001 08:13:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:10:05 UTC