[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wss] Proposed text on C14N
r/rsalz@datapower.com/2003.08.28/23:54:44 >> If the application cares about the tag, then the >> original message should have contained >> >> <i:innermost xmlns:i="foo.com" ID="foo">foo</i:innermost> > >This would require applications to rewrite their documents so that >any possible subset that someone might ever want to sign has all the >necessary namespace declarations. That imposes an impossible >burden on anyone creating an XML document, and on anyone signing >any XML content. With respect to the above example, placing the namespace declaration here or in an ancestor will make no difference; the namespace is visibly utilized, so both inclusive and exclusive c14n will emit it. However, consider the following XPath transform: <dsig:XPath xmlns:foo="urn:foo"> not (ancestor-or-self::foo:NotToBeSigned) </dsig:XPath> Here, the foo prefix is utilized by raw text element content; even schema awareness cannot tell that foo is used. Exclusive c14n must be explicitly parameterized with foo or else a signature that includes this XPath transform will fail. The fact that this namespace declaration occurs within the signed data is of no consequence to exclusive c14n; it only emits parameterized or visibly-utilized namespaces. merlin ----------------------------------------------------------------------------- The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error or there are any problems please notify the originator immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. 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. This footnote confirms that this email message has been swept for Content Security threats, including computer viruses. http://www.baltimore.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]