Disposition of comments for the XML Security Working Group

ISSUE-188: Agreement referenced in XML Signature 1.1 but definition not clear [Sig11 (XML Signature 1.1)]

http://www.w3.org/2008/xmlsec/track/issues/188

Raised by: Frederick Hirsch
On product: Sig11 (XML Signature 1.1)

Issue: xenc:Agreement referenced by XML Signature 1.1 does not appear to be defined.

XML Signature 1.1 section 4.5.8, http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.htm#sec-keyconvenance


states:
"The <xenc:EncryptedKey> and <xenc:Agreement> elements defined in [XMLENC-CORE1] as children of ds:KeyInfo can be used to convey in-band key agreement information, or encrypted key material."

xenc:Agreement does not appear in XML Encryption 1.1 or in the XML Encryption schema?

also referenced in section 4.5, KeyInfo schema.
http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/Overview.htm#sec-KeyInfo

Proposal:

Change references from xenc:Agreement to enc:DerivedKey in XML Signature 1.1

http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0052.html

Which is correct?

http://www.w3.org/2001/04/xmlenc#sha384 (in XML Signature 1.1)
http://www.w3.org/2001/04/xmldsig-more#sha384 (in XML Encryption 1.1)

Do they refer to different algorithms?

---
http://lists.w3.org/Archives/Public/public-xmlsec/2010Mar/0029.html

Also,

In 6.1, the URI is

http://www.w3.org/2001/04/xmldsig-more#sha384

In 6.2.3, the URI is

http://www.w3.org/2000/09/xmldsig#sha384

Which is correct? Or, are they different?

During the Requirements Workshop that led to the 1.1 effort, some flaws in
the schema and their impact on the ds:RetrievalMethod element were
discussed. With the inability to change the schema, an alternative approach
had to be developed to fix the problems with RetrievalMethod and the
assumption had been that the solution would require changes coming in XML
Signature 2.0.

After examining the problem and working up a solution, it turns out to be
compatible with XML Signature 1.1 as a KeyInfo child element extension, and
I believe it should be incorporated into 1.1 before final approval. The
addition is small, and low risk.

I propose the following additional section to be added as 4.5.10, and the
additional schema content added to the 1.1 extension schema. (We may wish to
adjust the warning text in section 4.5.3 about the use of RetrievalMethod to
recommend the use of KeyInfoReference in its place, but this is optional.)

------
The KeyInfoReference Element

A KeyInfoReference element within KeyInfo is used to convey a reference to a
KeyInfo element at another location in the same or different document. For
example, several signatures in a document might use a key verified by an
X.509v3 certificate chain appearing once in the document or remotely outside
the document; each signature's KeyInfo can reference this chain using a
single KeyInfoReference element instead of including the entire chain with a
sequence of X509Certificate elements repeated in multiple places.

KeyInfoReference uses the same syntax and dereferencing behavior as
Reference's URI (section 4.4.3.1) and the Reference Processing Model
(section 4.4.3.2) except that there are no child elements and the presence
of the URI attribute is mandatory.

The result of dereferencing a KeyInfoReference MUST be a KeyInfo element, or
an XML document with a KeyInfo element as the root.

Note: The KeyInfoReference element is a desirable alternative to the use of
RetrievalMethod when the data being referred to is a KeyInfo element and the
use of RetrievalMethod would require one or more Transform child elements,
which introduce security risk and implementation challenges.

Schema Definition

<!-- targetNamespace="http://www.w3.org/2009/xmldsig11#" -->

<element name="KeyInfoReference" type="dsig11:KeyInfoReferenceType"/>
<complexType name="KeyInfoReferenceType">
<attribute name="URI" type="anyURI" use="required"/>
<attribute name="Id" type="ID" use="optional"/>
</complexType>

Just reviewing the schema and noted there's a redundancy:

<simpleType name="ECPointType">
<restriction base="ds:CryptoBinary"/>
</simpleType>

Other places in the EC key syntax schema just use CryptoBinary directly, so
I'd suggest removing that type definition and
s/dsig11:ECPointType/ds:CryptoBinary for consistency.

This shouldn't affect any implementations at this point.

Small nit in section 4.5.2.3, ECKeyValue Element, there's a reference to
identifying a named curve with a "URN" attribute, should be "URI" I believe.

There also seem to be issues in that section and surrounding text that
aren't properly styling element names. That may need review throughout the
text, but that's just editorial.

Due to the ongoing problems with the X509IssuerSerial element, I would ask
that a new X509Data alternative for representing certificates uniquely by
hash be added to the 1.1 schema and specification, per the suggested changes
here:

http://lists.w3.org/Archives/Public/public-xmlsec/2010Sep/0052.html