W3C

XML Signature Syntax and Processing (削除) (Second Edition) (削除ここまで) (追記) Version 1.1 (追記ここまで)

W3C Recommendation (削除) 10 June 2008 (削除ここまで) (追記) 11 April 2013 (追記ここまで)

This version:
(削除) http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/ (削除ここまで) (追記) http://www.w3.org/TR/2013/REC-xmldsig-core1-20130411/ (追記ここまで)
Latest (追記) published (追記ここまで) version:
(削除) http://www.w3.org/TR/xmldsig-core/ (削除ここまで) (追記) http://www.w3.org/TR/xmldsig-core1/ (追記ここまで)
(追記) Latest editor's draft: (追記ここまで)
(追記) http://www.w3.org/2008/xmlsec/Drafts/xmldsig-core-11/ (追記ここまで)
Previous version:
(削除) http://www.w3.org/TR/2008/PER-xmldsig-core-20080326/ (削除ここまで) (追記) http://www.w3.org/TR/2013/PR-xmldsig-core1-20130124/ (追記ここまで)
(削除) Editors (削除ここまで) (追記) Editors: (追記ここまで)
Donald Eastlake (削除) < (削除ここまで) , d3e3e3@gmail.com (削除) > (削除ここまで)
Joseph Reagle (削除) < (削除ここまで) , reagle@mit.edu (削除) > (削除ここまで)
David Solo (削除) < (削除ここまで) , dsolo@alum.mit.edu (削除) > (削除ここまで)
Frederick Hirsch (削除) < (削除ここまで) , frederick.hirsch@nokia.com (削除) > (削除ここまで) (2nd (削除) edition) (削除ここまで) (追記) edition, 1.1) (追記ここまで)
(追記) Magnus Nyström (追記ここまで),(追記) mnystrom@microsoft.com (追記ここまで) (追記) (1.1) (追記ここまで)
Thomas Roessler (削除) < (削除ここまで) , tlr@w3.org (削除) > (削除ここまで) (2nd (削除) edition) (削除ここまで) (追記) edition, 1.1) (追記ここまで)
(追記) Kelvin Yiu (追記ここまで),(追記) kelviny@microsoft.com (追記ここまで) (追記) (1.1) (追記ここまで)
(削除) Authors (削除ここまで) (追記) Authors: (追記ここまで)
Mark Bartel (削除) < (削除ここまで) , mbartel@adobe.com (削除) > (削除ここまで)
John Boyer (削除) < (削除ここまで) , boyerj@ca.ibm.com (削除) > (削除ここまで)
Barb Fox (削除) < (削除ここまで) , bfox@Exchange.Microsoft.com (削除) > (削除ここまで)
Brian LaMacchia (削除) < (削除ここまで) , bal@microsoft.com (削除) > (削除ここまで)
Ed Simon (削除) < (削除ここまで) , edsimon@xmlsec.com (削除) > Contributors See Acknowledgements (削除ここまで)

Please refer to the errata for this document, which may include some normative corrections.

(削除) This document (削除ここまで) (追記) The English version of this specification (追記ここまで) is (削除) also available in these non-normative formats: XHTML with color-coded revision indicators against (削除ここまで) the (削除) previous recommendation (削除ここまで) (追記) only normative (追記ここまで) version. (追記) Non-normative (追記ここまで)(追記) translations (追記ここまで) (削除) See (削除ここまで) (追記) may (追記ここまで) also (削除) translations . (削除ここまで) (追記) be available. (追記ここまで)

Copyright (削除) © 2008 (削除ここまで) (追記) © 2013 (追記ここまで) The (削除) Internet Society (削除ここまで) (追記) IETF Trust (追記ここまで) & W3C (削除) ® (削除ここまで) (追記) ® (追記ここまで) ( MIT , ERCIM , Keio , (追記) Beihang (追記ここまで) ), All Rights Reserved. W3C liability , trademark and document use rules apply.

Abstract

This document specifies XML digital signature processing rules and syntax. XML Signatures provide integrity , message authentication , and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere.

Status of (削除) this document (削除ここまで) (追記) This Document (追記ここまで)

(追記) Note (追記ここまで):(追記) On 23 April 2013, the reference to the "Additional XML Security URIs" RFC was updated. The Director previously authorized the publication knowing that the reference would be updated in a near future. (追記ここまで)

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

(追記) This document has been reviewed by (追記ここまで)(追記) W3C (追記ここまで)(追記) Members, by software developers, and by other (追記ここまで)(追記) W3C (追記ここまで)(追記) groups and interested parties, and is endorsed by the Director as a (追記ここまで)(追記) W3C (追記ここまで)(追記) Recommendation. It is a stable document and may be used as reference material or cited from another document. (追記ここまで)(追記) W3C (追記ここまで)(追記) 's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the Web. (追記ここまで)

The original version of this specification was produced by the (削除) IETF/W3C (削除ここまで) (追記) IETF/ (追記ここまで)(追記) W3C (追記ここまで) XML Signature Working Group (削除) which believes the specification is sufficient for the creation of independent interoperable implementations; (削除ここまで) (追記) ; (追記ここまで) the Interoperability Report shows at least 10 implementations with at least two interoperable implementations over every feature.

(削除) This (削除ここまで) (追記) The (追記ここまで) Second Edition was produced by the W3C XML Security Specifications Maintenance Working Group , (削除) part of the W3C Security Activity ( Activity Statement ). This Second Edition of XML Signature Syntax and Processing adds (削除ここまで) (追記) adding (追記ここまで) Canonical XML 1.1 as a required canonicalization algorithm and (削除) recommends its use for inclusive canonicalization. This version (削除ここまで) (追記) incorporating known errata. A (追記ここまで)(追記) detailed list (追記ここまで) of (削除) Canonical XML enables use (削除ここまで) (追記) Second Edition changes (追記ここまで) (追記) is available as is a (追記ここまで)(追記) Second Edition implementation report (追記ここまで) (追記) demonstrating four or more implementations (追記ここまで) of (削除) xml:id and xml:base Recommendations with XML Signature and also enables other possible future attributes in the XML namespace. Additional minor changes, including the incorporation (削除ここまで) (追記) all new features. (追記ここまで)

(追記) Conformance-affecting changes (追記ここまで) of (削除) known errata, are documented in Changes in (削除ここまで) XML Signature (削除) Syntax and Processing (Second Edition) . The Working Group conducted an interoperability test as part (削除ここまで) (追記) 1.1 against this previous recommendation mainly affect the set (追記ここまで) of (削除) its activity. The Test Cases (削除ここまで) (追記) mandatory to implement cryptographic algorithms, including Elliptic Curve DSA (and mark-up (追記ここまで) for (削除) C14N 1.1 (削除ここまで) (追記) corresponding key material), (追記ここまで) and (削除) XMLDSig Interoperability (削除ここまで) (追記) additional hash algorithms. A detailed explanation of changes since the last Recommendation are available (追記ここまで) [ (削除) TESTCASES (削除ここまで) (追記) XMLDSIG-CORE1-CHGS (追記ここまで) (削除) ] (削除ここまで) (追記) ]. Changes (追記ここまで) are (削除) available as (削除ここまで) (追記) also described in (追記ここまで) a (削除) companion Working Group Note. The Implementation Report for XML Signature, (削除ここまで) (追記) diff document showing changes since the (追記ここまで) Second Edition (削除) is also publicly available. (削除ここまで) , (追記) as well as a (追記ここまで)(追記) diff document showing changes since the previous PR draft (追記ここまで).

Please (削除) send comments about this document (削除ここまで) (追記) refer (追記ここまで) to (削除) public-xmlsec-comments@w3.org (with public archive (削除ここまで) (追記) the (追記ここまで)(追記) implementation report for version 1.1 of this specification (追記ここまで) (削除) ). (削除ここまで) (追記) for additional details about the implementation status of features added in this revision. (追記ここまで)

This document (削除) has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed (削除ここまで) (追記) was published (追記ここまで) by the (削除) Director (削除ここまで) (追記) XML Security Working Group (追記ここまで) as a (削除) W3C (削除ここまで) Recommendation. (削除) It is a stable document and may be used as reference material or cited from another document. W3C's role in making the Recommendation is to draw attention (削除ここまで) (追記) If you wish (追記ここまで) to (削除) the specification and (削除ここまで) (追記) make comments regarding this document, please send them (追記ここまで) to (削除) promote its widespread deployment. This enhances the functionality and interoperability of the Web. (削除ここまで) (追記) public-xmlsec@w3.org (追記ここまで) (追記) ( (追記ここまで)(追記) subscribe (追記ここまで),(追記) archives (追記ここまで) (追記) ). All comments are welcome. (追記ここまで)

This document (削除) is governed by the 24 January 2002 CPP as amended (削除ここまで) (追記) was produced (追記ここまで) by (追記) a group operating under (追記ここまで) the (追記) 5 February 2004 (追記ここまで) W3C Patent Policy (削除) Transition Procedure (削除ここまで) . W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy . (削除) Patent disclosures relevant to this specification may be found on the IETF Page of Intellectual Property Rights Notices , in conformance with IETF policy. (削除ここまで)

(削除) The English version (削除ここまで) (追記) Additional information related to the IPR status (追記ここまで) of (削除) this specification (削除ここまで) (追記) XML Signature 1.1 (追記ここまで) is (削除) the only normative version. (削除ここまで) (追記) available. (追記ここまで)

Table of Contents

(削除) 1.0 Introduction (削除ここまで) (追記) 1. (追記ここまで)(追記) Introduction (追記ここまで)

This document specifies XML syntax and processing rules for creating and representing digital signatures. XML Signatures can be applied to any digital content (data object) , including XML. An XML Signature may be applied to the content of one or more resources. Enveloped or enveloping signatures are over data within the same XML document as the signature; detached signatures are over data external to the signature element. More specifically, this specification defines an XML signature element type and an XML signature application ; conformance requirements for each are specified by way of schema definitions and prose respectively. This specification also includes other useful types that identify methods for referencing collections of resources, algorithms, and keying and management information.

The XML Signature is a method of associating a key with referenced data (octets); it does not normatively specify how keys are associated with persons or institutions, nor the meaning of the data being referenced and signed. Consequently, while this specification is an important component of secure XML applications, it itself is not sufficient to address all application security/trust concerns, particularly with respect to using signed XML (or other data formats) as a basis of human-to-human communication and agreement. Such an application must specify additional key, algorithm, processing and rendering requirements. For further information, please see (追記) see (追記ここまで)(追記) section 8. (追記ここまで) Security Considerations .

(追記) The Working Group encourages implementers and developers to read (追記ここまで)(追記) XML Signature Best Practices (追記ここまで)(追記) [ (追記ここまで)(追記) XMLDSIG-BESTPRACTICES (追記ここまで) (削除) (section 8). (削除ここまで) (追記) ]. It contains a number of best practices related to the use of XML Signature, including implementation considerations and practical ways of improving security. (追記ここまで)

1.1 (削除) Editorial and (削除ここまで) Conformance (削除) Conventions (削除ここまで)

For readability, brevity, and historic reasons this document uses the term "signature" to generally refer to digital authentication values of all types. Obviously, the term is also strictly used to refer to authentication values that are based on public keys and that provide signer authentication. When specifically discussing authentication values based on symmetric secret key codes we use the terms authenticators or authentication codes. (See (追記) section 8.2 (追記ここまで) Check the Security Model (削除) , section 8.3.) (削除ここまで) .)

This specification provides (削除) an (削除ここまで) (追記) a normative (追記ここまで) XML Schema [ (削除) XML-schema (削除ここまで) (追記) XMLSCHEMA-1 (追記ここまで) (削除) ] and DTD (削除ここまで) (追記) ], (追記ここまで) [ (削除) XML (削除ここまで) (追記) XMLSCHEMA-2 (追記ここまで) ]. The (追記) full normative grammar is defined by the XSD (追記ここまで) schema (削除) definition (削除ここまで) (追記) and the normative text in this specification. The standalone XSD schema file (追記ここまで) is (削除) normative. (削除ここまで) (追記) authoritative in case there is any disagreement between it and the XSD schema portions in this specification. (追記ここまで)

The key words (削除) "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", (削除ここまで) (追記) " (追記ここまで)(追記) MUST (追記ここまで)(追記) ", " (追記ここまで)(追記) MUST NOT (追記ここまで)(追記) ", " (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) ", " (追記ここまで)(追記) SHALL (追記ここまで)(追記) ", " (追記ここまで)(追記) SHALL NOT (追記ここまで)(追記) ", " (追記ここまで)(追記) SHOULD (追記ここまで)(追記) ", " (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) ", " (追記ここまで)(追記) RECOMMENDED (追記ここまで)(追記) ", " (追記ここまで)(追記) MAY (追記ここまで)(追記) ", (追記ここまで) and (削除) "OPTIONAL" (削除ここまで) (追記) " (追記ここまで)(追記) OPTIONAL (追記ここまで)(追記) " (追記ここまで) in this specification are to be interpreted as described in (削除) RFC2119 (削除ここまで) [ (削除) KEYWORDS (削除ここまで) (追記) RFC2119 (追記ここまで) (削除) ]: (削除ここまで) (追記) ]. (追記ここまで)

(削除) "they (削除ここまで) (追記) "They (追記ここまで) MUST only be used where it is actually required for interoperation or to limit behavior which has potential for causing harm (e.g., limiting retransmissions)"

Consequently, we use these capitalized key words to unambiguously specify requirements over protocol and application features and behavior that affect the interoperability and security of implementations. These key words are not used (capitalized) to describe XML grammar; schema definitions unambiguously describe such requirements and we wish to reserve the prominence of these terms for the natural language descriptions of protocols and features. For instance, an XML attribute might be described as being "optional." Compliance with the Namespaces in XML specification [ (削除) XML-ns (削除ここまで) (追記) XML-NAMES (追記ここまで) ] is described as (削除) "REQUIRED." (削除ここまで) (追記) " (追記ここまで)(追記) REQUIRED (追記ここまで)."

(追記) This document specifies optional and mandatory to support algorithms, providing references for these algorithms. This means that a conformant implementation should for given inputs be able to produce outputs for those algorithms that interoperate as specified in the referenced specification. A conformant implementation may use any technique to achieve the results as-if it were implemented according to the referenced specification, but is not required to follow detailed implementation techniques of that specification. (追記ここまで)

1.2 Design Philosophy

The design philosophy and requirements of this specification are addressed in the (追記) original (追記ここまで) XML-Signature Requirements document [ (削除) XML-Signature-RD (削除ここまで) (追記) XMLDSIG-REQUIREMENTS (追記ここまで) (追記) ] and the XML Security 1.1 Requirements document [ (追記ここまで)(追記) XMLSEC11-REQS (追記ここまで) ].

1.3 (削除) Versions , (削除ここまで) (追記) Versions, (追記ここまで) Namespaces and Identifiers

(削除) No provision is made for an explicit version number in this syntax. If a future version is needed, it will (削除ここまで) (追記) This specification makes (追記ここまで) use (削除) a different namespace. The (削除ここまで) (追記) of (追記ここまで) XML (削除) namespace (削除ここまで) (追記) namespaces, and uses Uniform Resource Identifiers (追記ここまで) [ (削除) XML-ns (削除ここまで) (追記) URI (追記ここまで) ] (削除) URI that MUST be used by implementations (削除ここまで) (追記) to identify resources, algorithms, and semantics. (追記ここまで)

(追記) Implementations (追記ここまで) of this (削除) (dated) (削除ここまで) specification (削除) is: (削除ここまで) (追記) MUST (追記ここまで)(追記) use the following XML namespace URIs: (追記ここまで)

(削除) xmlns="http://www.w3.org/2000/09/xmldsig#" This (削除ここまで)
(追記) URI (追記ここまで) namespace (削除) is also used as the (削除ここまで) prefix (削除) for algorithm identifiers used by this specification. (削除ここまで) (追記) XML internal entity (追記ここまで)
(追記) http://www.w3.org/2000/09/xmldsig# (追記ここまで)(追記) default namespace (追記ここまで),(追記) ds: (追記ここまで),(追記) dsig: (追記ここまで)(追記) <!ENTITY dsig "http://www.w3.org/2000/09/xmldsig#"> (追記ここまで)
(追記) http://www.w3.org/2009/xmldsig11# (追記ここまで)(追記) dsig11: (追記ここまで)(追記) <!ENTITY dsig11 "http://www.w3.org/2009/xmldsig11#"> (追記ここまで)

While (削除) applications (削除ここまで) (追記) implementations (追記ここまで) MUST support XML and XML namespaces, (削除) the (削除ここまで) (追記) and while (追記ここまで) use of (削除) internal entities [ XML ] or our "dsig" XML (削除ここまで) (追記) the above (追記ここまで) namespace (削除) prefix (削除ここまで) (追記) URIs is (追記ここまで)(追記) REQUIRED (追記ここまで),(追記) the namespace prefixes (追記ここまで) and (削除) defaulting/scoping conventions (削除ここまで) (追記) entity declarations given (追記ここまで) are (削除) OPTIONAL; we (削除ここまで) (追記) merely editorial conventions used in this document. Their (追記ここまで) use (削除) these facilities to provide compact and readable examples. (削除ここまで) (追記) by implementations is (追記ここまで)(追記) OPTIONAL (追記ここまで).

(削除) This specification uses Uniform Resource Identifiers [ URI ] to identify resources, algorithms, and semantics. The URI in the (削除ここまで) (追記) These (追記ここまで) namespace (削除) declaration above is (削除ここまで) (追記) URIs are (追記ここまで) also used as (削除) a (削除ここまで) (追記) the (追記ここまで) prefix for (削除) URIs (削除ここまで) (追記) algorithm identifiers that are (追記ここまで) under (削除) the (削除ここまで) control of this specification. For resources not under the control of this specification, we use the designated Uniform Resource Names [ URN (追記) ], [ (追記ここまで)(追記) RFC3406 (追記ここまで) ] or Uniform Resource (削除) Locators (削除ここまで) (追記) Identifiers (追記ここまで) [ (削除) URL (削除ここまで) (追記) URI (追記ここまで) ] defined by (削除) its (削除ここまで) (追記) the relevant (追記ここまで) normative external specification. (削除) If an external specification has (削除ここまで)

(追記) The (追記ここまで)(追記) http://www.w3.org/2000/09/xmldsig# (追記ここまで)(追記) ( (追記ここまで)(追記) dsig: (追記ここまで)(追記) ) namespace was introduced in the first edition of this specification. This version does (追記ここまで) not (削除) allocated itself a Uniform Resource Identifier we allocate an identifier under our own namespace. For instance: (削除ここまで) (追記) coin any new elements or algorithm identifiers in that namespace; instead, the (追記ここまで)(追記) http://www.w3.org/2009/xmldsig11# (追記ここまで)(追記) ( (追記ここまで)(追記) dsig11: (追記ここまで)(追記) ) namespace is used. (追記ここまで)

(追記) This specification uses algorithm identifiers in the namespace (追記ここまで)(追記) http://www.w3.org/2001/04/xmldsig-more# (追記ここまで)(追記) that were originally coined in [ (追記ここまで)(追記) RFC6931 (追記ここまで) (追記) ]. RFC 6931 associates these identifiers with specific algorithms. Implementations of this specification (追記ここまで)(追記) MUST (追記ここまで)(追記) be fully interoperable with the algorithms specified in [ (追記ここまで)(追記) RFC6931 (追記ここまで) (追記) ], but (追記ここまで)(追記) MAY (追記ここまで)(追記) compute the requisite values through any technique that leads to the same output. (追記ここまで)

(追記) Examples of items in various namespaces include: (追記ここまで)

SignatureProperties is identified and defined by (削除) this specification's (削除ここまで) (追記) the (追記ここまで)(追記) disg: (追記ここまで) namespace
(削除) http://www.w3.org/2000/09/xmldsig# SignatureProperties (削除ここまで) (追記) http://www.w3.org/2000/09/xmldsig#SignatureProperties (追記ここまで)
(追記) ECKeyValue (追記ここまで)(追記) is identified and defined by the (追記ここまで)(追記) dsig11: (追記ここまで)(追記) namespace (追記ここまで)
(追記) http://www.w3.org/2009/xmldsig11#ECKeyValue (追記ここまで)
XSLT is identified and defined by an external URI
http://www.w3.org/TR/1999/REC-xslt-19991116
SHA1 is identified via this specification's namespace and defined via a normative reference (追記) [ (追記ここまで)(追記) FIPS-180-3 (追記ここまで) (追記) ] (追記ここまで)
(削除) http://www.w3.org/2000/09/xmldsig#sha1 (削除ここまで) (追記) http://www.w3.org/2001/04/xmlenc#sha256 (追記ここまで)
FIPS PUB (削除) 180-2. (削除ここまで) (追記) 180-3. (追記ここまで) Secure Hash Standard. U.S. Department of Commerce/National Institute of Standards and Technology.

(削除) Finally, in order to provide (削除ここまで) (追記) No provision is made (追記ここまで) for (削除) terse (削除ここまで) (追記) an explicit version number in this syntax. If a future version of this specification requires explicit versioning of the document format, a different (追記ここまで) namespace (削除) declarations we sometimes use XML internal entities [ XML ] within URIs. For instance: (削除ここまで) (追記) will be used. (追記ここまで)

(削除) <?xml version='1.0'?> <!DOCTYPE Signature SYSTEM "xmldsig-core-schema.dtd" [ <!ENTITY dsig "http://www.w3.org/2000/09/xmldsig#"> ]> <Signature xmlns="&dsig;" Id="MyFirstSignature"> <SignedInfo> ... (削除ここまで)

1.4 Acknowledgements

The contributions of the (削除) following (削除ここまで) (追記) members of the XML Signature (追記ここまで) Working Group (削除) members (削除ここまで) to (削除) this (削除ここまで) (追記) the first edition (追記ここまで) specification are gratefully acknowledged: Mark Bartel, Adobe, was Accelio (削除) (Author) (削除ここまで) (追記) (Author); (追記ここまで) John Boyer, IBM (削除) (Author) (削除ここまで) (追記) (Author); (追記ここまで) Mariano P. Consens, University of (削除) Waterloo (削除ここまで) (追記) Waterloo; (追記ここまで) John Cowan, Reuters (削除) Health (削除ここまで) (追記) Health; (追記ここまで) Donald Eastlake 3rd, Motorola (Chair, (削除) Author/Editor) (削除ここまで) (追記) Author/Editor); (追記ここまで) Barb Fox, Microsoft (削除) (Author) (削除ここまで) (追記) (Author); (追記ここまで) Christian Geuer-Pollmann, University (削除) Siegen (削除ここまで) (追記) Siegen; (追記ここまで) Tom Gindin, (削除) IBM (削除ここまで) (追記) IBM; (追記ここまで) Phillip Hallam-Baker, VeriSign (削除) Inc (削除ここまで) (追記) Inc; (追記ここまで) Richard Himes, US (削除) Courts (削除ここまで) (追記) Courts; (追記ここまで) Merlin Hughes, (削除) Baltimore (削除ここまで) (追記) Baltimore; (追記ここまで) Gregor Karlinger, IAIK TU (削除) Graz (削除ここまで) (追記) Graz; (追記ここまで) Brian LaMacchia, Microsoft (削除) (Author) (削除ここまで) (追記) (Author); (追記ここまで) Peter Lipp, IAIK TU (削除) Graz (削除ここまで) (追記) Graz; (追記ここまで) Joseph Reagle, NYU, was W3C (Chair, (削除) Author/Editor) (削除ここまで) (追記) Author/Editor); (追記ここまで) Ed Simon, XMLsec (削除) (Author) (削除ここまで) (追記) (Author); (追記ここまで) David Solo, Citigroup (削除) (Author/Editor) (削除ここまで) (追記) (Author/Editor); (追記ここまで) Petteri Stenius, (削除) Capslock (削除ここまで) (追記) Capslock; (追記ここまで) Raghavan Srinivas, (削除) Sun (削除ここまで) (追記) Sun; (追記ここまで) Kent Tamura, (削除) IBM (削除ここまで) (追記) IBM; (追記ここまで) Winchel Todd Vincent III, (削除) GSU (削除ここまで) (追記) GSU; (追記ここまで) Carl Wallace, Corsec Security, (削除) Inc. (削除ここまで) (追記) Inc.; (追記ここまで) Greg Whitehead, Signio Inc.

As are the (追記) first edition (追記ここまで) Last Call comments from the following:

The following members of the XML Security Specification Maintenance Working Group contributed to the second edition: Juan Carlos Cruellas, Universitat (削除) Politècnica (削除ここまで) (追記) Politècnica (追記ここまで) de (削除) Catalunya (削除ここまで) (追記) Catalunya; (追記ここまで) Pratik Datta, Oracle (削除) Corporation (削除ここまで) (追記) Corporation; (追記ここまで) Phillip Hallam-Baker, VeriSign, (削除) Inc. (削除ここまで) (追記) Inc.; (追記ここまで) Frederick Hirsch, Nokia, (Chair, (削除) Editor) (削除ここまで) (追記) Editor); (追記ここまで) Konrad Lanz, (削除) A-SIT (削除ここまで) (追記) Applied Information processing and Kommunications (IAIK); (追記ここまで) Hal Lockhart, BEA Systems, (削除) Inc. (削除ここまで) (追記) Inc.; (追記ここまで) Robert Miller, MITRE (削除) Corporation (削除ここまで) (追記) Corporation; (追記ここまで) Sean Mullan, Sun Microsystems, (削除) Inc. (削除ここまで) (追記) Inc.; (追記ここまで) Bruce Rich, IBM (削除) Corporation (削除ここまで) (追記) Corporation; (追記ここまで) Thomas Roessler, (削除) W3C/ERCIM, (削除ここまで) (追記) W3C (追記ここまで)(追記) / (追記ここまで)(追記) ERCIM (追記ここまで), (Staff contact, (削除) Editor) (削除ここまで) (追記) Editor); (追記ここまで) Ed Simon, W3C Invited (削除) Expert (削除ここまで) (追記) Expert; (追記ここまで) Greg Whitehead, (削除) HP (削除ここまで) (追記) HP. (追記ここまで)

(追記) Contributions for version 1.1 were received from the members of the XML Security Working Group: Scott Cantor, Juan Carlos Cruellas, Pratik Datta, Gerald Edgar, Ken Graf, Phillip Hallam-Baker, Brad Hill, Frederick Hirsch (Chair, Editor), Brian LaMacchia, Konrad Lanz, Hal Lockhart, Cynthia Martin, Rob Miller, Sean Mullan, Shivaram Mysore, Magnus Nyström, Bruce Rich, Thomas Roessler (Staff contact, Editor), Ed Simon, Chris Solc, John Wray, Kelvin Yiu (Editor). (追記ここまで)

(追記) The Working Group thanks Makoto Murata for assistance with the RELAX NG schemas. (追記ここまで)

(削除) 2.0 (削除ここまで) (追記) 2. (追記ここまで) Signature Overview and Examples

This section provides an overview and examples of XML digital signature syntax. The specific processing is given in (追記) section 3. (追記ここまで) Processing Rules (削除) (section 3). (削除ここまで) . The formal syntax is found in (追記) section 4. (追記ここまで) Core Signature Syntax (削除) (section 4) (削除ここまで) and (追記) section 5. (追記ここまで) Additional Signature Syntax (削除) (section 5). (削除ここまで) .

In this section, an informal representation and examples are used to describe the structure of the XML signature syntax. This representation and examples may omit attributes, details and potential features that are fully explained later.

XML Signatures are applied to arbitrary digital content (data objects) via an indirection. Data objects are digested, the resulting value is placed in an element (with other information) and that element is then digested and cryptographically signed. XML digital signatures are represented by the Signature element which has the following structure (where "?" denotes zero or one occurrence; "+" denotes one or more occurrences; and "*" denotes zero or more occurrences):

(削除) <Signature ID?> <SignedInfo> <CanonicalizationMethod/> <SignatureMethod/> (<Reference URI? > (<Transforms>)? <DigestMethod> <DigestValue> </Reference>)+ </SignedInfo> <SignatureValue> (<KeyInfo>)? (<Object ID?>)* </Signature> (削除ここまで)
Example 1
<SignatureID?><SignedInfo><CanonicalizationMethod/><SignatureMethod/>
(追記) (<ReferenceURI? >
 (<Transforms>)?
 (追記ここまで) <DigestMethod><DigestValue></Reference>)+ </SignedInfo><SignatureValue> (追記) 
 (<KeyInfo>)?
 (<ObjectID?>)*
 (追記ここまで)(追記) 
</Signature>
 (追記ここまで)

Signatures are related to data objects via URIs [ URI ]. Within an XML document, signatures are related to local data objects via fragment identifiers. Such local data can be included within an enveloping signature or can enclose an enveloped signature. Detached signatures are over external network resources or local data objects that reside within the same XML document as sibling elements; in this case, the signature is neither enveloping (signature is parent) nor enveloped (signature is child). Since a Signature element (and its Id attribute value/name) may co-exist or be combined with other elements (and their IDs) within a single XML document, care should be taken in choosing names such that there are no subsequent collisions that violate the ID uniqueness validity constraint [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ].

2.1 Simple Example ( Signature , SignedInfo , Methods , and Reference (削除) )s (削除ここまで) (追記) s) (追記ここまで)

The following example is a detached signature of the content of the HTML4 in XML specification.

(削除) [s01] <Signature Id="MyFirstSignature" xmlns="http://www.w3.org/2000/09/xmldsig#"> [s02] <SignedInfo> [s03] <CanonicalizationMethod Algorithm="http://www.w3.org/2006/12/xml-c14n11"/> [s04] <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/> [s05] <Reference URI="http://www.w3.org/TR/2000/REC-xhtml1-20000126/"> [s06] <Transforms> [s07] <Transform Algorithm="http://www.w3.org/2006/12/xml-c14n11"/> [s08] </Transforms> [s09] <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> [s10] <DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK.../DigestValue> [s11] </Reference> [s12] </SignedInfo> [s13] <SignatureValue>...</SignatureValue> [s14] <KeyInfo> [s15a] <KeyValue> [s15b] <DSAKeyValue> [s15c] <P>...</P><Q>...</Q><G>...</G><Y>...</Y> [s15d] </DSAKeyValue> [s15e] </KeyValue> [s16] </KeyInfo> [s17] </Signature> (削除ここまで)
Example 2
[s01]<SignatureId="MyFirstSignature" xmlns="http://www.w3.org/2000/09/xmldsig#">[s02]<SignedInfo>[s03]<CanonicalizationMethodAlgorithm="http://www.w3.org/2006/12/xml-c14n11"/>[s04]<SignatureMethodAlgorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/>[s05]<Reference URI="http://www.w3.org/TR/2000/REC-xhtml1-20000126/">[s06]<Transforms>[s07]<TransformAlgorithm="http://www.w3.org/2006/12/xml-c14n11"/>[s08]</Transforms> 
(追記) [s09] <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> 
 (追記ここまで)[s10]<DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...</DigestValue>[s11]</Reference> (追記) 
[s12] </SignedInfo> 
 (追記ここまで)[s13]<SignatureValue>...</SignatureValue>[s14]<KeyInfo>[s15a]<KeyValue>[s15b]<DSAKeyValue>[s15c]<P>...</P><Q>...</Q><G>...</G><Y>...</Y>[s15d]</DSAKeyValue> (追記) 
[s15e] </KeyValue> 
 (追記ここまで)[s16]</KeyInfo> (追記) 
[s17]
</
 (追記ここまで)(追記) 
Signature
 (追記ここまで)(追記) 
>
 (追記ここまで)

[s02-12] The required SignedInfo element is the information that is actually signed. Core validation of SignedInfo consists of two mandatory processes: validation of the signature over SignedInfo and validation of each Reference digest within SignedInfo . Note that the algorithms used in calculating the SignatureValue are also included in the signed information while the SignatureValue element is outside SignedInfo .

[s03] The CanonicalizationMethod is the algorithm that is used to canonicalize the SignedInfo element before it is digested as part of the signature operation. Note that this (削除) example, and all (削除ここまで) (追記) example is not in canonical form. (None of the (追記ここまで) examples in this (削除) specification, (削除ここまで) (追記) specification (追記ここまで) are (削除) not (削除ここまで) in canonical (削除) form. (削除ここまで) (追記) form.) (追記ここまで)

[s04] The SignatureMethod is the algorithm that is used to convert the canonicalized SignedInfo into the SignatureValue . It is a combination of a digest algorithm and a key dependent algorithm and possibly other algorithms such as padding, for example RSA-SHA1. The algorithm names are signed to resist attacks based on substituting a weaker algorithm. To promote application interoperability we specify a set of signature algorithms that MUST be implemented, though their use is at the discretion of the signature creator. We specify additional algorithms as RECOMMENDED or OPTIONAL for implementation; the design also permits arbitrary user specified algorithms.

[s05-11] Each Reference element includes the digest method and resulting digest value calculated over the identified data object. It also may include transformations that produced the input to the digest operation. A data object is signed by computing its digest value and a signature over that value. The signature is later checked via reference and signature validation .

[s14-16] KeyInfo indicates the key to be used to validate the signature. Possible forms for identification include certificates, key names, and key agreement algorithms and information -- we define only a few. KeyInfo is optional for two reasons. First, the signer may not wish to reveal key information to all document processing parties. Second, the information may be known within the application's context and need not be represented explicitly. Since KeyInfo is outside of SignedInfo , if the signer wishes to bind the keying information to the signature, a Reference can easily identify and include the KeyInfo as part of the signature. (追記) Use of (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) is optional, however note that senders and receivers must agree on how it will be used through a mechanism out of scope for this specification. (追記ここまで)

2.1.1 More on Reference

Example 3
[s05]<Reference URI="http://www.w3.org/TR/2000/REC-xhtml1-20000126/">[s06]<Transforms>[s07]<TransformAlgorithm="http://www.w3.org/2006/12/xml-c14n11"/>[s08]</Transforms> 
(追記) [s09] <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> 
 (追記ここまで)[s10]<DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...</DigestValue>(追記) 
[
 (追記ここまで)(追記) 
s11
 (追記ここまで)(追記) 
]
 (追記ここまで)(追記) 
</
 (追記ここまで)(追記) 
Reference
 (追記ここまで)(追記) 
>
 (追記ここまで)
(削除) 
 [s05] <Reference URI="http://www.w3.org/TR/2000/REC-xhtml1-20000126/"> 
 [s06] <Transforms> 
 [s07] <Transform Algorithm="http://www.w3.org/2006/12/xml-c14n11"/> 
 [s08] </Transforms> 
 [s09] <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> 
 [s10] <DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...</DigestValue> 
 [s11] </Reference>
 (削除ここまで)

[s05] The optional URI attribute of Reference identifies the data object to be signed. This attribute may be omitted on at most one Reference in a Signature . (This limitation is imposed in order to ensure that references and objects may be matched unambiguously.)

[s05-08] This identification, along with the transforms, is a description provided by the signer on how they obtained the signed data object in the form it was digested (i.e. the digested content). The verifier may obtain the digested content in another method so long as the digest verifies. In particular, the verifier may obtain the content from a different location such as a local store than that specified in the URI .

[s06-08] Transforms is an optional ordered list of processing steps that were applied to the resource's content before it was digested. Transforms can include operations such as canonicalization, encoding/decoding (including compression/inflation), XSLT, XPath, XML schema validation, or XInclude. XPath transforms permit the signer to derive an XML document that omits portions of the source document. Consequently those excluded portions can change without affecting signature validity. For example, if the resource being signed encloses the signature itself, such a transform must be used to exclude the signature value from its own computation. If no Transforms element is present, the resource's content is digested directly. While the Working Group has specified mandatory (and optional) canonicalization and decoding algorithms, user specified transforms are permitted.

[s09-10] DigestMethod is the algorithm applied to the data after Transforms is applied (if specified) to yield the DigestValue . The signing of the DigestValue is what binds (削除) a resources (削除ここまで) (追記) the (追記ここまで) content (追記) of a resource (追記ここまで) to the signer's key.

2.2 Extended Example ( Object and SignatureProperty )

This specification does not address mechanisms for making statements or assertions. Instead, this document defines what it means for something to be signed by an XML Signature ( integrity , message authentication , and/or signer authentication ). Applications that wish to represent other semantics must rely upon other technologies, such as [ (削除) XML , RDF (削除ここまで) (追記) XML10 (追記ここまで) (追記) ], [ (追記ここまで)(追記) RDF-PRIMER (追記ここまで) ]. For instance, an application might use a foo:assuredby attribute within its own markup to reference a Signature element. Consequently, it's the application that must understand and know how to make trust decisions given the validity of the signature and the meaning of assuredby syntax. We also define a SignatureProperties element type for the inclusion of assertions about the signature itself (e.g., signature semantics, the time of signing or the serial number of hardware used in cryptographic processes). Such assertions may be signed by including a Reference for the SignatureProperties in SignedInfo . While the signing application should be very careful about what it signs (it should understand what is in the SignatureProperty ) a receiving application has no obligation to understand that semantic (though its parent trust engine may wish to). Any content about the signature generation may be located within the SignatureProperty element. The mandatory Target attribute references the Signature element to which the property applies.

Consider the preceding example with an additional reference to a local Object that includes a SignatureProperty element. (Such a signature would not only be detached [p02] but enveloping [p03] .)

(削除) [ ] <Signature Id="MySecondSignature" ...> [p01] <SignedInfo> [ ] ... [p02] <Reference URI="http://www.w3.org/TR/xml-stylesheet/"> [ ] ... [p03] <Reference URI="#AMadeUpTimeStamp" [p04] Type="http://www.w3.org/2000/09/xmldsig#SignatureProperties"> [p05] <Transforms> [p06] <Transform Algorithm="http://www.w3.org/2006/12/xml-c14n11"/> [p07] </Transforms> [p08] <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> [p09] <DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...</DigestValue> [p10] </Reference> [p11] </SignedInfo> [p12] ... [p13] <Object> [p14] <SignatureProperties> [p15] <SignatureProperty Id="AMadeUpTimeStamp" Target="#MySecondSignature"> [p16] <timestamp xmlns="http://www.ietf.org/rfcXXXX.txt"> [p17] <date>19990914</date> [p18] <time>14:34:34:34</time> [p19] </timestamp> [p20] </SignatureProperty> [p21] </SignatureProperties> [p22] </Object> [p23]</Signature> (削除ここまで)
Example 4
[]<SignatureId="MySecondSignature"...>[p01]<SignedInfo>[]...[p02]<Reference URI="http://www.w3.org/TR/xml-stylesheet/">[]...[p03]<Reference URI="#AMadeUpTimeStamp"[p04]Type="http://www.w3.org/2000/09/xmldsig#SignatureProperties">[p05]<Transforms>[p06]<TransformAlgorithm="http://www.w3.org/2006/12/xml-c14n11"/>[p07]</Transforms> 
(追記) [p08] <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> 
 (追記ここまで)[p09]<DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...</DigestValue>[p10]</Reference> (追記) 
[p11] </SignedInfo> 
 (追記ここまで)[p12]...[p13]<Object>[p14]<SignatureProperties>[p15]<SignaturePropertyId="AMadeUpTimeStamp"Target="#MySecondSignature">[p16]<timestamp xmlns="http://www.ietf.org/rfcXXXX.txt">[p17]<date>19990914</date> (追記) 
[p18] <time>14:34:34:34</time> 
 (追記ここまで)[p19]</timestamp> (追記) 
[p20] </SignatureProperty> 
 (追記ここまで)[p21]</SignatureProperties> (追記) 
[p22] </Object> 
 (追記ここまで)(追記) 
[
 (追記ここまで)(追記) 
p23
 (追記ここまで)(追記) 
]</
 (追記ここまで)(追記) 
Signature
 (追記ここまで)(追記) 
>
 (追記ここまで)

[p04] The optional Type attribute of Reference provides information about the resource identified by the URI . In particular, it can indicate that it is an Object , SignatureProperty , or Manifest element. This can be used by applications to initiate special processing of some Reference elements. References to an XML data element within an Object element SHOULD identify the actual element pointed to. Where the element content is not XML (perhaps it is binary or encoded data) the reference should identify the Object and the Reference Type , if given, SHOULD indicate Object . Note that Type is advisory and no action based on it or checking of its correctness is required by core behavior.

[p13] Object is an optional element for including data objects within the signature element or elsewhere. The Object can be optionally typed and/or encoded.

[p14-21] Signature properties, such as time of signing, can be optionally signed by identifying them from within a Reference . (These properties are traditionally called signature "attributes" although that term has no relationship to the XML term "attribute".)

2.3 Extended Example ( Object and Manifest )

The Manifest element is provided to meet additional requirements not directly addressed by the mandatory parts of this specification. Two requirements and the way the Manifest satisfies them follow.

First, applications frequently need to efficiently sign multiple data objects even where the signature operation itself is an expensive public key signature. This requirement can be met by including multiple Reference elements within SignedInfo since the inclusion of each digest secures the data digested. However, some applications may not want the core validation behavior associated with this approach because it requires every Reference within SignedInfo to undergo reference validation -- the DigestValue elements are checked. These applications may wish to reserve reference validation decision logic to themselves. For example, an application might receive a signature valid SignedInfo element that includes three Reference elements. If a single Reference fails (the identified data object when digested does not yield the specified DigestValue ) the signature would fail core validation . However, the application may wish to treat the signature over the two valid Reference elements as valid or take different actions depending on which fails. To accomplish this, SignedInfo would reference a Manifest element that contains one or more Reference elements (with the same structure as those in SignedInfo ). Then, reference validation of the Manifest is under application control.

Second, consider an application where many signatures (using different keys) are applied to a large number of documents. An inefficient solution is to have a separate signature (per key) repeatedly applied to a large SignedInfo element (with many Reference s); this is wasteful and redundant. A more efficient solution is to include many references in a single Manifest that is then referenced from multiple Signature elements.

The example below includes a Reference that signs a Manifest found within the Object element.

(削除) [ ] ... [m01] <Reference URI="#MyFirstManifest" [m02] Type="http://www.w3.org/2000/09/xmldsig#Manifest"> [m03] <Transforms> [m04] <Transform Algorithm="http://www.w3.org/2006/12/xml-c14n11"/> [m05] </Transforms> [m06] <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> [m07] <DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...=</DigestValue> [m08] </Reference> [ ] ... [m09] <Object> [m10] <Manifest Id="MyFirstManifest"> [m11] <Reference> [m12] ... [m13] </Reference> [m14] <Reference> [m15] ... [m16] </Reference> [m17] </Manifest> [m18] </Object> (削除ここまで)
Example 5
[]...[m01]<Reference URI="#MyFirstManifest"[m02]Type="http://www.w3.org/2000/09/xmldsig#Manifest">[m03]<Transforms>[m04]<TransformAlgorithm="http://www.w3.org/2006/12/xml-c14n11"/>[m05]</Transforms> 
(追記) [m06] <DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/> 
 (追記ここまで)[m07]<DigestValue>dGhpcyBpcyBub3QgYSBzaWduYXR1cmUK...=</DigestValue>[m08]</Reference> (追記) 
[ ] ...
[m09] <Object>
[m10] <Manifest Id="MyFirstManifest">
[m11] <Reference>
[m12] ...
[m13] </Reference> 
 (追記ここまで)[m14]<Reference>[m15]...[m16]</Reference>(追記) 
[m17] </Manifest>
 (追記ここまで)(追記) 
[
 (追記ここまで)(追記) 
m18
 (追記ここまで)(追記) 
]
 (追記ここまで)(追記) 
</
 (追記ここまで)(追記) 
Object
 (追記ここまで)(追記) 
>
 (追記ここまで)

(削除) 3.0 (削除ここまで) (追記) 3. (追記ここまで) Processing Rules

The sections below describe the operations to be performed as part of signature generation and validation.

3.1 (削除) Core (削除ここまで) (追記) Signature (追記ここまで) Generation

The REQUIRED steps include the generation of Reference elements and the SignatureValue over SignedInfo .

3.1.1 Reference Generation

For each data object being signed:

  1. Apply the Transforms , as determined by the application, to the data object.
  2. Calculate the digest value over the resulting data object.
  3. Create a Reference element, including the (optional) identification of the data object, any (optional) transform elements, the digest algorithm and the DigestValue . (Note, it is the canonical form of these references that are signed in (追記) section (追記ここまで) 3.1.2 (追記) Signature Generation (追記ここまで) and validated in (追記) section (追記ここまで) 3.2.1 (削除) .) (削除ここまで) (追記) Reference Validation (追記ここまで).)
The (追記) Reference Processing Model ( (追記ここまで)(追記) section 4.4.3.2 The (追記ここまで) Reference Processing Model (削除) (section 4.3.3.2) (削除ここまで) (追記) ) (追記ここまで) requires use of Canonical XML 1.0 [ XML-C14N ] as default processing behavior when a transformation is expecting an octet-stream, but the data object resulting from URI dereferencing or from the previous transformation in the list of Transform elements is a node-set. We RECOMMEND that, when generating signatures, signature applications do not rely on this default behavior, but explicitly identify the transformation that is applied to perform this mapping. In cases in which inclusive canonicalization is desired, we RECOMMEND that Canonical XML 1.1 [ XML-C14N11 ] be used.

3.1.2 Signature Generation

  1. Create SignedInfo element with SignatureMethod , CanonicalizationMethod and Reference (s).
  2. Canonicalize and then calculate the SignatureValue over SignedInfo based on algorithms specified in SignedInfo .
  3. Construct the Signature element that includes SignedInfo , Object (s) (if desired, encoding may be different than that used for signing), KeyInfo (if required), and SignatureValue .

    Note, if the Signature includes same-document references, [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ] or [ (削除) XML-schema (削除ここまで) (追記) XMLSCHEMA-1 (追記ここまで) (追記) ], [ (追記ここまで)(追記) XMLSCHEMA-2 (追記ここまで) ] validation of the document might introduce changes that break the signature. Consequently, applications should be careful to consistently process the document or refrain from using external contributions (e.g., defaults and entities).

3.2 Core Validation

The REQUIRED steps of core validation include (1) reference validation , the verification of the digest contained in each Reference in SignedInfo , and (2) the cryptographic signature validation of the signature calculated over SignedInfo .

Note, there may be valid signatures that some signature applications are unable to validate. Reasons for this include failure to implement optional parts of this specification, inability or unwillingness to execute specified algorithms, or inability or unwillingness to dereference specified URIs (some URI schemes may cause undesirable side effects), etc.

Comparison of (削除) values (削除ここまで) (追記) each value (追記ここまで) in reference and signature validation (削除) are (削除ここまで) (追記) is (追記ここまで) over the numeric (e.g., integer) or decoded octet sequence of the value. Different implementations may produce different encoded digest and signature values when processing the same resources because of variances in their encoding, such as accidental white space. But if one uses numeric or octet comparison (choose one) on both the stated and computed values these problems are eliminated.

3.2.1 Reference Validation

  1. Canonicalize the SignedInfo element based on the CanonicalizationMethod in SignedInfo .
  2. For each Reference in SignedInfo :
    1. Obtain the data object to be digested. (For example, the signature application may dereference the URI and execute Transforms provided by the signer in the Reference element, or it may obtain the content through other means such as a local cache.)
    2. Digest the resulting data object using the DigestMethod specified in its Reference specification.
    3. Compare the generated digest value against DigestValue in the SignedInfo Reference ; if there is any mismatch, validation fails.

Note, SignedInfo is canonicalized in step 1. The application must ensure that the CanonicalizationMethod has no dangerous side (削除) affects, (削除ここまで) (追記) effects, (追記ここまで) such as rewriting URIs, (see (削除) CanonicalizationMethod (削除ここまで) (追記) note on Canonicalization Method (追記ここまで) (削除) (section 4.3)) (削除ここまで) (追記) ) (追記ここまで) and that it Sees What is Signed , which is the canonical form.

(追記) Note, After a (追記ここまで)(追記) Signature (追記ここまで)(追記) element has been created in Signature Generation for a signature with a same document reference, an implementation can serialize the XML content with variations in that serialization. This means that Reference Validation needs to canonicalize the XML document before digesting in step 1 to avoid issues related to variations in serialization. (追記ここまで)

3.2.2 Signature Validation

  1. Obtain the keying information from KeyInfo or from an external source.
  2. Obtain the canonical form of the SignatureMethod using the CanonicalizationMethod and use the result (and previously obtained KeyInfo ) to confirm the SignatureValue over the SignedInfo element.

Note, KeyInfo (or some transformed version thereof) may be signed via a Reference element. Transformation and validation of this reference (3.2.1) is orthogonal to Signature Validation which uses the KeyInfo as parsed.

Additionally, the SignatureMethod URI may have been altered by the canonicalization of SignedInfo (e.g., absolutization of relative URIs) and it is the canonical form that MUST be used. However, the required canonicalization [ XML-C14N ] of this specification does not change URIs.

(削除) 4.0 (削除ここまで) (追記) 4. (追記ここまで) Core Signature Syntax

The general structure of an XML signature is described in (追記) section 2. (追記ここまで) Signature Overview (削除) (section 2). (削除ここまで) (追記) and Examples (追記ここまで). This section provides detailed syntax of the core signature features. Features described in this section are mandatory to implement unless otherwise indicated. The syntax is defined via (削除) DTDs and (削除ここまで) (追記) an (追記ここまで) [ (削除) XML-Schema (削除ここまで) (追記) XMLSCHEMA-1 (追記ここまで) (追記) ][ (追記ここまで)(追記) XMLSCHEMA-2 (追記ここまで) ] with the following XML preamble, declaration, and internal entity.

(削除) Schema Definition: (削除ここまで)
(削除) <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE schema PUBLIC "-//W3C//DTD XMLSchema 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd" [ <!ATTLIST schema xmlns:ds CDATA #FIXED "http://www.w3.org/2000/09/xmldsig#"> <!ENTITY dsig 'http://www.w3.org/2000/09/xmldsig#'> <!ENTITY % p ''> <!ENTITY % s ''> ]> (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <schema xmlns="http://www.w3.org/2001/XMLSchema"
 xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
 targetNamespace="http://www.w3.org/2000/09/xmldsig#"
 version="0.1" elementFormDefault="qualified">
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!-- (削除ここまで) 
(削除) The following entity declarations enable external/flexible content in
 the Signature content model.
 (削除ここまで)

(追記) <?
 (追記ここまで)
(削除) #PCDATA emulates schema:string; when combined with element types it
 emulates schema mixed="true".
 (削除ここまで)

(追記) xml
version
 (追記ここまで)
(削除) %foo.ANY permits the user to include their own element types from
 other namespaces, for example:
 <!ENTITY % KeyValue.ANY '| ecds:ECDSAKeyValue'>
 ...
 <!ELEMENT ecds:ECDSAKeyValue (#PCDATA) >
 (削除ここまで)

(追記) =
 (追記ここまで)
(削除) -->
 (削除ここまで)

(追記) "1.0"
 (追記ここまで)(追記) 
encoding
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"utf-8"
 (追記ここまで)(追記) 
?>
 (追記ここまで)(追記) 
<!DOCTYPE
schema
PUBLIC
"-//W3C//DTD
XMLSchema
200102//EN"
[
<!ATTLIST
schema
xmlns:ds
CDATA
#FIXED
"http://www.w3.org/2000/09/xmldsig#">
 (追記ここまで)(追記) 
<!ENTITY
dsig
'http://www.w3.org/2000/09/xmldsig#'>
 (追記ここまで)(追記) 
<!ENTITY
%
p
''>
 (追記ここまで)(追記) 
<!ENTITY
%
s
''>
 (追記ここまで)(追記) 
]>
 (追記ここまで)(追記) 
<schema
 (追記ここまで)(追記) 
xmlns
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2001/XMLSchema"
 (追記ここまで)(追記) 
xmlns:ds
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2000/09/xmldsig#"
 (追記ここまで)(追記) 
targetNamespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2000/09/xmldsig#"
 (追記ここまで)(追記) 
version
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0.1"
 (追記ここまで)(追記) 
elementFormDefault
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"qualified"
 (追記ここまで)(追記) 
>
 (追記ここまで)
(削除) <!ENTITY % Object.ANY ''>
 <!ENTITY % Method.ANY ''>
 <!ENTITY % Transform.ANY ''>
 <!ENTITY % SignatureProperty.ANY ''>
 <!ENTITY % KeyInfo.ANY ''>
 <!ENTITY % KeyValue.ANY ''>
 <!ENTITY % PGPData.ANY ''>
 <!ENTITY % X509Data.ANY ''>
 <!ENTITY % SPKIData.ANY ''>
 (削除ここまで)
(削除) 4.0.1 (削除ここまで)

(追記) Additional markup defined in version 1.1 of this specification uses the (追記ここまで)(追記) dsig11: (追記ここまで)(追記) namespace. (追記ここまで) The (削除) ds: CryptoBinary (削除ここまで) (追記) syntax is defined in an XML schema with the following preamble: (追記ここまで)

(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<?
 (追記ここまで)(追記) 
xml
version
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"1.0"
 (追記ここまで)(追記) 
encoding
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"utf-8"
 (追記ここまで)(追記) 
?>
 (追記ここまで)(追記) 
<!DOCTYPE
schema
PUBLIC
"-//W3C//DTD
XMLSchema
200102//EN"
[
<!ENTITY
dsig
'http://www.w3.org/2000/09/xmldsig#'>
 (追記ここまで)(追記) 
<!ENTITY
dsig11
'http://www.w3.org/2009/xmldsig11#'>
 (追記ここまで)(追記) 
<!ENTITY
%
p
''>
 (追記ここまで)(追記) 
<!ENTITY
%
s
''>
 (追記ここまで)(追記) 
]>
 (追記ここまで)(追記) 
<schema
 (追記ここまで)(追記) 
xmlns
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2001/XMLSchema"
 (追記ここまで)(追記) 
xmlns:ds
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2000/09/xmldsig#"
 (追記ここまで)(追記) 
xmlns:dsig11
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2009/xmldsig11#"
 (追記ここまで)(追記) 
targetNamespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2009/xmldsig11#"
 (追記ここまで)(追記) 
version
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0.1"
 (追記ここまで)(追記) 
elementFormDefault
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"qualified"
 (追記ここまで)(追記) 
>
 (追記ここまで)

(追記) 4.1 (追記ここまで)(追記) The (追記ここまで)(追記) ds:CryptoBinary (追記ここまで) Simple Type

This specification defines the ds:CryptoBinary simple type for representing arbitrary-length integers (e.g. "bignums") in XML as octet strings. The integer value is first converted to a "big endian" bitstring. The bitstring is then padded with leading zero bits so that the total number of bits == 0 mod 8 (so that there are an integral number of octets). If the bitstring contains entire leading octets that are zero, these are removed (so the high-order octet is always non-zero). This octet string is then base64 [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ] encoded. (The conversion from integer to octet string is equivalent to IEEE 1363's I2OSP [ (削除) 1363 (削除ここまで) (追記) IEEE1363 (追記ここまで) ] with minimal length).

This type is used by "bignum" values such as RSAKeyValue and DSAKeyValue . If a value can be of type base64Binary or ds:CryptoBinary they are defined as base64Binary . For example, if the signature algorithm is RSA or DSA then SignatureValue represents a bignum and could be ds:CryptoBinary . However, if HMAC-SHA1 is the signature algorithm then SignatureValue could have leading zero octets that must be preserved. Thus SignatureValue is generically defined as of type base64Binary .

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <simpleType name="CryptoBinary">
 <restriction base="base64Binary">
 </restriction>
 </simpleType>
 (削除ここまで)


(追記) <simpleType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"CryptoBinary"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<restriction
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</simpleType>
 (追記ここまで)

(削除) 4.1 The (削除ここまで) (追記) 4.2 (追記ここまで)(追記) The (追記ここまで) Signature element

The Signature element is the root element of an XML Signature. Implementation MUST generate laxly schema valid [ (削除) XML-schema (削除ここまで) (追記) XMLSCHEMA-1 (追記ここまで) (追記) ][ (追記ここまで)(追記) XMLSCHEMA-2 (追記ここまで) ] Signature elements as specified by the following schema:

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="Signature" type="ds:SignatureType"/>
 <complexType name="SignatureType">
 <sequence> 
 <element ref="ds:SignedInfo"/> 
 <element ref="ds:SignatureValue"/> 
 <element ref="ds:KeyInfo" minOccurs="0"/> 
 <element ref="ds:Object" minOccurs="0" maxOccurs="unbounded"/> 
 </sequence> 
 <attribute name="Id" type="ID" use="optional"/>
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT Signature (SignedInfo, SignatureValue, KeyInfo?, Object*) > <!ATTLIST Signature xmlns CDATA #FIXED 'http://www.w3.org/2000/09/xmldsig#' Id ID #IMPLIED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Signature"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignatureType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignedInfo"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignatureValue"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:KeyInfo"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:Object"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.2 The (削除ここまで) (追記) 4.3 (追記ここまで)(追記) The (追記ここまで) SignatureValue Element

The SignatureValue element contains the actual value of the digital signature; it is always encoded using base64 [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ]. (削除) While we identify two SignatureMethod algorithms, one mandatory and one optional to implement, user specified algorithms may be used as well. (削除ここまで)

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="SignatureValue" type="ds:SignatureValueType"/> 
 <complexType name="SignatureValueType">
 <simpleContent>
 <extension base="base64Binary">
 <attribute name="Id" type="ID" use="optional"/>
 </extension>
 </simpleContent>
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT SignatureValue (#PCDATA) > <!ATTLIST SignatureValue Id ID #IMPLIED> (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignatureValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureValueType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<simpleContent>
 (追記ここまで)(追記) 
<extension
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</extension>
 (追記ここまで)(追記) 
</simpleContent>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.3 The (削除ここまで) (追記) 4.4 (追記ここまで)(追記) The (追記ここまで) SignedInfo Element

The structure of SignedInfo includes the canonicalization algorithm, a signature algorithm, and one or more references. The SignedInfo element may contain an optional ID attribute that will allow it to be referenced by other signatures and objects.

SignedInfo does not include explicit signature or digest properties (such as calculation time, cryptographic device serial number, etc.). If an application needs to associate properties with the signature or digest, it may include such information in a SignatureProperties element within an Object element.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="SignedInfo" type="ds:SignedInfoType"/> 
 <complexType name="SignedInfoType">
 <sequence> 
 <element ref="ds:CanonicalizationMethod"/>
 <element ref="ds:SignatureMethod"/> 
 <element ref="ds:Reference" maxOccurs="unbounded"/> 
 </sequence> 
 <attribute name="Id" type="ID" use="optional"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT SignedInfo (CanonicalizationMethod, SignatureMethod, Reference+) > <!ATTLIST SignedInfo Id ID #IMPLIED (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignedInfo"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignedInfoType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignedInfoType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CanonicalizationMethod"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignatureMethod"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:Reference"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.3.1 The (削除ここまで) (追記) 4.4.1 (追記ここまで)(追記) The (追記ここまで) CanonicalizationMethod Element

CanonicalizationMethod is a required element that specifies the canonicalization algorithm applied to the SignedInfo element prior to performing signature calculations. This element uses the general structure for algorithms described in (追記) section 6.1 (追記ここまで) Algorithm Identifiers and Implementation Requirements (削除) (section 6.1). (削除ここまで) . Implementations MUST support the REQUIRED canonicalization algorithms .

Alternatives to the REQUIRED canonicalization algorithms (section 6.5), such as Canonical XML with Comments (section 6.5.1) or a minimal canonicalization (such as CRLF and charset (削除) normalization), (削除ここまで) (追記) normalization) , (追記ここまで) may be explicitly specified but are NOT (削除) REQUIRED. (削除ここまで) (追記) REQUIRED (追記ここまで). Consequently, their use may not interoperate with other applications that do not support the specified algorithm (see XML Canonicalization and Syntax Constraint Considerations , section 7). Security issues may also arise in the treatment of entity processing and comments if non-XML aware canonicalization algorithms are not properly constrained (see section (削除) 8.2: (削除ここまで) (追記) 8.1.2: (追記ここまで) Only What is "Seen" Should be Signed ).

The way in which the SignedInfo element is presented to the canonicalization method is dependent on that method. The following applies to algorithms which process XML as nodes or characters:

  • XML based canonicalization implementations MUST be provided with (削除) a (削除ここまで) (追記) an (追記ここまで) [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ] node-set originally formed from the document containing the SignedInfo and currently indicating the SignedInfo , its descendants, and the attribute and namespace nodes of SignedInfo and its descendant elements.
  • Text based canonicalization algorithms (such as CRLF and charset normalization) should be provided with the UTF-8 octets that represent the well-formed SignedInfo element, from the first character to the last character of the XML representation, inclusive. This includes the entire text of the start and end tags of the SignedInfo element as well as all descendant markup and character data (i.e., the text ) between those tags. Use of text based canonicalization of SignedInfo is NOT (削除) RECOMMENDED. (削除ここまで) (追記) RECOMMENDED (追記ここまで).

We recommend applications that implement a text-based instead of XML-based canonicalization -- such as resource constrained apps -- generate canonicalized XML as their output serialization so as to mitigate interoperability and security concerns. For instance, such an implementation SHOULD (at least) generate standalone XML instances [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ].

(削除) NOTE (削除ここまで) (追記) Note (追記ここまで) : The signature application must exercise great care in accepting and executing an arbitrary CanonicalizationMethod . For example, the canonicalization method could rewrite the URIs of the Reference s being validated. Or, the method could massively transform SignedInfo so that validation would always succeed (i.e., converting it to a trivial signature with a known key over trivial data). Since CanonicalizationMethod is inside SignedInfo , in the resulting canonical form it could erase itself from SignedInfo or modify the SignedInfo element so that it appears that a different canonicalization function was used! Thus a Signature which appears to authenticate the desired data with the desired key, DigestMethod , and SignatureMethod , can be meaningless if a capricious CanonicalizationMethod is used.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="CanonicalizationMethod" type="ds:CanonicalizationMethodType"/> 
 <complexType name="CanonicalizationMethodType" mixed="true">
 <sequence>
 <any namespace="##any" minOccurs="0" maxOccurs="unbounded"/>
 <!-- (0,unbounded) elements from (1,1) namespace -->
 </sequence>
 <attribute name="Algorithm" type="anyURI" use="required"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT CanonicalizationMethod (#PCDATA %Method.ANY;)* > <!ATTLIST CanonicalizationMethod Algorithm CDATA #REQUIRED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"CanonicalizationMethod"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CanonicalizationMethodType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"CanonicalizationMethodType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##any"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
(0,unbounded)
elements
from
(1,1)
namespace
-->
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Algorithm"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.3.2 The (削除ここまで) (追記) 4.4.2 (追記ここまで)(追記) The (追記ここまで) SignatureMethod Element

SignatureMethod is a required element that specifies the algorithm used for signature generation and validation. This algorithm identifies all cryptographic functions involved in the signature operation (e.g. hashing, public key algorithms, MACs, padding, etc.). This element uses the general structure here for algorithms described in section (削除) 6.1: (削除ここまで) (追記) 6.1 (追記ここまで) Algorithm Identifiers and Implementation Requirements . While there is a single identifier, that identifier may specify a format containing multiple distinct signature values.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="SignatureMethod" type="ds:SignatureMethodType"/>
 <complexType name="SignatureMethodType" mixed="true">
 <sequence>
 <element name="HMACOutputLength" minOccurs="0" type="ds:HMACOutputLengthType"/>
 <any namespace="##other" minOccurs="0" maxOccurs="unbounded"/>
 <!-- (0,unbounded) elements from (1,1) external namespace -->
 </sequence>
 <attribute name="Algorithm" type="anyURI" use="required"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT SignatureMethod (#PCDATA|HMACOutputLength %Method.ANY;)* > <!ATTLIST SignatureMethod Algorithm CDATA #REQUIRED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureMethod"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignatureMethodType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureMethodType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"HMACOutputLength"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:HMACOutputLengthType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
(0,unbounded)
elements
from
(1,1)
external
namespace
-->
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Algorithm"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) 4.3.3 The (削除ここまで)

(追記) The (追記ここまで) (削除) Reference (削除ここまで) (追記) ds:HMACOutputLength (追記ここまで) (追記) parameter is used for HMAC [ (追記ここまで)(追記) HMAC (追記ここまで) (追記) ] algorithms. The parameter specifies a truncation length in bits. If this parameter is trusted without further verification, then this can lead to a security bypass [ (追記ここまで) (追記) CVE-2009-0217 (追記ここまで) (追記) ]. Signatures (追記ここまで)(追記) MUST (追記ここまで)(追記) be deemed invalid if the truncation length is below the larger of (a) half the underlying hash algorithm's output length, and (b) 80 bits. Note that some implementations are known to not accept truncation lengths that are lower than the underlying hash algorithm's output length. (追記ここまで)

(追記) 4.4.3 (追記ここまで)(追記) The (追記ここまで)(追記) Reference (追記ここまで) Element

Reference is an element that may occur one or more times. It specifies a digest algorithm and digest value, and optionally an identifier of the object being signed, the type of the object, and/or a list of transforms to be applied prior to digesting. The identification (URI) and transforms describe how the digested content (i.e., the input to the digest method) was created. The Type attribute facilitates the processing of referenced data. For example, while this specification makes no requirements over external data, an application may wish to signal that the referent is a Manifest . An optional ID attribute permits a Reference to be referenced from elsewhere.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="Reference" type="ds:ReferenceType"/>
 <complexType name="ReferenceType">
 <sequence> 
 <element ref="ds:Transforms" minOccurs="0"/> 
 <element ref="ds:DigestMethod"/> 
 <element ref="ds:DigestValue"/> 
 </sequence>
 <attribute name="Id" type="ID" use="optional"/> 
 <attribute name="URI" type="anyURI" use="optional"/> 
 <attribute name="Type" type="anyURI" use="optional"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT Reference (Transforms?, DigestMethod, DigestValue) > <!ATTLIST Reference Id ID #IMPLIED URI CDATA #IMPLIED Type CDATA #IMPLIED> (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Reference"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:ReferenceType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ReferenceType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:Transforms"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:DigestMethod"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:DigestValue"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"URI"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Type"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) 4.3.3.1 The (削除ここまで)
(追記) 4.4.3.1 (追記ここまで)(追記) The (追記ここまで) URI Attribute

The URI attribute identifies a data object using a URI-Reference [ URI ].

The mapping from this attribute's value to a URI reference MUST be performed as specified in section 3.2.17 of [ (削除) XMLSCHEMA Datatypes, 2nd Edition (削除ここまで) (追記) XMLSCHEMA-2 (追記ここまで) ]. Additionally: Some existing implementations are known to verify the value of the URI attribute against the grammar in [ URI ]. It is therefore safest to perform any necessary escaping while generating the URI attribute.

We RECOMMEND XML (削除) signature (削除ここまで) (追記) Signature (追記ここまで) applications be able to dereference URIs in the HTTP scheme. Dereferencing a URI in the HTTP scheme MUST comply with the Status Code Definitions of [ (削除) HTTP (削除ここまで) (追記) HTTP11 (追記ここまで) ] (e.g., 302, 305 and 307 redirects are followed to obtain the entity-body of a 200 status code response). Applications should also be cognizant of the fact that protocol parameter and state information, (such as HTTP cookies, HTML device profiles or content negotiation), may affect the content yielded by dereferencing a URI.

If a resource is identified by more than one URI, the most specific should be used (e.g. http://www.w3.org/2000/06/interop-pressrelease.html.en instead of http://www.w3.org/2000/06/interop-pressrelease). (See (削除) the Reference (削除ここまで) (追記) section 3.2 Core (追記ここまで) Validation (削除) (section 3.2.1) (削除ここまで) for (削除) a (削除ここまで) further information on reference processing.)

If the URI attribute is omitted altogether, the receiving application is expected to know the identity of the object. For example, a lightweight data protocol might omit this attribute given the identity of the object is part of the application context. This attribute may be omitted from at most one Reference in any particular SignedInfo , or Manifest .

The optional Type attribute contains information about the type of object being signed after all ds:Reference transforms have been applied. This is represented as a URI. For example:

Type= "http://www.w3.org/2000/09/xmldsig#Object"
Type= "http://www.w3.org/2000/09/xmldsig#Manifest"

The Type attribute applies to the item being pointed at, not its contents. For example, a reference that results in the digesting of an Object element containing a SignatureProperties element is still of type #Object . The (削除) type (削除ここまで) (追記) Type (追記ここまで) attribute is advisory. No validation of the type information is required by this specification.

(削除) 4.3.3.2 (削除ここまで)
(追記) 4.4.3.2 (追記ここまで) The Reference Processing Model

Note : XPath is (削除) RECOMMENDED. (削除ここまで) (追記) RECOMMENDED (追記ここまで). Signature applications need not conform to [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ] specification in order to conform to this specification. However, the XPath data model, definitions (e.g., node-sets ) and syntax is used within this document in order to describe functionality for those that want to process XML-as-XML (instead of octets) as part of signature generation. For those that want to use these features, a conformant [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ] implementation is one way to implement these features, but it is not required. Such applications could use a sufficiently functional replacement to a node-set and implement only those XPath expression behaviors REQUIRED by this specification. However, for simplicity we generally will use XPath terminology without including this qualification on every point. Requirements over "XPath node-sets" can include a node-set functional equivalent. Requirements over XPath processing can include application behaviors that are equivalent to the corresponding XPath behavior.

The data-type of the result of URI dereferencing or subsequent Transforms is either an octet stream or an XPath node-set.

The Transforms specified in this document are defined with respect to the input they require. The following is the default signature application behavior:

  • If the data object is an octet stream and the next transform requires a node-set, the signature application MUST attempt to parse the octets yielding the required node-set via [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ] well-formed processing.
  • If the data object is a node-set and the next transform requires octets, the signature application MUST attempt to convert the node-set to an octet stream using Canonical XML [ XML-C14N ].

Users may specify alternative transforms that override these defaults in transitions between transforms that expect different inputs. The final octet stream contains the data octets being secured. The digest algorithm specified by DigestMethod is then applied to these data octets, resulting in the DigestValue .

Note: The (追記) section 3.1.1 (追記ここまで) Reference Generation (削除) Model (削除ここまで) (削除) (section 3.1.1) (削除ここまで) includes further restrictions on the reliance upon defined default transformations when applications generate signatures.

In this specification, a 'same-document' reference is defined as a URI-Reference that consists of a hash sign ('#') followed by a fragment or alternatively consists of an empty URI [ URI ].

Unless the URI-Reference is such a 'same-document' reference , the result of dereferencing the URI-Reference MUST be an octet stream. In particular, an XML document identified by URI is not parsed by the signature application unless the URI is a same-document reference or unless a transform that requires XML parsing is applied. (See Transforms (section (削除) 4.3.3.1).) (削除ここまで) (追記) 4.4.3.4).) (追記ここまで)

When a fragment is preceded by an absolute or relative URI in the URI-Reference, the meaning of the fragment is defined by the resource's MIME (削除) type. (削除ここまで) (追記) type [ (追記ここまで)(追記) RFC2045 (追記ここまで) (追記) ]. (追記ここまで) Even for XML documents, URI dereferencing (including the fragment processing) might be done for the signature application by a proxy. Therefore, reference validation might fail if fragment processing is not performed in a standard way (as defined in the following section for same-document references). Consequently, we RECOMMEND in this case that the URI attribute not include fragment identifiers and that such processing be specified as an additional XPath Transform (削除) . (削除ここまで) (追記) or XPath Filter 2 Transform [ (追記ここまで)(追記) XMLDSIG-XPATH-FILTER2 (追記ここまで) (追記) ]. (追記ここまで)

When a fragment is not preceded by a URI in the URI-Reference, XML Signature applications MUST support the null URI and shortname XPointer [ (削除) XPointer-Framework (削除ここまで) (追記) XPTR-FRAMEWORK (追記ここまで) ]. We RECOMMEND support for the same-document XPointers ' #xpointer(/) ' and ' #xpointer(id('ID')) ' if the application also intends to support any canonicalization that preserves comments. (Otherwise URI="#foo" will automatically remove comments before the canonicalization can even be invoked due to the processing defined in Same-Document URI-References (section (削除) 4.3.3.3).) (削除ここまで) (追記) 4.4.3.3).) (追記ここまで) All other support for XPointers is (削除) OPTIONAL, (削除ここまで) (追記) OPTIONAL (追記ここまで), especially all support for shortname and other XPointers in external resources since the application may not have control over how the fragment is generated (leading to interoperability problems and validation failures).

' #xpointer(/) ' MUST be interpreted to identify the root node [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ] of the document that contains the URI attribute.

' #xpointer(id(' ID ')) ' MUST be interpreted to identify the element node identified by ' #element( ID ) ' [ (削除) XPointer-Element (削除ここまで) (追記) XPTR-ELEMENT (追記ここまで) ] when evaluated with respect to the document that contains the URI attribute.

The original edition of this specification [ (削除) XMLDSIG-2002 (削除ここまで) (追記) XMLDSIG-CORE (追記ここまで) ] referenced the XPointer Candidate Recommendation [ (削除) XPTR-2001 (削除ここまで) (追記) XPTR-XPOINTER-CR2001 (追記ここまで) ] and some implementations support it optionally. That Candidate Recommendation has been superseded by the [ (削除) XPointer-Framework (削除ここまで) (追記) XPTR-FRAMEWORK (追記ここまで) ], [ (削除) XPointer-xmlns (削除ここまで) (追記) XPTR-XMLNS (追記ここまで) ] and [ (削除) XPointer-Element (削除ここまで) (追記) XPTR-ELEMENT (追記ここまで) ] Recommendations, and -- at the time of this edition -- the [ (削除) XPointer-xpointer (削除ここまで) (追記) XPTR-XPOINTER (追記ここまで) ] Working Draft. Therefore, the use of the xpointer() scheme [ (削除) XPointer-xpointer (削除ここまで) (追記) XPTR-XPOINTER (追記ここまで) ] beyond the usage discussed in this section is discouraged.

The following examples demonstrate what the URI attribute identifies and how it is dereferenced:

URI="http://example.com/bar.xml"
Identifies the octets that represent the external resource 'http://example.com/bar.xml', that is probably an XML document given its file extension.
URI="http://example.com/bar.xml#chapter1"
Identifies the element with ID attribute value 'chapter1' of the external XML resource 'http://example.com/bar.xml', provided as an octet stream. Again, for the sake of interoperability, the element identified as 'chapter1' should be obtained using an XPath transform rather than a URI fragment (shortname XPointer resolution in external resources is not REQUIRED in this specification).
URI=""
Identifies the node-set (minus any comment nodes) of the XML resource containing the signature
URI="#chapter1"
Identifies a node-set containing the element with ID attribute value 'chapter1' of the XML resource containing the signature. XML Signature (and its applications) modify this node-set to include the element plus all descendants including namespaces and attributes -- but not comments.
(削除) 4.3.3.3 (削除ここまで)
(追記) 4.4.3.3 (追記ここまで) Same-Document URI-References

Dereferencing a same-document reference MUST result in an XPath node-set suitable for use by Canonical XML [ XML-C14N ]. Specifically, dereferencing a null URI ( URI="" ) MUST result in an XPath node-set that includes every non-comment node of the XML document containing the URI attribute. In a fragment URI, the characters after the number sign ('#') character conform to the XPointer syntax [ (削除) XPointer-Framework (削除ここまで) (追記) XPTR-FRAMEWORK (追記ここまで) ]. When processing an XPointer, the application MUST behave as if the XPointer was evaluated with respect to the XML document containing the URI attribute . The application MUST behave as if the result of XPointer processing [ (削除) XPointer-Framework (削除ここまで) (追記) XPTR-FRAMEWORK (追記ここまで) ] were a node-set derived from the resultant subresource as follows:

  1. include XPath nodes having full or partial content within the subresource
  2. replace the root node with its children (if it is in the node-set)
  3. replace any element node E with E plus all descendants of E (text, comment, PI, element) and all namespace and attribute nodes of E and its descendant elements.
  4. if the URI has no fragment identifier or the fragment identifier is a shortname XPointer, then delete all comment nodes

The second to last replacement is necessary because XPointer typically indicates a subtree of an XML document's parse tree using just the element node at the root of the subtree, whereas Canonical XML treats a node-set as a set of nodes in which absence of descendant nodes results in absence of their representative text from the canonical form.

The last step is performed for null URIs and shortname XPointers . It is necessary because when [ XML-C14N ] or [ XML-C14N11 ] is passed a node-set, it processes the node-set as is: with or without comments. Only when it is called with an octet stream does it invoke its own XPath expressions (default or without comments). Therefore to retain the default behavior of stripping comments when passed a node-set, they are removed in the last step if the URI is not a scheme-based XPointer. To retain comments while selecting an element by an identifier ID , use the following scheme-based XPointer: URI='#xpointer(id(' ID '))' . To retain comments while selecting the entire document, use the following scheme-based XPointer: URI='#xpointer(/)' .

The interpretation of these XPointers is defined in The Reference Processing Model (section (削除) 4.3.3.2). (削除ここまで) (追記) 4.4.3.2). (追記ここまで)

(削除) 4.3.3.4 The (削除ここまで)
(追記) 4.4.3.4 (追記ここまで)(追記) The (追記ここまで) Transforms Element

The optional Transforms element contains an ordered list of Transform elements; these describe how the signer obtained the data object that was digested. The output of each Transform serves as input to the next Transform . The input to the first Transform is the result of dereferencing the URI attribute of the Reference element. The output from the last Transform is the input for the DigestMethod algorithm. When transforms are applied the signer is not signing the native (original) document but the resulting (transformed) document. (See Only What is Signed is Secure (section (削除) 8.1).) (削除ここまで) (追記) 8.1.1).) (追記ここまで)

Each Transform consists of an Algorithm attribute and content parameters, if any, appropriate for the given algorithm. The Algorithm attribute value specifies the name of the algorithm to be performed, and the Transform content provides additional data to govern the algorithm's processing of the transform input. (See (追記) section 6.1 (追記ここまで) Algorithm Identifiers and Implementation Requirements (削除) (section 6).) (削除ここまで) (追記) ) (追記ここまで)

As described in The Reference Processing Model (section (削除) 4.3.3.2), (削除ここまで) (追記) 4.4.3.2), (追記ここまで) some transforms take an XPath node-set as input, while others require an octet stream. If the actual input matches the input needs of the transform, then the transform operates on the unaltered input. If the transform input requirement differs from the format of the actual input, then the input must be converted.

Some Transform s may require explicit MIME type, charset (IANA registered "character set"), or other such information concerning the data they are receiving from an earlier Transform or the source data, although no Transform algorithm specified in this document needs such explicit information. Such data characteristics are provided as parameters to the Transform algorithm and should be described in the specification for the algorithm.

Examples of transforms include but are not limited to base64 decoding [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ], canonicalization [ XML-C14N ], XPath filtering [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ], and XSLT [ XSLT ]. The generic definition of the Transform element also allows application-specific transform algorithms. For example, the transform could be a decompression routine given by a Java class appearing as a base64 encoded parameter to a Java Transform algorithm. However, applications should refrain from using application-specific transforms if they wish their signatures to be verifiable outside of their application domain. Transform Algorithms (section 6.6) defines the list of standard transformations.

(削除) Schema Definition: (削除ここまで)
(削除) <element name="Transforms" type="ds:TransformsType"/> <complexType name="TransformsType"> <sequence> <element ref="ds:Transform" maxOccurs="unbounded"/> </sequence> </complexType> (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="Transform" type="ds:TransformType"/>
 <complexType name="TransformType" mixed="true">
 <choice minOccurs="0" maxOccurs="unbounded"> 
 <any namespace="##other" processContents="lax"/>
 <!-- (1,1) elements from (0,unbounded) namespaces -->
 <element name="XPath" type="string"/> 
 </choice>
 <attribute name="Algorithm" type="anyURI" use="required"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT Transforms (Transform+)> (削除ここまで) 
(削除) <!ELEMENT Transform (#PCDATA|XPath %Transform.ANY;)* >
 <!ATTLIST Transform 
 Algorithm CDATA #REQUIRED >
 (削除ここまで)

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Transforms"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:TransformsType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"TransformsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:Transform"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Transform"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:TransformType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"TransformType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
(1,1)
elements
from
(0,unbounded)
namespaces
-->
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"XPath"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"string"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Algorithm"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) <!ELEMENT XPath (#PCDATA) >
 (削除ここまで)
(削除) 4.3.3.5 The (削除ここまで)
(追記) 4.4.3.5 (追記ここまで)(追記) The (追記ここまで) DigestMethod Element

DigestMethod is a required element that identifies the digest algorithm to be applied to the signed object. This element uses the general structure here for algorithms specified in (追記) section 6.1 (追記ここまで) Algorithm Identifiers and Implementation Requirements (削除) (section 6.1). (削除ここまで) .

If the result of the URI dereference and application of Transforms is an XPath node-set (or sufficiently functional replacement implemented by the application) then it must be converted as described in (削除) the (削除ここまで) (追記) section 4.4.3.2 The (追記ここまで) Reference Processing Model (削除) (section 4.3.3.2). (削除ここまで) . If the result of URI dereference and application of transforms is an octet stream, then no conversion occurs (comments might be present if the Canonical XML with Comments was specified in the Transforms). The digest algorithm is applied to the data octets of the resulting octet stream.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="DigestMethod" type="ds:DigestMethodType"/>
 <complexType name="DigestMethodType" mixed="true"> 
 <sequence>
 <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
 </sequence> 
 <attribute name="Algorithm" type="anyURI" use="required"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT DigestMethod (#PCDATA %Method.ANY;)* > <!ATTLIST DigestMethod Algorithm CDATA #REQUIRED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DigestMethod"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:DigestMethodType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DigestMethodType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Algorithm"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) 4.3.3.6 The (削除ここまで)
(追記) 4.4.3.6 (追記ここまで)(追記) The (追記ここまで) DigestValue Element

DigestValue is an element that contains the encoded value of the digest. The digest is always encoded using base64 [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ].

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="DigestValue" type="ds:DigestValueType"/>
 <simpleType name="DigestValueType">
 <restriction base="base64Binary"/>
 </simpleType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT DigestValue (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DigestValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:DigestValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<simpleType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DigestValueType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<restriction
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</simpleType>
 (追記ここまで)

(削除) 4.4 The (削除ここまで) (追記) 4.5 (追記ここまで)(追記) The (追記ここまで) KeyInfo Element

KeyInfo is an optional element that enables the recipient(s) to obtain the key needed to validate the signature. KeyInfo may contain keys, names, certificates and other public key management information, such as in-band key distribution or key agreement data. This specification defines a few simple types but applications may extend those types or all together replace them with their own key identification and exchange semantics using the XML namespace (削除) facility. (削除ここまで) (追記) facility (追記ここまで) [ (削除) XML-ns (削除ここまで) (追記) XML-NAMES (追記ここまで) (削除) ] (削除ここまで) (追記) ]. (追記ここまで) However, questions of trust of such key information (e.g., its authenticity or strength) are out of scope of this specification and left to the application. (追記) Details of the structure and usage of element children of (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) other than simple types described in this specification are out of scope. For example, the definition of PKI certificate contents, certificate ordering, certificate revocation and CRL management are out of scope. (追記ここまで)

If KeyInfo is omitted, the recipient is expected to be able to identify the key based on application context. Multiple declarations within KeyInfo refer to the same key. While applications may define and use any mechanism they choose through inclusion of elements from a different namespace, compliant versions MUST implement KeyValue (追記) ( (追記ここまで)(追記) section 4.5.2 The KeyValue Element (追記ここまで) (削除) (section 4.4.2) (削除ここまで) (追記) ) (追記ここまで) and SHOULD implement (削除) RetrievalMethod (削除ここまで) (追記) KeyInfoReference (追記ここまで)(追記) ( (追記ここまで)(追記) section 4.5.10 The KeyInfoReference Element (追記ここまで) (追記) ). (追記ここまで)(追記) KeyInfoReference (追記ここまで) (削除) (section 4.4.3). (削除ここまで) (追記) is preferred over use of (追記ここまで)(追記) RetrievalMethod (追記ここまで)(追記) as it avoids use of (追記ここまで)(追記) Transform (追記ここまで)(追記) child elements that introduce security risk and implementation challenges. Support for other children of (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) is (追記ここまで)(追記) OPTIONAL (追記ここまで).

The (削除) schema/DTD specifications (削除ここまで) (追記) schema specification (追記ここまで) of many of KeyInfo 's children (e.g., PGPData , SPKIData , X509Data ) permit their content to be extended/complemented with elements from another namespace. This may be done only if it is safe to ignore these extension elements while claiming support for the types defined in this specification. Otherwise, external elements, including alternative structures to those defined by this specification, MUST be a child of KeyInfo . For example, should a complete XML-PGP standard be defined, its root element MUST be a child of KeyInfo . (Of course, new structures from external namespaces can incorporate elements from the (削除) &dsig; (削除ここまで) (追記) dsig: (追記ここまで) namespace via features of the type definition language. For instance, they can create a (削除) DTD that mixes their own and dsig qualified elements, or a (削除ここまで) schema that permits, includes, imports, or derives new types based on (削除) &dsig; (削除ここまで) (追記) dsig: (追記ここまで) elements.)

The following list summarizes the KeyInfo types that are allocated an identifier in the (削除) &dsig; (削除ここまで) (追記) dsig: (追記ここまで) namespace; these can be used within the RetrievalMethod Type attribute to describe a remote KeyInfo structure.

(追記) The following list summarizes the additional (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) types that are allocated an identifier in the (追記ここまで)(追記) dsig11: (追記ここまで)(追記) namespace. (追記ここまで)

In addition to the types above for which we define an XML structure, we specify one additional type to indicate a binary (ASN.1 DER) X.509 Certificate .

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="KeyInfo" type="ds:KeyInfoType"/> 
 <complexType name="KeyInfoType" mixed="true">
 <choice maxOccurs="unbounded"> 
 <element ref="ds:KeyName"/> 
 <element ref="ds:KeyValue"/> 
 <element ref="ds:RetrievalMethod"/> 
 <element ref="ds:X509Data"/> 
 <element ref="ds:PGPData"/> 
 <element ref="ds:SPKIData"/>
 <element ref="ds:MgmtData"/>
 <any processContents="lax" namespace="##other"/>
 <!-- (1,1) elements from (0,unbounded) namespaces -->
 </choice>
 <attribute name="Id" type="ID" use="optional"/>
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT KeyInfo (#PCDATA|KeyName|KeyValue|RetrievalMethod| X509Data|PGPData|SPKIData|MgmtData %KeyInfo.ANY;)* > <!ATTLIST KeyInfo Id ID #IMPLIED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"KeyInfo"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:KeyInfoType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"KeyInfoType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:KeyName"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:KeyValue"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:RetrievalMethod"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:X509Data"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:PGPData"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SPKIData"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:MgmtData"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
<element
ref="dsig11:DEREncodedKeyValue"/>
-->
 (追記ここまで)(追記) 
<!--
DEREncodedKeyValue
(XMLDsig
1.1)
will
use
the
any
element
-->
 (追記ここまで)(追記) 
<!--
<element
ref="dsig11:KeyInfoReference"/>
-->
 (追記ここまで)(追記) 
<!--
KeyInfoReference
(XMLDsig
1.1)
will
use
the
any
element
-->
 (追記ここまで)(追記) 
<!--
<element
ref="xenc:EncryptedKey"/>
-->
 (追記ここまで)(追記) 
<!--
EncryptedKey
(XMLEnc)
will
use
the
any
element
-->
 (追記ここまで)(追記) 
<!--
<element
ref="xenc:Agreement"/>
-->
 (追記ここまで)(追記) 
<!--
Agreement
(XMLEnc)
will
use
the
any
element
-->
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
(1,1)
elements
from
(0,unbounded)
namespaces
-->
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.4.1 The (削除ここまで) (追記) 4.5.1 (追記ここまで)(追記) The (追記ここまで) KeyName Element

The KeyName element contains a string value (in which white space is significant) which may be used by the signer to communicate a key identifier to the recipient. Typically, KeyName contains an identifier related to the key pair used to sign the message, but it may contain other protocol-related information that indirectly identifies a key pair. (Common uses of KeyName include simple string names for keys, a key index, a distinguished name (DN), an email address, etc.)

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="KeyName" type="string"/>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT KeyName (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"KeyName"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"string"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

(削除) 4.4.2 The (削除ここまで) (追記) 4.5.2 (追記ここまで)(追記) The (追記ここまで) KeyValue Element

The KeyValue element contains a single public key that may be useful in validating the signature. Structured formats for defining DSA (削除) (REQUIRED) and (削除ここまで) (追記) ( (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) ), (追記ここまで) RSA (削除) (RECOMMENDED) (削除ここまで) (追記) ( (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) ) and ECDSA ( (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) ) (追記ここまで) public keys are defined in (追記) section 6.4 (追記ここまで) Signature Algorithms (削除) (section 6.4). (削除ここまで) . The KeyValue element may include externally defined public keys values represented as PCDATA or element types from an external namespace.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="KeyValue" type="ds:KeyValueType"/> 
 <complexType name="KeyValueType" mixed="true">
 <choice>
 <element ref="ds:DSAKeyValue"/>
 <element ref="ds:RSAKeyValue"/>
 <any namespace="##other" processContents="lax"/>
 </choice>
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT KeyValue (#PCDATA|DSAKeyValue|RSAKeyValue %KeyValue.ANY;)* > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"KeyValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:KeyValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"KeyValueType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:DSAKeyValue"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:RSAKeyValue"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
<element
ref="dsig11:ECKeyValue"/>
-->
 (追記ここまで)(追記) 
<!--
ECC
keys
(XMLDsig
1.1)
will
use
the
any
element
-->
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) 4.4.2.1 The (削除ここまで)
(追記) 4.5.2.1 (追記ここまで)(追記) The (追記ここまで) DSAKeyValue Element
Identifier
Type=" http://www.w3.org/2000/09/xmldsig#DSAKeyValue "
(this can be used within a RetrievalMethod or Reference element to identify the referent's type)

DSA keys and the DSA signature algorithm are specified in (削除) [DSS]. (削除ここまで) (追記) [ (追記ここまで)(追記) FIPS-186-3 (追記ここまで) (追記) ]. (追記ここまで) DSA public key values can have the following fields:

P
a prime modulus meeting the (削除) [DSS] (削除ここまで) (追記) [ (追記ここまで)(追記) FIPS-186-3 (追記ここまで) (追記) ] (追記ここまで) requirements
Q
an integer in the range 2**159 < Q < 2**160 which is a prime divisor of P-1
G
an integer with certain properties with respect to P and Q
Y
G**X mod P (where X is part of the private key and not made public)
J
(P - 1) / Q
seed
a DSA prime generation seed
pgenCounter
a DSA prime generation counter

Parameter J is available for inclusion solely for efficiency as it is calculatable from P and (削除) Q. (削除ここまで) (追記) Q (追記ここまで). Parameters seed and pgenCounter are used in the DSA prime number generation algorithm specified in (削除) [DSS]. (削除ここまで) (追記) [ (追記ここまで)(追記) FIPS-186-3 (追記ここまで) (追記) ]. (追記ここまで) As such, they are optional but must either both be present or both be absent. This prime generation algorithm is designed to provide assurance that a weak prime is not being used and it yields a P and Q value. Parameters (削除) P, Q, (削除ここまで) (追記) P (追記ここまで),(追記) Q (追記ここまで), and G can be public and common to a group of users. They might be known from application context. As such, they are optional but P and Q must either both appear or both be absent. If all of P , Q , seed , and pgenCounter are present, implementations are not required to check if they are consistent and are free to use either P and Q or seed and pgenCounter . All parameters are encoded as base64 [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ] values.

Arbitrary-length integers (e.g. "bignums" such as RSA moduli) are represented in XML as octet strings as defined by the ds:CryptoBinary type .

(削除) (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="DSAKeyValue" type="ds:DSAKeyValueType"/> 
 <complexType name="DSAKeyValueType"> 
 <sequence>
 <sequence minOccurs="0">
 <element name="P" type="ds:CryptoBinary"/> 
 <element name="Q" type="ds:CryptoBinary"/>
 </sequence>
 <element name="G" type="ds:CryptoBinary" minOccurs="0"/> 
 <element name="Y" type="ds:CryptoBinary"/> 
 <element name="J" type="ds:CryptoBinary" minOccurs="0"/>
 <sequence minOccurs="0">
 <element name="Seed" type="ds:CryptoBinary"/> 
 <element name="PgenCounter" type="ds:CryptoBinary"/> 
 </sequence>
 </sequence>
 </complexType>
 (削除ここまで)
(削除) (削除ここまで) (削除) <!ELEMENT DSAKeyValue ((P, Q)?, G?, Y, J?, (Seed, PgenCounter)?) > <!ELEMENT P (#PCDATA) > <!ELEMENT Q (#PCDATA) > <!ELEMENT G (#PCDATA) > <!ELEMENT Y (#PCDATA) > <!ELEMENT J (#PCDATA) > <!ELEMENT Seed (#PCDATA) > <!ELEMENT PgenCounter (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DSAKeyValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:DSAKeyValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DSAKeyValueType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<sequence
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"P"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Q"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"G"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Y"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"J"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<sequence
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Seed"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PgenCounter"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) 4.4.2.2 The (削除ここまで)
(追記) 4.5.2.2 (追記ここまで)(追記) The (追記ここまで) RSAKeyValue Element
Identifier
Type=" http://www.w3.org/2000/09/xmldsig#RSAKeyValue "
(this can be used within a RetrievalMethod or Reference element to identify the referent's type)

RSA key values have two fields: Modulus and (削除) Exponent. (削除ここまで) (追記) Exponent (追記ここまで).

(削除) <RSAKeyValue> <Modulus>xA7SEU+e0yQH5rm9kbCDN9o3aPIo7HbP7tX6WOocLZAtNfyxSZDU16ksL6W jubafOqNEpcwR3RdFsT7bCqnXPBe5ELh5u4VEy19MzxkXRgrMvavzyBpVRgBUwUlV 5foK5hhmbktQhyNdy/6LpQRhDUDsTvK+g9Ucj47es9AQJ3U= </Modulus> <Exponent>AQAB</Exponent> </RSAKeyValue> (削除ここまで)
Example 6
<RSAKeyValue><Modulus>xA7SEU+e0yQH5rm9kbCDN9o3aPIo7HbP7tX6WOocLZAtNfyxSZDU16ksL6W
(追記) jubafOqNEpcwR3RdFsT7bCqnXPBe5ELh5u4VEy19MzxkXRgrMvavzyBpVRgBUwUlV
 5foK5hhmbktQhyNdy/6LpQRhDUDsTvK+g9Ucj47es9AQJ3U=
 (追記ここまで) </Modulus><Exponent>AQAB</Exponent>(追記) 
</RSAKeyValue>
 (追記ここまで)

Arbitrary-length integers (e.g. "bignums" such as RSA moduli) are represented in XML as octet strings as defined by the ds:CryptoBinary type .

(削除) (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="RSAKeyValue" type="ds:RSAKeyValueType"/>
 <complexType name="RSAKeyValueType">
 <sequence>
 <element name="Modulus" type="ds:CryptoBinary"/> 
 <element name="Exponent" type="ds:CryptoBinary"/>
 </sequence>
 </complexType>
 (削除ここまで)
(削除) (削除ここまで) (削除) <!ELEMENT RSAKeyValue (Modulus, Exponent) > <!ELEMENT Modulus (#PCDATA) > <!ELEMENT Exponent (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"RSAKeyValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:RSAKeyValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"RSAKeyValueType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Modulus"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Exponent"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) 4.4.3 (削除ここまで)
(追記) 4.5.2.3 (追記ここまで) The (追記) ECKeyValue (追記ここまで)(追記) Element (追記ここまで)
(追記) Identifier (追記ここまで)
(追記) Type=" (追記ここまで)(追記) http://www.w3.org/2009/xmldsig11#ECKeyValue (追記ここまで) (追記) " (追記ここまで)
 (追記) (this can be used within a (追記ここまで) RetrievalMethod (追記) or (追記ここまで)(追記) Reference (追記ここまで)(追記) element to identify the referent's type) (追記ここまで)

(追記) The (追記ここまで)(追記) ECKeyValue (追記ここまで)(追記) element is defined in the http://www.w3.org/2009/xmldsig11# namespace. (追記ここまで)

(追記) EC public key values consists of two sub components: Domain parameters and (追記ここまで)(追記) PublicKey (追記ここまで).

Example 7
<ECKeyValuexmlns="http://www.w3.org/2009/xmldsig11#"><NamedCurveURI="urn:oid:1.2.840.10045.3.1.7"/><PublicKey>(追記) 
 vWccUP6Jp3pcaMCGIcAh3YOev4gaa2ukOANC7Ufg
 Cf8KDO7AtTOsGJK7/TA8IC3vZoCy9I5oPjRhyTBulBnj7Y
 (追記ここまで) </PublicKey>(追記) 
</ECKeyValue>
 (追記ここまで)

(追記) Note - A line break has been added to the (追記ここまで)(追記) PublicKey (追記ここまで)(追記) content to preserve printed page width. (追記ここまで)

(追記) Domain parameters can be encoded explicitly using the (追記ここまで)(追記) dsig11:ECParameters (追記ここまで)(追記) element or by reference using the (追記ここまで)(追記) dsig11:NamedCurve (追記ここまで)(追記) element. A named curve is specified through the (追記ここまで)(追記) URI (追記ここまで)(追記) attribute. For named curves that are identified by OIDs, such as those defined in [ (追記ここまで)(追記) RFC3279 (追記ここまで) (追記) ] and [ (追記ここまで)(追記) RFC4055 (追記ここまで) (追記) ], the OID (追記ここまで)(追記) SHOULD (追記ここまで)(追記) be encoded according to [ (追記ここまで)(追記) URN-OID (追記ここまで) (追記) ]. Conformant applications (追記ここまで)(追記) MUST (追記ここまで)(追記) support the (追記ここまで)(追記) dsig11:NamedCurve (追記ここまで)(追記) element and the 256-bit prime field curve as identified by the OID (追記ここまで)(追記) 1.2.840.10045.3.1.7 (追記ここまで).

(追記) The (追記ここまで)(追記) PublicKey (追記ここまで)(追記) element contains a Base64 encoding of a binary representation of the x and y coordinates of the point. Its value is computed as follows: (追記ここまで)

  1. (追記) Convert the elliptic curve point (x,y) to an octet string by first converting the field elements x and y to octet strings as specified in Section 6.2 of [ (追記ここまで)(追記) ECC-ALGS (追記ここまで) (追記) ] ( (追記ここまで)(追記) note (追記ここまで) (追記) ), and then prepend the concatenated result of the conversion with 0x04. Support for Elliptic-Curve-Point-to-Octet-String conversion without point compression is (追記ここまで)(追記) REQUIRED (追記ここまで).
  2. (追記) Base64 encode the octet string resulting from the conversion in Step 1. (追記ここまで)
(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<!--
targetNamespace="http://www.w3.org/2009/xmldsig11#"
-->
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ECKeyValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:ECKeyValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ECKeyValueType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<choice>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ECParameters"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:ECParametersType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"NamedCurve"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:NamedCurveType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PublicKey"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:ECPointType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"NamedCurveType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"URI"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<simpleType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ECPointType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<restriction
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</simpleType>
 (追記ここまで)
(追記) 4.5.2.3.1 (追記ここまで)(追記) Explicit Curve Parameters (追記ここまで)

(追記) The (追記ここまで)(追記) ECParameters (追記ここまで)(追記) element consists of the following subelements. Note these definitions are based on the those described in [ (追記ここまで)(追記) RFC3279 (追記ここまで) (追記) ]. (追記ここまで)

  1. (追記) The (追記ここまで)(追記) FieldID (追記ここまで)(追記) element identifies the finite field over which the elliptic curve is defined. Additional details on the structures for defining prime and characteristic two fields is provided below. (追記ここまで)
  2. (追記) The (追記ここまで)(追記) dsig11:Curve (追記ここまで)(追記) element specifies the coefficients a and b of the elliptic curve E. Each coefficient is first converted from a field element to an octet string as specified in section 6.2 of [ (追記ここまで)(追記) ECC-ALGS (追記ここまで) (追記) ], then the resultant octet string is encoded in base64. (追記ここまで)
  3. (追記) The (追記ここまで)(追記) Base (追記ここまで)(追記) element specifies the base point P on the elliptic curve. The base point is represented as a value of type (追記ここまで)(追記) ECPointType (追記ここまで).
  4. (追記) The (追記ここまで)(追記) Order (追記ここまで)(追記) element specifies the order n of the base point and is encoded as a positiveInteger. (追記ここまで)
  5. (追記) The (追記ここまで)(追記) Cofactor (追記ここまで)(追記) element is an optional element that specifies the integer h = #E(Fq)/n. The cofactor is not required to support ECDSA, except in parameter validation. The cofactor (追記ここまで)(追記) MAY (追記ここまで)(追記) be included to support parameter validation for ECDSA keys. Parameter validation is not required by this specification. The cofactor is required in ECDH public key parameters. (追記ここまで)
  6. (追記) The (追記ここまで)(追記) dsig11:ValidationData (追記ここまで)(追記) element is an optional element that specifies the hash algorithm used to generate the elliptic curve E and the base point G verifiably at random. It also specifies the seed that was used to generate the curve and the base point. (追記ここまで)
(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<!--
targetNamespace="http://www.w3.org/2009/xmldsig11#"
-->
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ECParametersType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"FieldID"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:FieldIDType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Curve"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:CurveType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Base"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:ECPointType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Order"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"CoFactor"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"integer"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ValidationData"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:ECValidationDataType"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"FieldIDType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:Prime"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:TnB"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:PnB"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:GnB"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"CurveType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"A"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"B"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ECValidationDataType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"seed"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"hashAlgorithm"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(追記) Prime fields are described by a single subelement (追記ここまで)(追記) P (追記ここまで),(追記) which represents the field size in bits. It is encoded as a positiveInteger. (追記ここまで)

(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<!--
targetNamespace="http://www.w3.org/2009/xmldsig11#"
-->
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Prime"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:PrimeFieldParamsType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PrimeFieldParamsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"P"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:CryptoBinary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(追記) Structures are defined for three types of characteristic two fields: gaussian normal basis, pentanomial basis and trinomial basis. (追記ここまで)

(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<!--
targetNamespace="http://www.w3.org/2009/xmldsig11#"
-->
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"GnB"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:CharTwoFieldParamsType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"CharTwoFieldParamsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"M"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"positiveInteger"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"TnB"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:TnBFieldParamsType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"TnBFieldParamsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<complexContent>
 (追記ここまで)(追記) 
<extension
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:CharTwoFieldParamsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"K"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"positiveInteger"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</extension>
 (追記ここまで)(追記) 
</complexContent>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PnB"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:PnBFieldParamsType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PnBFieldParamsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<complexContent>
 (追記ここまで)(追記) 
<extension
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:CharTwoFieldParamsType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"K1"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"positiveInteger"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"K2"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"positiveInteger"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"K3"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"positiveInteger"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</extension>
 (追記ここまで)(追記) 
</complexContent>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(追記) 4.5.2.3.2 (追記ここまで)(追記) Compatibility with RFC 4050 (追記ここまで)

(追記) Implementations that need to support the [ (追記ここまで)(追記) RFC4050 (追記ここまで) (追記) ] format for ECDSA keys can avoid known interoperability problems with that specification by adhering to the following profile: (追記ここまで)

  1. (追記) Avoid validating the (追記ここまで)(追記) ECDSAKeyValue (追記ここまで)(追記) element against the [ (追記ここまで) (追記) RFC4050 (追記ここまで) (追記) ] schema. XML schema validators may not support integer types with decimal data exceeding 18 decimal digits. [ (追記ここまで)(追記) XMLSCHEMA-1 (追記ここまで) (追記) ][ (追記ここまで)(追記) XMLSCHEMA-2 (追記ここまで) (追記) ]. (追記ここまで)
  2. (追記) Support only the (追記ここまで)(追記) NamedCurve (追記ここまで)(追記) element. (追記ここまで)
  3. (追記) Support the 256-bit prime field curve, as identified by the URN (追記ここまで)(追記) urn:oid:1.2.840.10045.3.1.7 (追記ここまで).

(追記) The following is an example of a (追記ここまで)(追記) ECDSAKeyValue (追記ここまで)(追記) element that meets the profile described in this section. (追記ここまで)

Example 8
<ECDSAKeyValuexmlns="http://www.w3.org/2001/04/xmldsig-more#"><DomainParameters><NamedCurveURN="urn:oid:1.2.840.10045.3.1.7"/></DomainParameters><PublicKey><XValue="5851106065380174439324917904648283332(追記) 
 0204931884267326155134056258624064349885"/>
 (追記ここまで) <YValue="1024033521368277752409102672177795083(追記) 
 59028642524881540878079119895764161434936"/>
 (追記ここまで) </PublicKey>(追記) 
</ECDSAKeyValue>
 (追記ここまで)

(追記) Note - A line break has been added to the (追記ここまで)(追記) X (追記ここまで)(追記) and (追記ここまで)(追記) Y (追記ここまで)(追記) Value (追記ここまで)(追記) attribute values to preserve printed page width. (追記ここまで)

(追記) 4.5.3 (追記ここまで)(追記) The (追記ここまで)(追記) RetrievalMethod (追記ここまで) Element

A RetrievalMethod element within KeyInfo is used to convey a reference to KeyInfo information that is stored at another location. 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 RetrievalMethod element instead of including the entire chain with a sequence of X509Certificate elements.

RetrievalMethod uses the same syntax and dereferencing behavior as (追記) the (追記ここまで) Reference (削除) 's (削除ここまで) URI (追記) attribute ( (追記ここまで)(追記) section 4.4.3.1 The URI Attribute (追記ここまで) (削除) (section 4.3.3.1) (削除ここまで) (追記) ) (追記ここまで) and (削除) The (削除ここまで) (追記) the (追記ここまで) Reference Processing Model (削除) (section 4.3.3.2) (削除ここまで) except that there (削除) is (削除ここまで) (追記) are (追記ここまで) no DigestMethod or DigestValue child elements and presence of the URI (追記) attribute (追記ここまで) is mandatory.

Type is an optional identifier for the type of data retrieved after all transforms have been applied. The result of dereferencing a RetrievalMethod Reference for all KeyInfo types defined by this specification (削除) (section 4.4) (削除ここまで) (追記) ( (追記ここまで)(追記) section 4.5 The KeyInfo Element (追記ここまで) (追記) ) (追記ここまで) with a corresponding XML structure is an XML element or document with that element as the root. The rawX509Certificate KeyInfo (for which there is no XML structure) returns a binary X509 certificate.

(削除) Schema Definition (削除ここまで)

(追記) Note that when referencing one of the defined (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) types within the same document, or some remote documents, at least one (追記ここまで)(追記) Transform (追記ここまで)(追記) is required to turn an ID-based reference to a (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) element into a child element located inside it. This is due to the lack of an XML ID attribute on the defined (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) types. In such cases, use of (追記ここまで)(追記) KeyInfoReference (追記ここまで)(追記) is encouraged instead, see (追記ここまで)(追記) section 4.5.10 The KeyInfoReference Element (追記ここまで).

(追記) Note: (追記ここまで)(追記) The (追記ここまで)(追記) KeyInfoReference (追記ここまで)(追記) element is preferred over use of (追記ここまで)(追記) RetrievalMethod (追記ここまで)(追記) as it avoids use of (追記ここまで)(追記) Transform (追記ここまで)(追記) child elements that introduce security risk and implementation challenges. (追記ここまで)

(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="RetrievalMethod" type="ds:RetrievalMethodType"/> 
 <complexType name="RetrievalMethodType">
 <sequence>
 <element ref="ds:Transforms" minOccurs="0"/> 
 </sequence> 
 <attribute name="URI" type="anyURI"/>
 <attribute name="Type" type="anyURI" use="optional"/>
 </complexType>
 (削除ここまで)
(削除) DTD (削除ここまで) (削除) <!ELEMENT RetrievalMethod (Transforms?) > <!ATTLIST RetrievalMethod URI CDATA #REQUIRED Type CDATA #IMPLIED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"RetrievalMethod"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:RetrievalMethodType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"RetrievalMethodType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:Transforms"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"URI"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Type"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

Note: The schema for the URI attribute of RetrievalMethod erroneously omitted the attribute: use="required" (削除) The DTD is correct. (削除ここまで) . However, this error only results in a more lax schema which permits all valid RetrievalMethod elements. Because the existing schema is embedded in many applications, which may include the schema in their signatures, the schema has not been corrected to be more restrictive.

(削除) 4.4.4 The (削除ここまで) (追記) 4.5.4 (追記ここまで)(追記) The (追記ここまで) X509Data Element

Identifier
Type=" http://www.w3.org/2000/09/xmldsig#X509Data "
(this can be used within a RetrievalMethod or Reference element to identify the referent's type)

An X509Data element within KeyInfo contains one or more identifiers of keys or X509 certificates (or certificates' identifiers or a revocation list). The content of X509Data (削除) is: At (削除ここまで) (追記) is at (追記ここまで) least one element, from the following set of element types; any of these may appear together or more than once iff (if and only if) each instance describes or is related to the same certificate:

  • The (追記) deprecated (追記ここまで) X509IssuerSerial element, which contains an X.509 issuer distinguished name/serial number pair. The distinguished name SHOULD be represented as a string that complies with section 3 of RFC4514 [ LDAP-DN ], to be generated according to the Distinguished Name Encoding Rules section below,
  • The X509SubjectName element, which contains an X.509 subject distinguished name that SHOULD be represented as a string that complies with section 3 of RFC4514 [ LDAP-DN ], to be generated according to the Distinguished Name Encoding Rules section below,
  • The X509SKI element, which contains the base64 encoded plain (i.e. non-DER-encoded) value of a X509 V.3 SubjectKeyIdentifier (削除) extension. (削除ここまで) (追記) extension, (追記ここまで)
  • The X509Certificate element, which contains a base64-encoded [ (削除) X509v3 (削除ここまで) (追記) X509V3 (追記ここまで) ] certificate, and
  • (削除) Elements from an external namespace which accompanies/complements any of the elements above. (削除ここまで) The X509CRL element, which contains a base64-encoded certificate revocation list (CRL) [ (削除) X509v3 (削除ここまで) (追記) X509V3 (追記ここまで) ].
  • (追記) The (追記ここまで)(追記) dsig11:X509Digest (追記ここまで)(追記) element contains a base64-encoded digest of a certificate. The digest algorithm URI is identified with a required (追記ここまで)(追記) Algorithm (追記ここまで)(追記) attribute. The input to the digest (追記ここまで)(追記) MUST (追記ここまで)(追記) be the raw octets that would be base64-encoded were the same certificate to appear in the X509Certificate element. (追記ここまで)
  • (追記) Elements from an external namespace which accompanies/complements any of the elements above. (追記ここまで)

Any X509IssuerSerial , X509SKI , (削除) and (削除ここまで) X509SubjectName , (追記) and (追記ここまで)(追記) dsig11:X509Digest (追記ここまで) elements that appear MUST refer to the certificate or certificates containing the validation key. All such elements that refer to a particular individual certificate MUST be grouped inside a single X509Data element and if the certificate to which they refer appears, it MUST also be in that X509Data element.

Any X509IssuerSerial , X509SKI , (削除) and (削除ここまで) X509SubjectName , (追記) and (追記ここまで)(追記) dsig11:X509Digest (追記ここまで) elements that relate to the same key but different certificates MUST be grouped within a single KeyInfo but MAY occur in multiple X509Data elements.

(追記) Note that if (追記ここまで)(追記) X509Data (追記ここまで)(追記) child elements are used to identify a trusted certificate (rather than solely as an untrusted hint supplemented by validation by policy), the complete set of such elements that are intended to identify a certificate (追記ここまで)(追記) SHOULD (追記ここまで)(追記) be integrity protected, typically by signing an entire (追記ここまで)(追記) X509Data (追記ここまで)(追記) or (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) element. (追記ここまで)

All certificates appearing in an X509Data element MUST relate to the validation key by either containing it or being part of a certification chain that terminates in a certificate containing the validation key.

No ordering is implied by the above constraints. The comments in the following instance demonstrate these constraints:

(削除) <KeyInfo> <X509Data> <!-- two pointers to certificate-A --> <X509IssuerSerial> <X509IssuerName><span class= "tx">CN=TAMURA Kent, OU=TRL, O=IBM, L=Yamato-shi, ST=Kanagawa, C=JP</X509IssuerName> <X509SerialNumber>12345678</X509SerialNumber> </X509IssuerSerial> <X509SKI>31d97bd7</X509SKI> </X509Data> <X509Data><!-- single pointer to certificate-B --> <X509SubjectName>Subject of Certificate B</X509SubjectName> </X509Data> <X509Data> <!-- certificate chain --> <!--Signer cert, issuer CN=arbolCA,OU=FVT,O=IBM,C=US, serial 4--> <X509Certificate>MIICXTCCA..</X509Certificate> <!-- Intermediate cert subject CN=arbolCA,OU=FVT,O=IBM,C=US issuer CN=tootiseCA,OU=FVT,O=Bridgepoint,C=US --> <X509Certificate>MIICPzCCA...</X509Certificate> <!-- Root cert subject CN=tootiseCA,OU=FVT,O=Bridgepoint,C=US --> <X509Certificate>MIICSTCCA...</X509Certificate> </X509Data> </KeyInfo> (削除ここまで)
Example 9
<KeyInfo><X509Data><!-- two pointers to certificate-A --><X509IssuerSerial><X509IssuerName>
(追記) CN=TAMURA Kent, OU=TRL, O=IBM, L=Yamato-shi, ST=Kanagawa, C=JP
 (追記ここまで) </X509IssuerName><X509SerialNumber>12345678</X509SerialNumber></X509IssuerSerial><X509SKI>31d97bd7</X509SKI></X509Data><X509Data><!-- single pointer to certificate-B --><X509SubjectName>Subject of Certificate B</X509SubjectName></X509Data><X509Data><!-- certificate chain --><!--Signer cert, issuer CN=arbolCA,OU=FVT,O=IBM,C=US, serial 4--><X509Certificate>MIICXTCCA..</X509Certificate><!-- Intermediate cert subject CN=arbolCA,OU=FVT,O=IBM,C=US (追記) 
 issuer CN=tootiseCA,OU=FVT,O=Bridgepoint,C=US -->
 (追記ここまで) <X509Certificate>MIICPzCCA...</X509Certificate><!-- Root cert subject CN=tootiseCA,OU=FVT,O=Bridgepoint,C=US --><X509Certificate>MIICSTCCA...</X509Certificate></X509Data>(追記) 
</KeyInfo>
 (追記ここまで)

Note, there is no direct provision for a PKCS#7 encoded "bag" of certificates or CRLs. However, a set of certificates and CRLs can occur within an X509Data element and multiple X509Data elements can occur in a KeyInfo . Whenever multiple certificates occur in an X509Data element, at least one such certificate must contain the public key which verifies the signature.

(追記) While in principle many certificate encodings are possible, it is (追記ここまで)(追記) RECOMMENDED (追記ここまで)(追記) that certificates appearing in an (追記ここまで)(追記) X509Certificate (追記ここまで)(追記) element be limited to an encoding of BER or its DER subset, allowing that within the certificate other content may be present. The use of other encodings may lead to interoperability issues. In any case, XML Signature implementations (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) alter or re-encode certificates, as doing so could invalidate their signatures. (追記ここまで)

(追記) The (追記ここまで)(追記) X509IssuerSerial (追記ここまで)(追記) element has been deprecated in favor of the newly-introduced (追記ここまで)(追記) dsig11:X509Digest (追記ここまで)(追記) element. The XML Schema type of the serial number was defined to be an integer, and XML Schema validators may not support integer types with decimal data exceeding 18 decimal digits [ (追記ここまで) (削除) 4.4.4.1 (削除ここまで) (追記) XMLSCHEMA-2 (追記ここまで) (追記) ]. This has proven insufficient, because many Certificate Authorities issue certificates with large, random serial numbers that exceed this limit. As a result, deployments that do make use of this element should take care if schema validation is involved. New deployments (追記ここまで)(追記) SHOULD (追記ここまで)(追記) avoid use of the element. (追記ここまで)

(追記) 4.5.4.1 (追記ここまで) Distinguished Name Encoding Rules

To encode a distinguished name ( X509IssuerSerial , X509SubjectName , and KeyName if appropriate), the encoding rules in section 2 of RFC 4514 [ LDAP-DN ] SHOULD be applied, except that the character escaping rules in section 2.4 of RFC 4514 [ LDAP-DN ] MAY be augmented as follows:

  • Escape all occurrences of ASCII control characters (Unicode range \x00 - \x1f) by replacing them with "\" followed by a two digit hex number showing its Unicode number.
  • Escape any trailing space characters (Unicode \x20) by replacing them with "20円", instead of using the escape sequence "\ ".

Since (削除) a (削除ここまで) (追記) an (追記ここまで) XML document logically consists of characters, not octets, the resulting Unicode string is finally encoded according to the character encoding used for producing the physical representation of the XML document.

(削除) Schema Definition (削除ここまで)
(削除) <element name="X509Data" type="ds:X509DataType"/> <complexType name="X509DataType"> <sequence maxOccurs="unbounded"> <choice> <element name="X509IssuerSerial" type="ds:X509IssuerSerialType"/> <element name="X509SKI" type="base64Binary"/> <element name="X509SubjectName" type="string"/> <element name="X509Certificate" type="base64Binary"/> <element name="X509CRL" type="base64Binary"/> <any namespace="##other" processContents="lax"/> </choice> </sequence> </complexType> (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <complexType name="X509IssuerSerialType"> 
 <sequence> 
 <element name="X509IssuerName" type="string"/> 
 <element name="X509SerialNumber" type="integer"/> 
 </sequence>
 </complexType>
 (削除ここまで)
(削除) DTD (削除ここまで) (削除) <!ELEMENT X509Data ((X509IssuerSerial | X509SKI | X509SubjectName | X509Certificate | X509CRL)+ %X509.ANY;)> <!ELEMENT X509IssuerSerial (X509IssuerName, X509SerialNumber) > <!ELEMENT X509IssuerName (#PCDATA) > <!ELEMENT X509SubjectName (#PCDATA) > <!ELEMENT X509SerialNumber (#PCDATA) > <!ELEMENT X509SKI (#PCDATA) > <!ELEMENT X509Certificate (#PCDATA) > <!ELEMENT X509CRL (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509Data"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:X509DataType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509DataType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509IssuerSerial"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:X509IssuerSerialType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509SKI"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509SubjectName"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"string"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509Certificate"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509CRL"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
<element
ref="dsig11:X509Digest"/>
-->
 (追記ここまで)(追記) 
<!--
The
X509Digest
element
(XMLDSig
1.1)
will
use
the
any
element
-->
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509IssuerSerialType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509IssuerName"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"string"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509SerialNumber"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"integer"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<!--
Note,
this
schema
permits
X509Data
to
be
empty;
this
is
precluded
by
the
text
in
<a
href="#sec-KeyInfo"
class="sectionRef"></a>
which
states
that
at
least
one
element
from
the
dsig
namespace
should
be
present
in
the
PGP,
SPKI,
and
X509
structures.
This
is
easily
expressed
for
the
other
key
types,
but
not
for
X509Data
because
of
its
rich
structure.
-->
 (追記ここまで)(追記) 
<!--
targetNameSpace="http://www.w3.org/2009/xmldsig11#"
-->
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509Digest"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:X509DigestType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"X509DigestType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<simpleContent>
 (追記ここまで)(追記) 
<extension
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Algorithm"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</extension>
 (追記ここまで)(追記) 
</simpleContent>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) <!-- Note, this DTD and schema permit to be empty; this is 
 precluded by the text in <a href="#sec-KeyInfo" shape=
"rect"> (section 4.4) which states 
 that at least one element from the dsig namespace should be present 
 in the PGP, SPKI, and X509 structures. This is easily expressed for 
 the other key types, but not for X509Data because of its rich 
 structure. -->
 (削除ここまで)

(削除) 4.4.5 The (削除ここまで) (追記) 4.5.5 (追記ここまで)(追記) The (追記ここまで) PGPData Element

Identifier
Type=" http://www.w3.org/2000/09/xmldsig#PGPData "
(this can be used within a RetrievalMethod or Reference element to identify the referent's type)

The PGPData element within KeyInfo is used to convey information related to PGP public key pairs and signatures on such keys. The PGPKeyID 's value is a base64Binary sequence containing a standard PGP public key identifier as defined in [ PGP (削除) , (削除ここまで) (追記) ] (追記ここまで) section 11.2]. The PGPKeyPacket contains a base64-encoded Key Material Packet as defined in [ PGP (削除) , (削除ここまで) (追記) ] (追記ここまで) section 5.5]. These children element types can be complemented/extended by siblings from an external namespace within PGPData , or PGPData can be replaced all together with an alternative PGP XML structure as a child of KeyInfo . PGPData must contain one PGPKeyID and/or one PGPKeyPacket and 0 or more elements from an external namespace.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="PGPData" type="ds:PGPDataType"/> 
 <complexType name="PGPDataType"> 
 <choice>
 <sequence>
 <element name="PGPKeyID" type="base64Binary"/> 
 <element name="PGPKeyPacket" type="base64Binary" minOccurs="0"/> 
 <any namespace="##other" processContents="lax" minOccurs="0"
 maxOccurs="unbounded"/>
 </sequence>
 <sequence>
 <element name="PGPKeyPacket" type="base64Binary"/> 
 <any namespace="##other" processContents="lax" minOccurs="0"
 maxOccurs="unbounded"/>
 </sequence>
 </choice>
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT PGPData ((PGPKeyID, PGPKeyPacket?) | (PGPKeyPacket) %PGPData.ANY;) > <!ELEMENT PGPKeyPacket (#PCDATA) > <!ELEMENT PGPKeyID (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PGPData"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:PGPDataType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PGPDataType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PGPKeyID"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PGPKeyPacket"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"PGPKeyPacket"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.4.6 The (削除ここまで) (追記) 4.5.6 (追記ここまで)(追記) The (追記ここまで) SPKIData Element

Identifier
Type=" http://www.w3.org/2000/09/xmldsig#SPKIData "
(this can be used within a RetrievalMethod or Reference element to identify the referent's type)

The SPKIData element within KeyInfo is used to convey information related to SPKI public key pairs, certificates and other SPKI data. SPKISexp is the base64 encoding of a SPKI canonical S-expression. SPKIData must have at least one SPKISexp ; SPKISexp can be complemented/extended by siblings from an external namespace within SPKIData , or SPKIData can be entirely replaced with an alternative SPKI XML structure as a child of KeyInfo .

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="SPKIData" type="ds:SPKIDataType"/> 
 <complexType name="SPKIDataType">
 <sequence maxOccurs="unbounded">
 <element name="SPKISexp" type="base64Binary"/>
 <any namespace="##other" processContents="lax" minOccurs="0"/>
 </sequence>
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT SPKIData (SPKISexp %SPKIData.ANY;) > <!ELEMENT SPKISexp (#PCDATA) > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SPKIData"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SPKIDataType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SPKIDataType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SPKISexp"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 4.4.7 The (削除ここまで) (追記) 4.5.7 (追記ここまで)(追記) The (追記ここまで) MgmtData Element

Identifier
Type=" http://www.w3.org/2000/09/xmldsig#MgmtData "
(this can be used within a RetrievalMethod or Reference element to identify the referent's type)
The MgmtData element within KeyInfo is a string value used to convey in-band key distribution or agreement data. (削除) For example, DH key exchange, RSA key encryption, etc. Use (削除ここまで) (追記) However, use (追記ここまで) of this element is NOT (削除) RECOMMENDED. It provides a syntactic hook where in-band (削除ここまで) (追記) RECOMMENDED (追記ここまで)(追記) and (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) be used. The (追記ここまで)(追記) section 4.5.8 XML Encryption EncryptedKey and DerivedKey Elements (追記ここまで) (追記) describes new (追記ここまで)(追記) KeyInfo (追記ここまで)(追記) types for conveying (追記ここまで) key (削除) distribution (削除ここまで) (追記) information. (追記ここまで)
(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"MgmtData"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"string"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

(追記) 4.5.8 (追記ここまで)(追記) XML Encryption (追記ここまで)(追記) EncryptedKey (追記ここまで)(追記) and (追記ここまで)(追記) DerivedKey (追記ここまで)(追記) Elements (追記ここまで)

(追記) The (追記ここまで)(追記) <xenc:EncryptedKey> (追記ここまで)(追記) and (追記ここまで)(追記) <xenc:DerivedKey> (追記ここまで)(追記) elements defined in [ (追記ここまで)(追記) XMLENC-CORE1 (追記ここまで) (追記) ] as children of (追記ここまで)(追記) ds:KeyInfo (追記ここまで)(追記) can be used to convey in-band encrypted (追記ここまで) or (削除) agreement data (削除ここまで) (追記) derived key material. In particular, the (追記ここまで)(追記) xenc:DerivedKey (追記ここまで)(追記) > element may be present when the key used in calculating a Message Authentication Code is derived from a shared secret. (追記ここまで)

(追記) 4.5.9 (追記ここまで)(追記) The (追記ここまで)(追記) DEREncodedKeyValue (追記ここまで)(追記) Element (追記ここまで)

(追記) Identifier (追記ここまで)
(追記) Type=" (追記ここまで)(追記) http://www.w3.org/2009/xmldsig11#DEREncodedKeyValue (追記ここまで) (追記) " (追記ここまで)
(追記) (this (追記ここまで) can be (削除) placed. However, superior interoperable child elements of (削除ここまで) (追記) used within a (追記ここまで) (削除) KeyInfo (削除ここまで) (追記) RetrievalMethod (追記ここまで)(追記) or (追記ここまで)(追記) Reference (追記ここまで) (追記) element to identify the referent's type) (追記ここまで)

(追記) The public key algorithm and value are DER-encoded in accordance with the value that would be used in the Subject Public Key Info field of an X.509 certificate, per section 4.1.2.7 of [ (追記ここまで)(追記) RFC5280 (追記ここまで) (追記) ]. The DER-encoded value is then base64-encoded. (追記ここまで)

(追記) For the key value types supported in this specification, refer to the following (追記ここまで) for (追記) normative references on (追記ここまで) the (削除) transmission (削除ここまで) (追記) format (追記ここまで) of (削除) encrypted keys (削除ここまで) (追記) Subject Public Key Info (追記ここまで) and (追記) the relevant OID values that identify the key/algorithm type: (追記ここまで)

(追記) RSA (追記ここまで)
(追記) See section 2.3.1 of [ (追記ここまで)(追記) RFC3279 (追記ここまで) (追記) ] (追記ここまで)
(追記) DSA (追記ここまで)
(追記) See section 2.3.2 of [ (追記ここまで)(追記) RFC3279 (追記ここまで) (追記) ] (追記ここまで)
(追記) EC (追記ここまで)
(追記) See section 2 of [ (追記ここまで)(追記) RFC5480 (追記ここまで) (追記) ] (追記ここまで)

(追記) Specifications that define additional key types should provide such a normative reference (追記ここまで) for (追記) their own (追記ここまで) key (削除) agreement (削除ここまで) (追記) types where possible. (追記ここまで)

(追記) 
Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(追記) 
<!--
targetNamespace="http://www.w3.org/2009/xmldsig11#"
-->
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DEREncodedKeyValue"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"dsig11:DEREncodedKeyValueType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"DEREncodedKeyValueType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<simpleContent>
 (追記ここまで)(追記) 
<extension
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"base64Binary"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</extension>
 (追記ここまで)(追記) 
</simpleContent>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(追記) Historical note: The (追記ここまで)(追記) DEREncodedKeyValue (追記ここまで)(追記) element was added to XML Signature 1.1 in order to support certain interoperability scenarios where at least one of signer and/or verifier (追記ここまで) are (削除) being specified by (削除ここまで) (追記) not able to serialize keys in (追記ここまで) the (削除) W3C (削除ここまで) XML (削除) Encryption Working Group and they should (削除ここまで) (追記) formats described in (追記ここまで)(追記) section 4.5.2 The KeyValue Element (追記ここまで) (追記) above. The (追記ここまで)(追記) KeyValue (追記ここまで)(追記) element is to (追記ここまで) be used (削除) instead (削除ここまで) (追記) for "bare" XML key representations (not XML wrappings around other binary encodings like ASN.1 DER); for this reason the (追記ここまで)(追記) DEREncodedKeyValue (追記ここまで)(追記) element is not a child (追記ここまで) of (削除) MgmtData (削除ここまで) (追記) KeyValue (追記ここまで) . (追記) The (追記ここまで)(追記) DEREncodedKeyValue (追記ここまで)(追記) element is also not a child of the (追記ここまで)(追記) X509Data (追記ここまで)(追記) element, as the keys represented by (追記ここまで)(追記) DEREncodedKeyValue (追記ここまで)(追記) may not have X.509 certificates associated with them (a requirement for (追記ここまで)(追記) X509Data (追記ここまで)(追記) ). (追記ここまで)

(削除) Schema Definition: (削除ここまで)

(追記) 4.5.10 (追記ここまで)(追記) 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 The URI Attribute (追記ここまで) (追記) ) and the Reference Processing Model ( (追記ここまで)(追記) section 4.4.3.2 The Reference Processing Model (追記ここまで) (追記) ) 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
 (追記ここまで):
(削除) <element name="MgmtData" type="string"/>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT MgmtData (#PCDATA)> (削除ここまで) 

(追記) <!--
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>
 (追記ここまで)

(削除) 4.5 The (削除ここまで) (追記) 4.6 (追記ここまで)(追記) The (追記ここまで) Object Element

Identifier
Type= "http://www.w3.org/2000/09/xmldsig#Object"
(this can be used within a Reference element to identify the referent's type)

Object is an optional element that may occur one or more times. When present, this element may contain any data. The Object element may include optional MIME type, ID, and encoding attributes.

The Object 's Encoding attributed may be used to provide a URI that identifies the method by which the object is encoded (e.g., a binary file).

The MimeType attribute is an optional attribute which describes the data within the Object (independent of its encoding). This is a string with values defined by [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ]. For example, if the Object contains base64 encoded PNG , the Encoding may be specified as 'http://www.w3.org/2000/09/xmldsig#base64' and the MimeType as 'image/png'. This attribute is purely advisory; no validation of the MimeType information is required by this specification. Applications which require normative type and encoding information for signature validation should specify Transforms with well defined resulting types and/or encodings.

The Object 's Id is commonly referenced from a Reference in SignedInfo , or Manifest . This element is typically used for enveloping signatures where the object being signed is to be included in the signature element. The digest is calculated over the entire Object element including start and end tags.

Note, if the application wishes to exclude the <Object> tags from the digest calculation the Reference must identify the actual data object (easy for XML documents) or a transform must be used to remove the Object tags (likely where the data object is non-XML). Exclusion of the object tags may be desired for cases where one wants the signature to remain valid if the data object is moved from inside a signature to outside the signature (or vice versa), or where the content of the Object is an encoding of an original binary document and it is desired to extract and decode so as to sign the original bitwise representation.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="Object" type="ds:ObjectType"/> 
 <complexType name="ObjectType" mixed="true">
 <sequence minOccurs="0" maxOccurs="unbounded">
 <any namespace="##any" processContents="lax"/>
 </sequence>
 <attribute name="Id" type="ID" use="optional"/> 
 <attribute name="MimeType" type="string" use="optional"/>
 <attribute name="Encoding" type="anyURI" use="optional"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT Object (#PCDATA|Signature|SignatureProperties|Manifest %Object.ANY;)* > <!ATTLIST Object Id ID #IMPLIED MimeType CDATA #IMPLIED Encoding CDATA #IMPLIED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Object"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:ObjectType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ObjectType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence
 (追記ここまで)(追記) 
minOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"0"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##any"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"MimeType"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"string"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Encoding"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

(削除) 5.0 (削除ここまで) (追記) 5. (追記ここまで) Additional Signature Syntax

This section describes the optional to implement Manifest and SignatureProperties elements and describes the handling of XML processing instructions and comments. With respect to the elements Manifest and SignatureProperties this section specifies syntax and little behavior -- it is left to the application. These elements can appear anywhere the parent's content model permits; the Signature content model only permits them within Object .

5.1 The Manifest Element

Identifier
Type= "http://www.w3.org/2000/09/xmldsig#Manifest"
(this can be used within a Reference element to identify the referent's type)

The Manifest element provides a list of Reference s. The difference from the list in SignedInfo is that it is application defined which, if any, of the digests are actually checked against the objects referenced and what to do if the object is inaccessible or the digest compare fails. If a Manifest is pointed to from SignedInfo , the digest over the Manifest itself will be checked by the core signature validation behavior. The digests within such a Manifest are checked at the application's discretion. If a Manifest is referenced from another Manifest , even the overall digest of this two level deep Manifest might not be checked.

(削除) Schema Definition: (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="Manifest" type="ds:ManifestType"/> 
 <complexType name="ManifestType">
 <sequence>
 <element ref="ds:Reference" maxOccurs="unbounded"/> 
 </sequence> 
 <attribute name="Id" type="ID" use="optional"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT Manifest (Reference+) > <!ATTLIST Manifest Id ID #IMPLIED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Manifest"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:ManifestType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ManifestType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:Reference"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)

5.2 The SignatureProperties Element

Identifier
Type=" http://www.w3.org/2000/09/xmldsig#SignatureProperties "
(this can be used within a Reference element to identify the referent's type)

Additional information items concerning the generation of the signature(s) can be placed in a SignatureProperty element (i.e., date/time stamp or the serial number of cryptographic hardware used in signature generation).

(削除) Schema Definition: (削除ここまで)
(削除) <element name="SignatureProperties" type="ds:SignaturePropertiesType"/> <complexType name="SignaturePropertiesType"> <sequence> <element ref="ds:SignatureProperty" maxOccurs="unbounded"/> </sequence> <attribute name="Id" type="ID" use="optional"/> </complexType> (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) <element name="SignatureProperty" type="ds:SignaturePropertyType"/> 
 <complexType name="SignaturePropertyType" mixed="true">
 <choice maxOccurs="unbounded">
 <any namespace="##other" processContents="lax"/>
 <!-- (1,1) elements from (1,unbounded) namespaces -->
 </choice>
 <attribute name="Target" type="anyURI" use="required"/> 
 <attribute name="Id" type="ID" use="optional"/> 
 </complexType>
 (削除ここまで)
(削除) DTD: (削除ここまで) (削除) <!ELEMENT SignatureProperties (SignatureProperty+) > <!ATTLIST SignatureProperties Id ID #IMPLIED > (削除ここまで) 

(追記) <element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureProperties"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignaturePropertiesType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignaturePropertiesType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<sequence>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
ref
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignatureProperty"
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</sequence>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)(追記) 
<element
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignatureProperty"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ds:SignaturePropertyType"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<complexType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"SignaturePropertyType"
 (追記ここまで)(追記) 
mixed
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"true"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<choice
 (追記ここまで)(追記) 
maxOccurs
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"unbounded"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<any
 (追記ここまで)(追記) 
namespace
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"##other"
 (追記ここまで)(追記) 
processContents
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"lax"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<!--
(1,1)
elements
from
(1,unbounded)
namespaces
-->
 (追記ここまで)(追記) 
</choice>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Target"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"anyURI"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"required"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
<attribute
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"Id"
 (追記ここまで)(追記) 
type
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"ID"
 (追記ここまで)(追記) 
use
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"optional"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</complexType>
 (追記ここまで)
(削除) <!ELEMENT SignatureProperty (#PCDATA %SignatureProperty.ANY;)* >
 <!ATTLIST SignatureProperty 
 Target CDATA #REQUIRED
 Id ID #IMPLIED >
 (削除ここまで)

5.3 Processing Instructions in Signature Elements

No XML processing instructions (PIs) are used by this specification.

Note that PIs placed inside SignedInfo by an application will be signed unless the CanonicalizationMethod algorithm discards them. (This is true for any signed XML content.) All of the CanonicalizationMethod s identified within this specification retain PIs. When a PI is part of content that is signed (e.g., within SignedInfo or referenced XML documents) any change to the PI will obviously result in a signature failure.

5.4 Comments in Signature Elements

XML comments are not used by this specification.

Note that unless CanonicalizationMethod removes comments within SignedInfo or any other referenced XML (which [ XML-C14N ] does), they will be signed. Consequently, if they are retained, a change to the comment will cause a signature failure. Similarly, the XML signature over any XML data will be sensitive to comment changes unless a comment-ignoring canonicalization/transform method, such as the Canonical XML [ XML-C14N ], is specified.

(削除) 6.0 Algorithms (削除ここまで) (追記) 6. (追記ここまで)(追記) Algorithms (追記ここまで)

This section identifies algorithms used with the XML digital signature specification. Entries contain the identifier to be used in Signature elements, a reference to the formal specification, and definitions, where applicable, for the representation of keys and the results of cryptographic operations.

6.1 Algorithm Identifiers and Implementation Requirements

Algorithms are identified by URIs that appear as an attribute to the element that identifies the algorithms' role ( DigestMethod , Transform , SignatureMethod , or CanonicalizationMethod ). All algorithms used herein take parameters but in many cases the parameters are implicit. For example, a SignatureMethod is implicitly given two parameters: the keying info and the output of CanonicalizationMethod . Explicit additional parameters to an algorithm appear as content elements within the algorithm role element. Such parameter elements have a descriptive element name, which is frequently algorithm specific, and MUST be in the XML Signature namespace or an algorithm specific namespace.

This specification defines a set of algorithms, their URIs, and requirements for implementation. Requirements are specified over implementation, not over requirements for signature use. Furthermore, the mechanism is extensible; alternative algorithms may be used by signature applications.

Digest
(追記) Required (追記ここまで)
  1. (削除) Required (削除ここまで) SHA1 (追記) (Use is DISCOURAGED; see (追記ここまで)(追記) SHA-1 Warning (追記ここまで) (追記) ) (追記ここまで)
    http://www.w3.org/2000/09/xmldsig#sha1
  2. (追記) SHA256 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmlenc#sha256 (追記ここまで)
(追記) Optional (追記ここまで)
  1. (追記) SHA224 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#sha224 (追記ここまで)
  2. (追記) SHA384 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#sha384 (追記ここまで)
  3. (追記) SHA512 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmlenc#sha512 (追記ここまで)
Encoding
(追記) Required (追記ここまで)
  1. (削除) Required (削除ここまで) base64 (追記) ( (追記ここまで)(追記) *note (追記ここまで) (追記) ) (追記ここまで)
    http://www.w3.org/2000/09/xmldsig# base64
MAC
(追記) Required (追記ここまで)
  1. (削除) Required (削除ここまで) HMAC-SHA1 (追記) (Use is DISCOURAGED; see (追記ここまで)(追記) SHA-1 Warning (追記ここまで) (追記) ) (追記ここまで)
    http://www.w3.org/2000/09/xmldsig#hmac-sha1
  2. (追記) HMAC-SHA256 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha256 (追記ここまで)
(追記) Recommended (追記ここまで)
  1. (追記) HMAC-SHA384 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha384 (追記ここまで)
  2. (追記) HMAC-SHA512 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha512 (追記ここまで)
(追記) Optional (追記ここまで)
  1. (追記) HMAC-SHA224 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha224 (追記ここまで)
Signature
Required (削除) DSAwithSHA1 (DSS) (削除ここまで) (削除) http://www.w3.org/2000/09/xmldsig# (削除ここまで)
  1. (追記) RSAwithSHA256 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 (追記ここまで) (削除) dsa-sha1 (削除ここまで) (追記) [ (追記ここまで)(追記) section 6.4.2 RSA (PKCS#1 v1.5) (追記ここまで) (追記) ] (追記ここまで)
  2. (追記) ECDSAwithSHA256 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.3 ECDSA (追記ここまで) (追記) ] (追記ここまで)
  3. (追記) DSAwithSHA1 (追記ここまで)
    (追記) ( (追記ここまで)(追記) signature verification (追記ここまで)(追記) ) (追記ここまで)
    (追記) http://www.w3.org/2000/09/xmldsig#dsa-sha1 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.1 DSA (追記ここまで) (追記) ] (追記ここまで)
Recommended
  1. RSAwithSHA1
    (追記) ( (追記ここまで)(追記) signature verification (追記ここまで)(追記) ; use for signature generation is DISCOURAGED; see (追記ここまで)(追記) SHA-1 Warning (追記ここまで) (追記) ) (追記ここまで)
    http://www.w3.org/2000/09/xmldsig# rsa-sha1
(追記) Optional (追記ここまで)
  1. (追記) RSAwithSHA224 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha224 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.2 RSA (PKCS#1 v1.5) (追記ここまで) (追記) ] (追記ここまで)
  2. (追記) RSAwithSHA384 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha384 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.2 RSA (PKCS#1 v1.5) (追記ここまで) (追記) ] (追記ここまで)
  3. (追記) RSAwithSHA512 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha512 (追記ここまで)
  4. (追記) ECDSAwithSHA1 (Use is DISCOURAGED; see (追記ここまで)(追記) SHA-1 Warning (追記ここまで) (追記) ) (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.3 ECDSA (追記ここまで) (追記) ] (追記ここまで)
  5. (追記) ECDSAwithSHA224 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha224 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.3 ECDSA (追記ここまで) (追記) ] (追記ここまで)
  6. (追記) ECDSAwithSHA384 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha384 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.3 ECDSA (追記ここまで) (追記) ] (追記ここまで)
  7. (追記) ECDSAwithSHA512 (追記ここまで)
    (追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha512 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.3 ECDSA (追記ここまで) (追記) ] (追記ここまで)
  8. (追記) DSAwithSHA1 (追記ここまで)
    (追記) ( (追記ここまで)(追記) signature generation (追記ここまで)(追記) ) (追記ここまで)
    (追記) http://www.w3.org/2000/09/xmldsig#dsa-sha1 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.1 DSA (追記ここまで) (追記) ] (追記ここまで)
  9. (追記) DSAwithSHA256 (追記ここまで)
    (追記) http://www.w3.org/2009/xmldsig11#dsa-sha256 (追記ここまで) (追記) [ (追記ここまで)(追記) section 6.4.1 DSA (追記ここまで) (追記) ] (追記ここまで)
Canonicalization
(追記) Required (追記ここまで)
  1. (削除) Required (削除ここまで) Canonical XML (削除) 1.0(omits (削除ここまで) (追記) 1.0 (omit (追記ここまで) comments)
    http://www.w3.org/TR/2001/REC-xml-c14n-20010315
  2. (削除) Recommended (削除ここまで) Canonical XML (削除) 1.0with Comments http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments (削除ここまで) (追記) 1.1 (omit comments) (追記ここまで)
    (追記) http://www.w3.org/2006/12/xml-c14n11 (追記ここまで)
  3. (削除) Required (削除ここまで) (追記) Exclusive XML Canonicalization 1.0 (omit comments) (追記ここまで)
    (追記) http://www.w3.org/2001/10/xml-exc-c14n# (追記ここまで)
(追記) Recommended (追記ここまで)
  1. Canonical XML (削除) 1.1 (omits (削除ここまで) (追記) 1.0 (with (追記ここまで) comments) (削除) http://www.w3.org/2006/12/xml-c14n11 (削除ここまで)
    (追記) http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments (追記ここまで)
  2. (削除) Recommended (削除ここまで) Canonical XML 1.1 (削除) with Comments (削除ここまで) (追記) (with comments) (追記ここまで)
    http://www.w3.org/2006/12/xml-c14n11#WithComments
  3. (追記) Exclusive XML Canonicalization 1.0 (with comments) (追記ここまで)
    (追記) http://www.w3.org/2001/10/xml-exc-c14n#WithComments (追記ここまで)
Transform
(追記) Required (追記ここまで)
  1. (削除) Optional XSLT http://www.w3.org/TR/1999/REC-xslt-19991116 (削除ここまで) (追記) base64 ( (追記ここまで)(追記) *note (追記ここまで) (追記) ) (追記ここまで)
    (追記) http://www.w3.org/2000/09/xmldsig# (追記ここまで)(追記) base64 (追記ここまで)
  2. (追記) Enveloped Signature ( (追記ここまで)(追記) **note (追記ここまで) (追記) ) (追記ここまで)
    (追記) http://www.w3.org/2000/09/xmldsig#enveloped-signature (追記ここまで)
Recommended
  1. XPath
    http://www.w3.org/TR/1999/REC-xpath-19991116
  2. (削除) Required Enveloped Signature* http://www.w3.org/2000/09/xmldsig#enveloped-signature (削除ここまで) (追記) XPath Filter 2.0 (追記ここまで)
    (追記) http://www.w3.org/2002/06/xmldsig-filter2 (追記ここまで)
(追記) Optional (追記ここまで)
  1. (追記) XSLT (追記ここまで)
    (追記) http://www.w3.org/TR/1999/REC-xslt-19991116 (追記ここまで)

(削除) * (削除ここまで) (追記) *note: Note that the same URI is used to identify base64 both in "encoding" context (e.g. within the (追記ここまで)(追記) Object (追記ここまで)(追記) element) as well as in "transform" context (when identifying a base64 transform). (追記ここまで)

(追記) **note: (追記ここまで) The Enveloped Signature transform removes the Signature element from the calculation of the signature when the signature is within the content that it is being signed. This MAY be implemented via the (削除) RECOMMENDED (削除ここまで) XPath specification specified in 6.6.4: Enveloped Signature Transform ; it MUST have the same effect as that specified by the XPath (削除) Transform . (削除ここまで) (追記) Transform. (追記ここまで)

(追記) When using transforms, we RECOMMEND selecting the least expressive choice that still accomplishes the needs of the use case at hand: Use of XPath filter 2.0 is recommended over use of XPath filter. Use of XPath filter is recommended over use of XSLT. (追記ここまで)

(追記) Note: (追記ここまで)(追記) Implementation requirements for the XPath transform may be downgraded to (追記ここまで)(追記) OPTIONAL (追記ここまで)(追記) in a future version of this specification. (追記ここまで)

6.2 Message Digests

(削除) Only one digest algorithm is defined herein. However, it is expected that one or more additional strong (削除ここまで) (追記) This specification defines several possible (追記ここまで) digest algorithms (削除) will be developed in connection with (削除ここまで) (追記) for (追記ここまで) the (削除) US Advanced Encryption Standard effort. (削除ここまで) (追記) DigestMethod element, including (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) algorithm SHA-256. (追記ここまで) Use of (削除) MD5 [ MD5 ] (削除ここまで) (追記) SHA-256 (追記ここまで) is (削除) NOT RECOMMENDED (削除ここまで) (追記) strongly recommended over SHA-1 (追記ここまで) because recent advances in cryptanalysis (追記) (see e.g. [ (追記ここまで)(追記) SHA-1-Analysis (追記ここまで) (追記) ]) (追記ここまで) have cast doubt on (削除) its strength. (削除ここまで) (追記) the long-term collision resistance of SHA-1. Therefore, SHA-1 support is (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) in this specification only for backwards-compatibility reasons. (追記ここまで)

(追記) Digest algorithms that are known not to be collision resistant (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) be used in DigestMethod elements. For example, the (追記ここまで)(追記) MD5 (追記ここまで) (追記) message digest algorithm (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) be used as specific collisions have been demonstrated for that algorithm. (追記ここまで)

6.2.1 SHA-1

Identifier:
http://www.w3.org/2000/09/xmldsig#sha1

(追記) Note: (追記ここまで)(追記) Use of SHA-256 is strongly recommended over SHA-1 because recent advances in cryptanalysis (see e.g. [ (追記ここまで)(追記) SHA-1-Analysis (追記ここまで) (追記) ], [ (追記ここまで)(追記) SHA-1-Collisions (追記ここまで) (追記) ] ) have cast doubt on the long-term collision resistance of SHA-1. (追記ここまで)

The SHA-1 algorithm [ (削除) SHA-1 (削除ここまで) (追記) FIPS-186-3 (追記ここまで) ] takes no explicit parameters. An example of an SHA-1 DigestAlg element is:

(削除) <span style= "font-weight: normal">http://www.w3.org/2000/09/xmldsig# (削除ここまで)
(追記) Example 10 (追記ここまで)
(追記) 
<DigestMethod
 (追記ここまで)(追記) 
Algorithm
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2000/09/xmldsig#sha1"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

A SHA-1 digest is a 160-bit string. The content of the DigestValue element shall be the base64 encoding of this bit string viewed as a 20-octet octet stream. For example, the DigestValue element for the message digest:

(削除) A9993E36 4706816A BA3E2571 7850C26C 9CD0D89D (削除ここまで)
(追記) Example 11 (追記ここまで)
(追記) 
A9993E36
 (追記ここまで)(追記) 
4706816A
 (追記ここまで)(追記) 
BA3E2571
 (追記ここまで)(追記) 
7850C26C
 (追記ここまで)(追記) 
9CD0D89D
 (追記ここまで)

from Appendix A of the SHA-1 standard would be:

(削除) <DigestValue>qZk+NkcGgWq6PiVxeFDCbJzQ2J0=</DigestValue> (削除ここまで)
(追記) Example 12 (追記ここまで)
(追記) 
<DigestValue>
 (追記ここまで)(追記) 
qZk+NkcGgWq6PiVxeFDCbJzQ2J0=
 (追記ここまで)(追記) 
</DigestValue>
 (追記ここまで)

(追記) 6.2.2 (追記ここまで)(追記) SHA-224 (追記ここまで)

(追記) Identifier: (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#sha224 (追記ここまで)

(追記) The (追記ここまで)(追記) SHA-224 (追記ここまで) (追記) algorithm [ (追記ここまで)(追記) FIPS-180-3 (追記ここまで) (追記) ] takes no explicit parameters. A SHA-224 digest is a 224-bit string. The content of the DigestValue element shall be the base64 encoding of this bit string viewed as a 28-octet octet stream. (追記ここまで)

(追記) 6.2.3 (追記ここまで)(追記) SHA-256 (追記ここまで)

(追記) Identifier: (追記ここまで)
(追記) http://www.w3.org/2001/04/xmlenc#sha256 (追記ここまで)

(追記) The (追記ここまで)(追記) SHA-256 (追記ここまで) (追記) algorithm [ (追記ここまで)(追記) FIPS-180-3 (追記ここまで) (追記) ] takes no explicit parameters. A SHA-256 digest is a 256-bit string. The content of the DigestValue element shall be the base64 encoding of this bit string viewed as a 32-octet octet stream. (追記ここまで)

(追記) 6.2.4 (追記ここまで)(追記) SHA-384 (追記ここまで)

(追記) Identifier: (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#sha384 (追記ここまで)

(追記) The (追記ここまで)(追記) SHA-384 (追記ここまで) (追記) algorithm [ (追記ここまで)(追記) FIPS-180-3 (追記ここまで) (追記) ] takes no explicit parameters. A SHA-384 digest is a 384-bit string. The content of the DigestValue element shall be the base64 encoding of this bit string viewed as a 48-octet octet stream. (追記ここまで)

(追記) 6.2.5 (追記ここまで)(追記) SHA-512 (追記ここまで)

(追記) Identifier: (追記ここまで)
(追記) http://www.w3.org/2001/04/xmlenc#sha512 (追記ここまで)

(追記) The (追記ここまで)(追記) SHA-512 (追記ここまで) (追記) algorithm [ (追記ここまで)(追記) FIPS-180-3 (追記ここまで) (追記) ] takes no explicit parameters. A SHA-512 digest is a 512-bit string. The content of the DigestValue element shall be the base64 encoding of this bit string viewed as a 64-octet octet stream. (追記ここまで)

6.3 Message Authentication Codes

MAC algorithms take two implicit parameters, their keying material determined from KeyInfo and the octet stream output by CanonicalizationMethod . MACs and signature algorithms are syntactically identical but a MAC implies a shared secret key.

6.3.1 HMAC

Identifier:
http://www.w3.org/2000/09/xmldsig#hmac-sha1
(追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha224 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha256 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha384 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#hmac-sha512 (追記ここまで)

The HMAC algorithm (RFC2104 [ HMAC ]) takes the (削除) truncation (削除ここまで) (追記) output (truncation) (追記ここまで) length in bits as a parameter; (削除) if (削除ここまで) (追記) this specification REQUIRES that the truncation length be a multiple of 8 (i.e. fall on a byte boundary) because Base64 encoding operates on full bytes. If (追記ここまで) the (追記) truncation (追記ここまで) parameter is not specified then all the bits of the hash are output. (追記) Any signature with a truncation length that is less than half the output length of the underlying hash algorithm (追記ここまで)(追記) MUST (追記ここまで)(追記) be deemed invalid. (追記ここまで) An example of an HMAC SignatureMethod element:

(削除) <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"> <HMACOutputLength>128</HMACOutputLength> </SignatureMethod> (削除ここまで)
Example 13
<SignatureMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#hmac-sha1"><HMACOutputLength>128</HMACOutputLength>

(追記) </SignatureMethod>
 (追記ここまで)

The output of the HMAC algorithm is ultimately the output (possibly truncated) of the chosen digest algorithm. This value shall be base64 encoded in the same straightforward fashion as the output of the digest algorithms. Example: the SignatureValue element for the HMAC-SHA1 digest

(削除) 9294727A 3638BB1C 13F48EF8 158BFC9D (削除ここまで)
(追記) Example 14 (追記ここまで)
(追記) 
9294727A
 (追記ここまで)(追記) 
3638BB1C
 (追記ここまで)(追記) 
13F48EF8
 (追記ここまで)(追記) 
158BFC9D
 (追記ここまで)

from the test vectors in [ HMAC ] would be

(削除) <SignatureValue>kpRyejY4uxwT9I74FYv8nQ==</SignatureValue> (削除ここまで)
(追記) Example 15 (追記ここまで)
(追記) 
<SignatureValue>
 (追記ここまで)(追記) 
kpRyejY4uxwT9I74FYv8nQ==
 (追記ここまで)(追記) 
</SignatureValue>
 (追記ここまで)
(削除) Schema Definition: (削除ここまで) (削除) <simpleType name="HMACOutputLengthType"> <restriction base="integer"/> </simpleType> (削除ここまで) 

(追記) Schema
 (追記ここまで)(追記) 
Definition
 (追記ここまで):
(削除) DTD: (削除ここまで) (削除) <!ELEMENT HMACOutputLength (#PCDATA)> (削除ここまで) 

(追記) <simpleType
 (追記ここまで)(追記) 
name
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"HMACOutputLengthType"
 (追記ここまで)(追記) 
>
 (追記ここまで)(追記) 
<restriction
 (追記ここまで)(追記) 
base
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"integer"
 (追記ここまで)(追記) 
/>
 (追記ここまで)(追記) 
</simpleType>
 (追記ここまで)

6.4 Signature Algorithms

Signature algorithms take two implicit parameters, their keying material determined from KeyInfo and the octet stream output by CanonicalizationMethod . Signature and MAC algorithms are syntactically identical but a signature implies public key cryptography.

6.4.1 DSA

Identifier:
http://www.w3.org/2000/09/xmldsig#dsa-sha1
(追記) http://www.w3.org/2009/xmldsig11#dsa-sha256 (追記ここまで)

The DSA (削除) algorithm (削除ここまで) (追記) family of algorithms is defined in FIPS 186-3 (追記ここまで) [ (削除) DSS (削除ここまで) (追記) FIPS-186-3 (追記ここまで) (削除) ] (削除ここまで) (追記) ]. FIPS 186-3 defines DSA in terms of two security parameters L and N where L = |p|, N = |q|, p is the prime modulus, q is a prime divisor of (p-1). FIPS 186-3 defines four valid pairs of (L, N); they are: (1024, 160), (2048, 224), (2048, 256) and (3072, 256). The pair (1024, 160) corresponds to the algorithm DSAwithSHA1, which is identified in this specification by the URI (追記ここまで)(追記) http://www.w3.org/2000/09/xmldsig#dsa-sha1 (追記ここまで). (追記) The pairs (2048, 256) and (3072, 256) correspond to the algorithm DSAwithSHA256, which is identified in this specification by the URI (追記ここまで)(追記) http://www.w3.org/2009/xmldsig11#dsa-sha256 (追記ここまで). (追記) This specification does not use the (2048, 224) instance of DSA (which corresponds to DSAwithSHA224). (追記ここまで)

(追記) DSA (追記ここまで) takes no explicit (削除) parameters. An (削除ここまで) (追記) parameters; an (追記ここまで) example of a DSA SignatureMethod element is:

(削除) (削除ここまで)
(追記) Example 16 (追記ここまで)
(追記) 
<SignatureMethod
 (追記ここまで)(追記) 
Algorithm
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2009/xmldsig11#dsa-sha256"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

The output of the DSA algorithm consists of a pair of integers usually referred by the pair (r, s). The signature value consists of the base64 encoding of the concatenation of two octet-streams that respectively result from the octet-encoding of the values r and s in that order. Integer to octet-stream conversion must be done according to the I2OSP operation defined in the RFC (削除) 2437 (削除ここまで) (追記) 3447 (追記ここまで) [ PKCS1 ] specification with a l parameter equal to 20. For example, the SignatureValue element for a DSA signature ( r , s ) with values specified in hexadecimal:

(削除) (削除ここまで)
Example 17
r =8BAC1AB66410435C B7181F95 B16AB97C 92B341C0


(追記) s
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
41E2345F
 (追記ここまで)(追記) 
1F56DF24
 (追記ここまで)(追記) 
58F426D1
 (追記ここまで)(追記) 
55B4BA2D
 (追記ここまで)(追記) 
B6DCD8C8
 (追記ここまで)

from the example in Appendix 5 of the DSS standard would be

(削除) (削除ここまで)
Example 18
<SignatureValue>


(追記) i6watmQQQ1y3GB+VsWq5fJKzQcBB4jRfH1bfJFj0JtFVtLotttzYyA==
 (追記ここまで)(追記) 
</SignatureValue>
 (追記ここまで)

(追記) Security considerations regarding DSA key sizes (追記ここまで)

(追記) Per FIPS 186-3 [ (追記ここまで)(追記) FIPS-186-3 (追記ここまで) (追記) ], the DSA security parameter L is defined to be 1024, 2048 or 3072 bits and the corresponding DSA q value is defined to be 160, 224/256 and 256 bits respectively. (追記ここまで)

(追記) NIST provides guidance on the use of keys of various strength for various time frames in special Publication SP 800-57 Part 1 [ (追記ここまで)(追記) SP800-57 (追記ここまで) (追記) ]. Implementers should consult this publication for guidance on acceptable key lengths for applications, however 2048-bit public keys are the minimum recommended key length and 3072-bit keys are recommended for securing information beyond 2030. SP800-57 Part 1 states that DSA 1024-bit key sizes should not be used except to verify and honor signatures created using older legacy systems. (追記ここまで)

(追記) Since XML Signature 1.0 requires implementations to support DSA-based digital signatures, this XML Signature 1.1 revision allows verifiers to verify DSA signatures for DSA keys of 1024 bits in order to validate existing signatures. XML Signature 1.1 implementations (追記ここまで)(追記) MAY (追記ここまで)(追記) but are (追記ここまで)(追記) NOT REQUIRED (追記ここまで)(追記) to support DSA-based signature generation. Given the short key size and SP800-57 guidelines, DSA with 1024-bit prime moduli (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) be used to create signatures. DSA with 1024-bit prime moduli (追記ここまで)(追記) MAY (追記ここまで)(追記) be used to verify older legacy signatures, with an understanding of the associated risks. Important older signatures (追記ここまで)(追記) SHOULD (追記ここまで)(追記) be re-signed with stronger signatures. (追記ここまで)

6.4.2 (削除) PKCS1 (RSA-SHA1) (削除ここまで) (追記) RSA (PKCS#1 v1.5) (追記ここまで)

Identifier:
http://www.w3.org/2000/09/xmldsig#rsa-sha1
(追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha224 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha384 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#rsa-sha512 (追記ここまで)

The expression "RSA algorithm" as used in this specification refers to the RSASSA-PKCS1-v1_5 algorithm described in RFC (削除) 2437 (削除ここまで) (追記) 3447 (追記ここまで) [ PKCS1 ]. The RSA algorithm takes no explicit parameters. An example of an RSA SignatureMethod element is:

(削除) (削除ここまで)
(追記) Example 19 (追記ここまで)
(追記) 
<SignatureMethod
 (追記ここまで)(追記) 
Algorithm
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2000/09/xmldsig#rsa-sha1"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

The SignatureValue content for an RSA signature is the base64 [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ] encoding of the octet string computed as per RFC (削除) 2437 (削除ここまで) (追記) 3447 (追記ここまで) [ PKCS1 (削除) , (削除ここまで) (追記) ], (追記ここまで) section (削除) 8.1.1: (削除ここまで) (追記) 8.2.1: (追記ここまで) Signature generation for the RSASSA-PKCS1-v1_5 signature scheme]. (削除) As specified in the EMSA-PKCS1-V1_5-ENCODE function RFC 2437 [ PKCS1 , section 9.2.1], the value input to (削除ここまで) (追記) Computation of (追記ここまで) the signature (削除) function MUST contain a pre-pended algorithm object identifier for (削除ここまで) (追記) will require concatenation of (追記ここまで) the hash (削除) function, but the availability (削除ここまで) (追記) value and a constant string determined by RFC 3447. Signature computation and verification does not require implementation (追記ここまで) of an ASN.1 (削除) parser and recognition of OIDs (削除ここまで) (追記) parser. (追記ここまで)

(追記) The resulting base64 [ (追記ここまで)(追記) RFC2045 (追記ここまで) (追記) ] string (追記ここまで) is (削除) not required (削除ここまで) (追記) the value (追記ここまで) of (削除) a signature verifier. The PKCS#1 v1.5 representation appears as: (削除ここまで) (追記) the child text node of the SignatureValue element, e.g. (追記ここまで)

(削除) CRYPT (PAD (ASN.1 (OID, DIGEST (data)))) (削除ここまで)
Example 20
<SignatureValue>
(追記) IWijxQjUrcXBYoCei4QxjWo9Kg8D3p9tlWoT4t0/gyTE96639In0FZFY2/rvP+/bMJ01EArmKZs
R5VW3rwoPxw=
 (追記ここまで)(追記) 
</SignatureValue>
 (追記ここまで)

Note (削除) that (削除ここまで) (追記) - A line break has been added to preserve printed page width. (追記ここまで)

(追記) Security considerations regarding RSA key sizes (追記ここまで)

(追記) NIST provides guidance on (追記ここまで) the (削除) padded ASN.1 (削除ここまで) (追記) use of keys of various strength for various time frames in special Publication SP 800-57 Part 1 [ (追記ここまで)(追記) SP800-57 (追記ここまで) (追記) ]. Implementers should consult this publication for guidance on acceptable key lengths for applications, however 2048-bit public keys are the minimum recommended key length and 3072-bit keys are recommended for securing information beyond 2030. (追記ここまで)

(追記) All conforming implementations of XML Signature 1.1 (追記ここまで)(追記) MUST (追記ここまで)(追記) support RSA signature generation and verification with public keys at least 2048 bits in length. RSA public keys of 1024 bits or less (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) be used to create new signatures but (追記ここまで)(追記) MAY (追記ここまで)(追記) be used to verify signatures created by older legacy systems. XML Signature 1.1 implementations (追記ここまで)(追記) MUST (追記ここまで)(追記) use at least 2048-bit keys for creating signatures, and (追記ここまで)(追記) SHOULD (追記ここまで)(追記) use at least 3072-bit keys for signatures that (追記ここまで) will be (追記) verified beyond 2030. (追記ここまで)

(追記) 6.4.3 (追記ここまで)(追記) ECDSA (追記ここまで)

(追記) Identifiers: (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha1 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha224 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha384 (追記ここまで)
(追記) http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha512 (追記ここまで)

(追記) The ECDSA algorithm [ (追記ここまで)(追記) FIPS-186-3 (追記ここまで) (追記) ] takes no explicit parameters. An example (追記ここまで) of (削除) the following form: (削除ここまで) (追記) a ECDSA (追記ここまで)(追記) SignatureMethod (追記ここまで)(追記) element is: (追記ここまで)

(削除) 01 | FF* | 00 | prefix | hash (削除ここまで)
(追記) Example 21 (追記ここまで)
(追記) 
<SignatureMethod
 (追記ここまで)(追記) 
Algorithm
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"http://www.w3.org/2001/04/xmldsig-more#ecdsa-sha256"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

(削除) where "|" is concatenation, "01", "FF", and "00" are fixed octets (削除ここまで) (追記) The output (追記ここまで) of the (削除) corresponding hexadecimal value, "hash" is (削除ここまで) (追記) ECDSA algorithm consists of a pair of integers usually referred by (追記ここまで) the (削除) SHA1 digest (削除ここまで) (追記) pair (r, s). The signature value consists (追記ここまで) of the (削除) data, and "prefix" is (削除ここまで) (追記) base64 encoding of (追記ここまで) the (削除) ASN.1 BER SHA1 algorithm designator prefix required (削除ここまで) (追記) concatenation of two octet-streams that respectively result from the octet-encoding of the values r and s (追記ここまで) in (削除) PKCS1 [RFC 2437], (削除ここまで) that (削除) is, hex 30 21 30 09 06 05 2B 0E 03 02 1A 05 00 04 14 This prefix is included to make it easier (削除ここまで) (追記) order. Integer (追記ここまで) to (削除) use standard cryptographic libraries. The FF octet MUST (削除ここまで) (追記) octet-stream conversion must (追記ここまで) be (削除) repeated (削除ここまで) (追記) done according to (追記ここまで) the (削除) maximum number (削除ここまで) (追記) I2OSP operation defined in the (追記ここまで)(追記) RFC 3447 (追記ここまで) (追記) [ (追記ここまで)(追記) PKCS1 (追記ここまで) (追記) ] specification with the (追記ここまで)(追記) l (追記ここまで)(追記) parameter equal to the size (追記ここまで) of (削除) times such that (削除ここまで) the (削除) value (削除ここまで) (追記) base point order (追記ここまで) of the (削除) quantity being CRYPTed is one octet shorter than (削除ここまで) (追記) curve in bytes (e.g. 32 for (追記ここまで) the (削除) RSA modulus. (削除ここまで) (追記) P-256 curve and 66 for the P-521 curve). (追記ここまで)

(削除) The resulting base64 (削除ここまで) (追記) This specification REQUIRES implementations to implement an algorithm that leads to the same results as ECDSA over the P-256 prime curve specified in Section D.2.3 of FIPS 186-3 (追記ここまで) [ (削除) MIME (削除ここまで) (追記) FIPS-186-3 (追記ここまで) ] (削除) string (削除ここまで) (追記) (and using the SHA-256 hash algorithm), referred to as the ECDSAwithSHA256 signature algorithm [ (追記ここまで)(追記) ECC-ALGS (追記ここまで) (追記) ]. It (追記ここまで) is (追記) further (追記ここまで)(追記) RECOMMENDED (追記ここまで)(追記) that implementations also implement algorithms that lead to (追記ここまで) the (削除) value of (削除ここまで) (追記) same results as ECDSA over (追記ここまで) the (削除) child text node (削除ここまで) (追記) P-384 and P-521 prime curves; these curves are defined in Sections D.2.4 and D.2.5 (追記ここまで) of (追記) FIPS 186-3, respectively [ (追記ここまで)(追記) ECC-ALGS (追記ここまで) (追記) ]. (追記ここまで)

(追記) Note: (追記ここまで)(追記) As described in IETF RFC 6090, (追記ここまで) the (削除) SignatureValue element, e.g. (削除ここまで) (追記) Elliptic Curve DSA (ECDSA) and KT-I signature methods are mathematically and functionally equivalent for fields of characteristic greater than three. See IETF RFC 6090 Section 7.2 [ (追記ここまで)(追記) ECC-ALGS (追記ここまで) (追記) ]. (追記ここまで)

(削除) <SignatureValue> IWijxQjUrcXBYoCei4QxjWo9Kg8D3p9tlWoT4t0/gyTE96639In0FZFY2/rvP+/bMJ01EArmKZsR5VW3rwoPxw= </SignatureValue> (削除ここまで)

6.5 Canonicalization Algorithms

If canonicalization is performed over octets, the canonicalization algorithms take two implicit parameters: the content and its charset. The charset is derived according to the rules of the transport protocols and media types (e.g, (削除) RFC2376 (削除ここまで) [ (削除) XML-MT (削除ここまで) (追記) XML-MEDIA-TYPES (追記ここまで) ] defines the media types for XML). This information is necessary to correctly sign and verify documents and often requires careful server side configuration.

Various canonicalization algorithms require conversion to [ UTF-8 (削除) ].The (削除ここまで) (追記) ]. The (追記ここまで) algorithms below understand at least [ UTF-8 ] and [ UTF-16 ] as input encodings. We RECOMMEND that externally specified algorithms do the same. Knowledge of other encodings is (削除) OPTIONAL. (削除ここまで) (追記) OPTIONAL (追記ここまで).

Various canonicalization algorithms transcode from a non-Unicode encoding to Unicode. The output of these algorithms will be in NFC [ NFC (削除) , NFC-Corrigendum (削除ここまで) ]. This is because the XML processor used to prepare the XPath data model input is required (by the Data Model) to use Normalization Form C when converting an XML document to the UCS character domain from any encoding that is not UCS-based.

We RECOMMEND that externally specified canonicalization algorithms do the same. (Note, there can be ambiguities in converting existing charsets to Unicode, for an example see the XML Japanese Profile (追記) Note (追記ここまで) [ XML-Japanese (削除) ] Note.) (削除ここまで) (追記) ].) (追記ここまで)

This specification REQUIRES implementation of (削除) both (削除ここまで) Canonical XML 1.0 [ XML-C14N (削除) ] and (削除ここまで) (追記) ], (追記ここまで) Canonical XML 1.1 [ XML-C14N11 (追記) ]] and Exclusive XML Canonicalization [ (追記ここまで)(追記) XML-EXC-C14N (追記ここまで) ]. We RECOMMEND that applications that generate signatures choose Canonical XML 1.1 [ XML-C14N11 ] when inclusive canonicalization is desired.

Note : Canonical XML 1.0 [ XML-C14N ] and Canonical XML 1.1 [ XML-C14N11 ] specify a standard serialization of XML that, when applied to a subdocument, includes the subdocument's ancestor context including all of the namespace declarations and some attributes in the 'xml:' namespace. However, some applications require a method which, to the extent practical, excludes unused ancestor context from a canonicalized subdocument. The Exclusive XML Canonicalization Recommendation [ (削除) XML-exc-C14N (削除ここまで) (追記) XML-EXC-C14N (追記ここまで) ] may be used to address requirements resulting from scenarios where a subdocument is moved between contexts.

6.5.1 Canonical XML 1.0

Identifier for REQUIRED Canonical XML 1.0 (omits comments):
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
Identifier for Canonical XML 1.0 with Comments:
http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments
(追記) Input: (追記ここまで)
(追記) octet-stream, node-set (追記ここまで)
(追記) Output: (追記ここまで)
(追記) octet-stream (追記ここまで)

An example of an XML canonicalization element is:

(削除) (削除ここまで)
(追記) Example 22 (追記ここまで)
(追記) 
<CanonicalizationMethod
 (追記ここまで)(追記) 
Algorithm
 (追記ここまで)(追記) 
=
 (追記ここまで)(追記) 
"
 (追記ここまで)(追記) 
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
 (追記ここまで)(追記) 
"
 (追記ここまで)(追記) 
/>
 (追記ここまで)

The normative specification of Canonical XML1.0 is [ XML-C14N ]. The algorithm is capable of taking as input either an octet stream or an XPath node-set (or sufficiently functional alternative). The algorithm produces an octet stream as output. Canonical XML is easily parameterized (via an additional URI) to omit or retain comments.

6.5.2 Canonical XML 1.1

Identifier for REQUIRED Canonical XML 1.1 (omits comments):
http://www.w3.org/2006/12/xml-c14n11
Identifier for Canonical XML 1.1 with Comments:
http://www.w3.org/2006/12/xml-c14n11#WithComments
(追記) Input: (追記ここまで)
(追記) octet-stream, node-set (追記ここまで)
(追記) Output: (追記ここまで)
(追記) octet-stream (追記ここまで)

The normative specification of Canonical XML 1.1 is [ XML-C14N11 ]. The algorithm is capable of taking as input either an octet stream or an XPath node-set (or sufficiently functional alternative). The algorithm produces an octet stream as output. Canonical XML 1.1 is easily parameterized (via an additional URI) to omit or retain comments.

(追記) 6.5.3 (追記ここまで)(追記) Exclusive XML Canonicalization 1.0 (追記ここまで)

(追記) Identifier for (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) Exclusive XML Canonicalization 1.0 (omits comments): (追記ここまで)
(追記) http://www.w3.org/2001/10/xml-exc-c14n# (追記ここまで)
(追記) Identifier for Exclusive XML Canonicalization 1.0 with Comments: (追記ここまで)
(追記) http://www.w3.org/2001/10/xml-exc-c14n#WithComments (追記ここまで)
(追記) Input: (追記ここまで)
(追記) octet-stream, node-set (追記ここまで)
(追記) Output: (追記ここまで)
(追記) octet-stream (追記ここまで)

(追記) The normative specification of Exclusive XML Canonicalization 1.0 is [XML-EXC-C14N]]. (追記ここまで)

6.6 Transform Algorithms

A Transform algorithm has a single implicit parameter: an octet stream from the Reference or the output of an earlier Transform .

(追記) For implementation requirements, please see (追記ここまで)(追記) Algorithm Identifiers and Implementation Requirements (追記ここまで). Application developers are strongly encouraged to support all transforms (追記) that are (追記ここまで) listed (削除) in this section (削除ここまで) as RECOMMENDED unless the application environment has resource constraints that would make such support impractical. Compliance with this recommendation will maximize application interoperability and libraries should be available to enable support of these transforms in applications without extensive development.

6.6.1 Canonicalization

Any canonicalization algorithm that can be used for CanonicalizationMethod (such as those in Canonicalization Algorithms (section 6.5)) can be used as a Transform .

6.6.2 Base64

Identifiers:
http://www.w3.org/2000/09/xmldsig#base64
(追記) Input: (追記ここまで)
(追記) octet-stream, node-set (追記ここまで)
(追記) Output: (追記ここまで)
(追記) octet-stream (追記ここまで)

The normative specification for base64 decoding transforms is [ (削除) MIME (削除ここまで) (追記) RFC2045 (追記ここまで) ]. The base64 Transform element has no content. The input is decoded by the algorithms. This transform is useful if an application needs to sign the raw data associated with the encoded content of an element.

This transform (削除) requires (削除ここまで) (追記) accepts either (追記ここまで) an (削除) octet stream for (削除ここまで) (追記) octet-stream or a node-set as (追記ここまで) input. If an (追記) octet-string is given as input, then this octet-stream is processed directly. If an (追記ここまで) XPath node-set (or sufficiently functional alternative) is given as input, then it is converted to an octet stream by performing operations logically equivalent to 1) applying an XPath transform with expression self::text() , then 2) (削除) taking (削除ここまで) (追記) sorting the nodeset by document order, then concatenating (追記ここまで) the string-value of (追記) each of (追記ここまで) the (削除) node-set. (削除ここまで) (追記) nodes into one long string. (追記ここまで) Thus, if an XML element is identified by a shortname XPointer in the Reference URI, and its content consists solely of base64 encoded character data, then this transform automatically strips away the start and end tags of the identified element and any of its descendant elements as well as any descendant comments and processing instructions. The output of this transform is an octet stream.

6.6.3 XPath Filtering

Identifier:
http://www.w3.org/TR/1999/REC-xpath-19991116
(追記) Input: (追記ここまで)
(追記) octet-stream, node-set (追記ここまで)
(追記) Output: (追記ここまで)
(追記) node-set (追記ここまで)

The normative specification for XPath expression evaluation is [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ]. The XPath expression to be evaluated appears as the character content of a transform parameter child element named XPath .

The input required by this transform is an XPath (削除) node-set. (削除ここまで) (追記) node-set or an octet-stream. (追記ここまで) Note that if the actual input is an XPath node-set resulting from a null URI or shortname XPointer dereference, then comment nodes will have been omitted. If the actual input is an octet stream, then the application MUST convert the octet stream to an XPath node-set suitable for use by Canonical XML with Comments. (A subsequent application of the REQUIRED Canonical XML algorithm would strip away these comments.) In other words, the input node-set should be equivalent to the one that would be created by the following process:

  1. Initialize an XPath evaluation context by setting the initial node equal to the input XML document's root node, and set the context position and size to 1.
  2. Evaluate the XPath expression (//. | //@* | //namespace::*)

The evaluation of this expression includes all of the document's nodes (including comments) in the node-set representing the octet stream.

The transform output is (削除) also (削除ここまで) (追記) always (追記ここまで) an XPath node-set. The XPath expression appearing in the XPath parameter is evaluated once for each node in the input node-set. The result is converted to a boolean. If the boolean is true, then the node is included in the output node-set. If the boolean is false, then the node is omitted from the output node-set.

Note: Even if the input node-set has had comments removed, the comment nodes still exist in the underlying parse tree and can separate text nodes. For example, the markup <e>Hello, <!-- comment -->world!</e> contains two text nodes. Therefore, the expression self::text()[string()="Hello, world!"] would fail. Should this problem arise in the application, it can be solved by either canonicalizing the document before the XPath transform to physically remove the comments or by matching the node based on the parent element's string value (e.g. by using the expression self::text()[string(parent::e)="Hello, world!"] ).

The primary purpose of this transform is to ensure that only specifically defined changes to the input XML document are permitted after the signature is affixed. This is done by omitting precisely those nodes that are allowed to change once the signature is affixed, and including all other input nodes in the output. It is the responsibility of the XPath expression author to include all nodes whose change could affect the interpretation of the transform output in the application context.

Note that the XML-Signature XPath Filter 2.0 Recommendation [ (削除) XPath-Filter-2 (削除ここまで) (追記) XMLDSIG-XPATH-FILTER2 (追記ここまで) ] may be used for this purpose. (削除) This (削除ここまで) (追記) That (追記ここまで) recommendation defines an XPath transform that permits the easy specification of subtree selection and omission that can be efficiently implemented.

An important scenario would be a document requiring two enveloped signatures. Each signature must omit itself from its own digest calculations, but it is also necessary to exclude the second signature element from the digest calculations of the first signature so that adding the second signature does not break the first signature.

The XPath transform establishes the following evaluation context for each node of the input node-set:

  • A context node equal to a node of the input node-set.
  • A context position , initialized to 1.
  • A context size , initialized to 1.
  • A library of functions equal to the function set defined in [ (削除) XPath] (削除ここまで) (追記) XPATH (追記ここまで) (削除) plus (削除ここまで) (追記) ] augmented with (追記ここまで) a function named here (削除) . (削除ここまで) (追記) to be treated as if part of the library (and not namespace prefixed). (追記ここまで)
  • A set of variable bindings. No means for initializing these is defined. Thus, the set of variable bindings used when evaluating the XPath expression is empty, and use of a variable reference in the XPath expression results in an error.
  • The set of namespace declarations in scope for the XPath expression.

As a result of the context node setting, the XPath expressions appearing in this transform will be quite similar to those used in used in [ XSLT ], except that the size and position are always 1 to reflect the fact that the transform is automatically visiting every node (in XSLT, one recursively calls the command apply-templates to visit the nodes of the input tree).

The function here() is defined as follows:

Function: node-set here ()

The here function returns a node-set containing the attribute or processing instruction node or the parent element of the text node that directly bears the XPath expression. This expression results in an error if the containing XPath expression does not appear in the same XML document against which the XPath expression is being evaluated.

As an example, consider creating an enveloped signature (a Signature element that is a descendant of an element being signed). Although the signed content should not be changed after signing, the elements within the Signature element are changing (e.g. the digest value must be put inside the DigestValue and the SignatureValue must be subsequently calculated). One way to prevent these changes from invalidating the digest value in DigestValue is to add an XPath Transform that omits all Signature elements and their descendants. For example,

(削除) <Document> ... <Signature xmlns="http://www.w3.org/2000/09/xmldsig#"> <SignedInfo> (削除ここまで)
Example 23
<Document>
(追記) ... 
 (追記ここまで) <Signaturexmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo>
 ...
(削除) <Reference URI="">
 <Transforms>
 <Transform Algorithm="http://www.w3.org/TR/1999/REC-xpath-19991116">
 <XPath xmlns:dsig="&dsig;">
 not(ancestor-or-self::dsig:Signature)
 </XPath>
 </Transform>
 </Transforms>
 <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
 <DigestValue></DigestValue>
 </Reference>
 </SignedInfo>
 <SignatureValue></SignatureValue>
 </Signature>
 ...
 </Document>
 (削除ここまで)
 <ReferenceURI=""><Transforms><TransformAlgorithm="http://www.w3.org/TR/1999/REC-xpath-19991116"><XPathxmlns:dsig="&dsig;">
(追記) not(ancestor-or-self::dsig:Signature)
 (追記ここまで) </XPath></Transform></Transforms><DigestMethodAlgorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue></DigestValue></Reference></SignedInfo><SignatureValue></SignatureValue></Signature>(追記) 
 ...
 (追記ここまで)(追記) 
</Document>
 (追記ここまで)

Due to the null Reference URI in this example, the XPath transform input node-set contains all nodes in the entire parse tree starting at the root node (except the comment nodes). For each node in this node-set, the node is included in the output node-set except if the node or one of its ancestors has a tag of Signature that is in the namespace given by the replacement text for the entity &dsig; .

A more elegant solution uses the here function to omit only the Signature containing the XPath Transform, thus allowing enveloped signatures to sign other signatures. In the example above, use the XPath element:

(削除) <XPath xmlns:dsig="&dsig;"> count(ancestor-or-self::dsig:Signature | here()/ancestor::dsig:Signature[1]) > count(ancestor-or-self::dsig:Signature)</XPath> (削除ここまで)
Example 24
<XPathxmlns:dsig="&dsig;">
(追記) count(ancestor-or-self::dsig:Signature |
here()/ancestor::dsig:Signature[1]) >
count(ancestor-or-self::dsig:Signature)
 (追記ここまで)(追記) 
</XPath>
 (追記ここまで)

Since the XPath equality operator converts node sets to string values before comparison, we must instead use the XPath union operator (|). For each node of the document, the predicate expression is true if and only if the node-set containing the node and its Signature element ancestors does not include the enveloped Signature element containing the XPath expression (the union does not produce a larger set if the enveloped Signature element is in the node-set given by ancestor-or-self::Signature ).

6.6.4 Enveloped Signature Transform

Identifier:
http://www.w3.org/2000/09/xmldsig#enveloped-signature
(追記) Input: (追記ここまで)
(追記) node-set (追記ここまで)
(追記) Output: (追記ここまで)
(追記) node-set (追記ここまで)

An enveloped signature transform T removes the whole Signature element containing T from the digest calculation of the Reference element containing T . The entire string of characters used by an XML processor to match the Signature with the XML production element is removed. The output of the transform is equivalent to the output that would result from replacing T with an XPath transform containing the following XPath parameter element:

(削除) <XPath xmlns:dsig="&dsig;"> count(ancestor-or-self::dsig:Signature | here()/ancestor::dsig:Signature[1]) > count(ancestor-or-self::dsig:Signature)</XPath> (削除ここまで)
Example 25
<XPathxmlns:dsig="&dsig;">
(追記) count(ancestor-or-self::dsig:Signature |
here()/ancestor::dsig:Signature[1]) >
count(ancestor-or-self::dsig:Signature)
 (追記ここまで)(追記) 
</XPath>
 (追記ここまで)

The input and output requirements of this transform are identical to those of the XPath transform, but may only be applied to a node-set from its parent XML document. Note that it is not necessary to use an XPath expression evaluator to create this transform. However, this transform MUST produce output in exactly the same manner as the XPath transform parameterized by the XPath expression above.

6.6.5 XSLT Transform

Identifier:
http://www.w3.org/TR/1999/REC-xslt-19991116
(追記) Input: (追記ここまで)
(追記) octet-stream (追記ここまで)
(追記) Output: (追記ここまで)
(追記) octet-stream (追記ここまで)

The normative specification for XSL Transformations is [ XSLT ]. Specification of a namespace-qualified stylesheet element, which MUST be the sole child of the Transform element, indicates that the specified style sheet should be used. Whether this instantiates in-line processing of local XSLT declarations within the resource is determined by the XSLT processing model; the ordered application of multiple stylesheet may require multiple Transforms . No special provision is made for the identification of a remote stylesheet at a given URI because it can be communicated via an xsl:include or xsl:import within the stylesheet child of the Transform .

This transform requires an octet stream as input. (削除) If the actual input is an XPath node-set, then the signature application should attempt to convert it to octets (apply Canonical XML ]) as described in the Reference Processing Model (section 4.3.3.2). (削除ここまで)

The output of this transform is an octet stream. The processing rules for the XSL style sheet (追記) [ (追記ここまで)(追記) XSL10 (追記ここまで) (追記) ] (追記ここまで) or transform element are stated in the XSLT specification [ XSLT ].

We RECOMMEND that XSLT transform authors use an output method of xml for XML and HTML. As XSLT implementations do not produce consistent serializations of their output, we further RECOMMEND inserting a transform after the XSLT transform to canonicalize the output. These steps will help to ensure interoperability of the resulting signatures among applications that support the XSLT transform. Note that if the output is actually HTML, then the result of these steps is logically equivalent [ (削除) XHTML (削除ここまで) (追記) XHTML10 (追記ここまで) ].

(削除) 7.0 (削除ここまで) (追記) 7. (追記ここまで) XML Canonicalization and Syntax Constraint Considerations

Digital signatures only work if the verification calculations are performed on exactly the same bits as the signing calculations. If the surface representation of the signed data can change between signing and verification, then some way to standardize the changeable aspect must be used before signing and verification. For example, even for simple ASCII text there are at least three widely used line ending sequences. If it is possible for signed text to be modified from one line ending convention to another between the time of signing and signature verification, then the line endings need to be canonicalized to a standard form before signing and verification or the signatures will break.

XML is subject to surface representation changes and to processing which discards some surface information. For this reason, XML digital signatures have a provision for indicating canonicalization methods in the signature so that a verifier can use the same canonicalization as the signer.

Throughout this specification we distinguish between the canonicalization of a Signature element and other signed XML data objects. It is possible for an isolated XML document to be treated as if it were binary data so that no changes can occur. In that case, the digest of the document will not change and it need not be canonicalized if it is signed and verified as such. However, XML that is read and processed using standard XML parsing and processing techniques is frequently changed such that some of its surface representation information is lost or modified. In particular, this will occur in many cases for the Signature and enclosed SignedInfo elements since they, and possibly an encompassing XML document, will be processed as XML.

Similarly, these considerations apply to Manifest , Object , and SignatureProperties elements if those elements have been digested, their DigestValue is to be checked, and they are being processed as XML.

The kinds of changes in XML that may need to be canonicalized can be divided into four categories. There are those related to the basic [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ], as described in 7.1 below. There are those related to [ (削除) DOM (削除ここまで) (追記) DOM-LEVEL-1 (追記ここまで) ], [ SAX ], or similar processing as described in 7.2 below. Third, there is the possibility of coded character set conversion, such as between UTF-8 and UTF-16, both of which all [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ] compliant processors are required to support, which is described in the paragraph immediately below. And, fourth, there are changes that related to namespace declaration and XML namespace attribute context as described in 7.3 below.

Any canonicalization algorithm should yield output in a specific fixed coded character set. All canonicalization algorithms identified in this document use UTF-8 (without a byte order mark (BOM)) and do not provide character normalization. We RECOMMEND that signature applications create XML content ( Signature elements and their (削除) descendents/content) (削除ここまで) (追記) descendants/content) (追記ここまで) in Normalization Form C [ NFC (削除) , NFC-Corrigendum (削除ここまで) ] and check that any XML being consumed is in that form as well; (if not, signatures may consequently fail to validate). Additionally, none of these algorithms provide data type normalization. Applications that normalize data types in varying formats (e.g., (true, false) or (1,0)) may not be able to validate each other's signatures.

7.1 XML 1.0 (削除) , (削除ここまで) Syntax Constraints, and Canonicalization

XML 1.0 [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) (削除) ] (削除ここまで) (追記) ]] (追記ここまで) defines an interface where a conformant application reading XML is given certain information from that XML and not other information. In particular,

  1. line endings are normalized to the single character #xA by dropping #xD characters if they are immediately followed by a #xA and replacing them with #xA in all other cases,
  2. missing attributes declared to have default values are provided to the application as if present with the default value,
  3. character references are replaced with the corresponding character,
  4. entity references are replaced with the corresponding declared entity,
  5. attribute values are normalized by
    1. replacing character and entity references as above,
    2. replacing occurrences of #x9, #xA, and #xD with #x20 (space) except that the sequence #xD#xA is replaced by a single space, and
    3. if the attribute is not declared to be CDATA, stripping all leading and trailing spaces and replacing all interior runs of spaces with a single space.

Note that items (2), (4), and (5.3) depend on the presence of a schema, DTD or similar declarations. The Signature element type is laxly schema valid [ (削除) XML-schema (削除ここまで) (追記) XMLSCHEMA-1 (追記ここまで) (追記) ][ (追記ここまで)(追記) XMLSCHEMA-2 (追記ここまで) ], consequently external XML or even XML within the same document as the signature may be (only) well-formed or from another namespace (where permitted by the signature schema); the noted items may not be present. Thus, a signature with such content will only be verifiable by other signature applications if the following syntax constraints are observed when generating any signed material including the SignedInfo element:

  1. attributes having default values be explicitly present,
  2. all entity references (except "amp", "lt", "gt", "apos", "quot", and other character entities not representable in the encoding chosen) be expanded,
  3. attribute value white space be normalized

7.2 DOM/SAX Processing and Canonicalization

In addition to the canonicalization and syntax constraints discussed above, many XML applications use the Document Object Model [ (削除) DOM (削除ここまで) (追記) DOM-LEVEL-1 (追記ここまで) ] or the Simple API for XML [ SAX ]. DOM maps XML into a tree structure of nodes and typically assumes it will be used on an entire document with subsequent processing being done on this tree. SAX converts XML into a series of events such as a start tag, content, etc. In either case, many surface characteristics such as the ordering of attributes and insignificant white space within start/end tags is lost. In addition, namespace declarations are mapped over the nodes to which they apply, losing the namespace prefixes in the source text and, in most cases, losing where namespace declarations appeared in the original instance.

If an XML Signature is to be produced or verified on a system using the DOM or SAX processing, a canonical method is needed to serialize the relevant part of a DOM tree or sequence of SAX events. XML canonicalization specifications, such as [ XML-C14N ], are based only on information which is preserved by DOM and SAX. For an XML Signature to be verifiable by an implementation using DOM or SAX, not only must the XML 1.0 syntax constraints given in the (削除) previous (削除ここまで) section (追記) 7.1 XML 1.0 Syntax Constraints, and Canonicalization (追記ここまで) be followed but an appropriate XML canonicalization MUST be specified so that the verifier can re-serialize DOM/SAX mediated input into the same octet stream that was signed.

7.3 Namespace Context and Portable Signatures

In [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ] and consequently the Canonical XML data model an element has namespace nodes that correspond to those declarations within the element and its ancestors:

" Note: An element E has namespace nodes that represent its namespace declarations as well as any namespace declarations made by its ancestors that have not been overridden in E 's declarations, the default namespace if it is non-empty, and the declaration of the prefix xml ." [ XML-C14N ]

When serializing a Signature element or signed XML data that's the child of other elements using these data models, that Signature element and its (削除) children, (削除ここまで) (追記) children (追記ここまで) may (削除) contain namespace declarations (削除ここまで) (追記) have in-scope namespaces inherited (追記ここまで) from its (削除) ancestor (削除ここまで) (追記) ancestral (追記ここまで) context. In addition, the Canonical XML and Canonical XML with Comments algorithms (削除) import all xml namespace (削除ここまで) (追記) define special treatment for (追記ここまで) attributes (削除) (such (削除ここまで) (追記) in the XML namespace, which can cause them to be part of the canonicalized XML even if they were outside of the document subset. Simple inheritable attributes (i.e. attributes that have a value that requires at most a simple redeclaration such (追記ここまで) as xml:lang (追記) and (追記ここまで)(追記) xml:space (追記ここまで) ) (追記) are inherited (追記ここまで) from (削除) the (削除ここまで) nearest ancestor in which they are declared to the apex node of canonicalized XML unless they are already declared at that node. This may frustrate the intent of the signer to create a signature in one context which remains valid in another. For example, given a signature which is a child of B and a grandchild of A :

(削除) <A xmlns:n1="&foo;"> <B xmlns:n2="&bar;"> <Signature xmlns="&dsig;"> ... <Reference URI="#signme"/> ... </Signature> <C ID="signme" xmlns="&baz;"/> </B> </A> (削除ここまで)
Example 26
<Axmlns:n1="http://foo.example"><Bxmlns:n2="http://bar.example"><Signaturexmlns="http://www.w3.org/2000/09/xmldsig#">
(追記) ...
 (追記ここまで) <ReferenceURI="#signme"/> ... </Signature><CID="signme"xmlns="http://baz.example"/></B>(追記) 
</A>
 (追記ここまで)

when either the element B or the signed element C is moved into a [ (削除) SOAP (削除ここまで) (追記) SOAP12-PART1 (追記ここまで) ] envelope for transport:

(削除) <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> ... <SOAP:Body> <B xmlns:n2="&bar;"> <Signature xmlns="&dsig;"> ... </Signature> <C ID="signme" xmlns="&baz;"/> </B> </SOAP:Body> </SOAP:Envelope> (削除ここまで)
Example 27
<SOAP:Envelopexmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
(追記) ...
 (追記ここまで) <SOAP:Body><Bxmlns:n2="http://bar.example"><Signaturexmlns="http://www.w3.org/2000/09/xmldsig#">(追記) 
 ...
 (追記ここまで) </Signature><CID="signme"xmlns="http://baz.example"/></B></SOAP:Body>(追記) 
</SOAP:Envelope>
 (追記ここまで)

The canonical form of the signature in this context will contain new namespace declarations from the SOAP:Envelope context, invalidating the signature. Also, the canonical form will lack namespace declarations it may have originally had from element A 's context, also invalidating the signature. To avoid these problems, the application may:

  1. Rely upon the enveloping application to properly divorce its body (the signature payload) from the context (the envelope) before the signature is validated. Or,
  2. Use a canonicalization method that "repels/excludes" instead of "attracts" ancestor context. [ XML-C14N ] purposefully attracts such context.

(削除) 8.0 (削除ここまで) (追記) 8. (追記ここまで) Security Considerations

The XML Signature specification provides a very flexible digital signature mechanism. (削除) Implementors (削除ここまで) (追記) Implementers (追記ここまで) must give consideration to their application threat models and to the following factors. (追記) For additional security considerations in implementation and deployment of this specification, see [ (追記ここまで)(追記) XMLDSIG-BESTPRACTICES (追記ここまで) (追記) ]. (追記ここまで)

8.1 Transforms

A requirement of this specification is to permit signatures to "apply to a part or totality of a XML document." (See [ (削除) XML-Signature-RD , (削除ここまで) (追記) XMLDSIG-REQUIREMENTS (追記ここまで) (追記) ], (追記ここまで) section 3.1.3].) The Transforms mechanism meets this requirement by permitting one to sign data derived from processing the content of the identified resource. For instance, applications that wish to sign a form, but permit users to enter limited field data without invalidating a previous signature on the form might use [ (削除) XPath (削除ここまで) (追記) XPATH (追記ここまで) ] to exclude those portions the user needs to change. Transforms may be arbitrarily specified and may include encoding transforms, canonicalization instructions or even XSLT transformations. Three cautions are raised with respect to this feature in the following sections.

Note, core validation behavior does not confirm that the signed data was obtained by applying each step of the indicated transforms. (Though it does check that the digest of the resulting content matches that specified in the signature.) For example, some applications may be satisfied with verifying an XML signature over a cached copy of already transformed data. Other applications might require that content be freshly dereferenced and transformed.

(削除) 8.1.1 (削除ここまで) (追記) 8.1.1 (追記ここまで) Only What is Signed is Secure

First, obviously, signatures over a transformed document do not secure any information discarded by transforms: only what is signed is secure.

Note that the use of Canonical XML [ XML-C14N ] ensures that all internal entities and XML namespaces are expanded within the content being signed. All entities are replaced with their definitions and the canonical form explicitly represents the namespace that an element would otherwise inherit. Applications that do not canonicalize XML content (especially the SignedInfo element) SHOULD NOT use internal entities and SHOULD represent the namespace explicitly within the content being signed since they can not rely upon canonicalization to do this for them. Also, users concerned with the integrity of the element type definitions associated with the XML instance being signed may wish to sign those definitions as well (i.e., the schema, DTD, or natural language description associated with the namespace/identifier).

Second, an envelope containing signed information is not secured by the signature. For instance, when an encrypted envelope contains a signature, the signature does not protect the authenticity or integrity of unsigned envelope headers nor its ciphertext form, it only secures the plaintext actually signed.

8.1.2 Only What is "Seen" Should be Signed

Additionally, the signature secures any information introduced by the transform: only what is "seen" (that which is represented to the user via visual, auditory or other media) should be signed. If signing is intended to convey the judgment or consent of a user (an automated mechanism or person), then it is normally necessary to secure as exactly as practical the information that was presented to that user. Note that this can be accomplished by literally signing what was presented, such as the screen images shown a user. However, this may result in data which is difficult for subsequent software to manipulate. Instead, one can sign the data along with whatever filters, style sheets, client profile or other information that affects its presentation.

8.1.3 "See" What is Signed

Just as a user should only sign what he or she "sees," persons and automated mechanism that trust the validity of a transformed document on the basis of a valid signature should operate over the data that was transformed (including canonicalization) and signed, not the original pre-transformed data. This recommendation applies to transforms specified within the signature as well as those included as part of the document itself. For instance, if an XML document includes an embedded style sheet [ XSLT ] it is the transformed document that should be represented to the user and signed. To meet this recommendation where a document references an external style sheet, the content of that external resource should also be signed as via a signature Reference otherwise the content of that external content might change which alters the resulting document without invalidating the signature.

Some applications might operate over the original or intermediary data but should be extremely careful about potential weaknesses introduced between the original and transformed data. This is a trust decision about the character and meaning of the transforms that an application needs to make with caution. Consider a canonicalization algorithm that normalizes character case (lower to upper) or character composition ('e and accent' to 'accented-e'). An adversary could introduce changes that are normalized and consequently inconsequential to signature validity but material to a DOM processor. For instance, by changing the case of a character one might influence the result of an XPath selection. A serious risk is introduced if that change is normalized for signature validation but the processor operates over the original data and returns a different result than intended.

As a result:

  • All documents operated upon and generated by signature applications MUST be in [ NFC (削除) , NFC-Corrigendum (削除ここまで) ] (otherwise intermediate processors might unintentionally break the signature)
  • Encoding normalizations SHOULD NOT be done as part of a signature transform, or (to state it another way) if normalization does occur, the application SHOULD always "see" (operate over) the normalized form.

8.2 Check the Security Model

This specification uses public key signatures and keyed hash authentication codes. These have substantially different security models. Furthermore, it permits user specified algorithms which may have other models.

With public key signatures, any number of parties can hold the public key and verify signatures while only the parties with the private key can create signatures. The number of holders of the private key should be minimized and preferably be one. Confidence by verifiers in the public key they are using and its binding to the entity or capabilities represented by the corresponding private key is an important issue, usually addressed by certificate or online authority systems.

Keyed hash authentication codes, based on secret keys, are typically much more efficient in terms of the computational effort required but have the characteristic that all verifiers need to have possession of the same key as the signer. Thus any verifier can forge signatures.

This specification permits user provided signature algorithms and keying information designators. Such user provided algorithms may have different security models. For example, methods involving biometrics usually depend on a physical characteristic of the authorized user that can not be changed the way public or secret keys can be and may have other security model differences.

8.3 Algorithms, Key (削除) Lengths , (削除ここまで) (追記) Lengths, (追記ここまで) Certificates, Etc.

The strength of a particular signature depends on all links in the security chain. This includes the signature and digest algorithms used, the strength of the key generation [ RANDOM ] and the size of the key, the security of key and certificate authentication and distribution mechanisms, certificate chain validation policy, protection of cryptographic processing from hostile observation and tampering, etc.

Care must be exercised by applications in executing the various algorithms that may be specified in an XML signature and in the processing of any "executable content" that might be provided to such algorithms as parameters, such as XSLT transforms. The algorithms specified in this document will usually be implemented via a trusted library but even there perverse parameters might cause unacceptable processing or memory demand. Even more care may be warranted with application defined algorithms.

The security of an overall system will also depend on the security and integrity of its operating procedures, its personnel, and on the administrative enforcement of those procedures. All the factors listed in this section are important to the overall security of a system; however, most are beyond the scope of this specification.

(追記) 8.4 (追記ここまで)(追記) Error Messages (追記ここまで)

(追記) Implementations (追記ここまで)(追記) SHOULD NOT (追記ここまで)(追記) provide detailed error responses related to security algorithm processing. Error messages should be limited to a generic error message to avoid providing information to a potential attacker related to the specifics of the algorithm implementation. For example, if an error occurs in signature verification processing the error response should be a generic message providing no specifics on the details of the processing error. (追記ここまで)

(削除) 9.0 (削除ここまで) (追記) 9. (追記ここまで) Schema (削除) , DTD, Data Model, and Valid Examples (削除ここまで)

(追記) 9.1 (追記ここまで)(追記) XSD Schema (追記ここまで)

XML Signature (追記) Core (追記ここまで) Schema Instance
xmldsig-core-schema.xsd
Valid XML schema instance based on (削除) the 20001024 Schema/DTD (削除ここまで) [ (削除) XML-Schema ]. XML Signature DTD (削除ここまで) (削除) xmldsig-core-schema.dtd (削除ここまで) (追記) XMLSCHEMA-1 (追記ここまで) (削除) RDF Data Model (削除ここまで) (追記) ][ (追記ここまで) (削除) xmldsig-datamodel-20000112.gif (削除ここまで) (追記) XMLSCHEMA-2 (追記ここまで) (追記) ]. (追記ここまで)
XML Signature (削除) Object Example (削除ここまで) (追記) 1.1 Schema Instance (追記ここまで)
(削除) signature-example.xml (削除ここまで) (追記) xmldsig11-schema.xsd (追記ここまで)
(削除) A cryptographical fabricated XML example that includes foreign content and validates under the schema, it also uses schemaLocation to aid automated (削除ここまで) (追記) This (追記ここまで) schema (削除) fetching and validation. (削除ここまで) (追記) document defines the additional elements defined in this version of the XML Signature specification. (追記ここまで)
(削除) RSA (削除ここまで) XML Signature (削除) Example (削除ここまで) (追記) 1.1 Schema Driver (追記ここまで)
(削除) signature-example-rsa.xml (削除ここまで) (追記) xmldsig1-schema.xsd (追記ここまで)
(削除) An (削除ここまで) (追記) This schema instance binds together the (追記ここまで) XML Signature (削除) example with generated cryptographic values by Merlin Hughes (削除ここまで) (追記) Core Schema Instance (追記ここまで) and (削除) validated by Gregor Karlinger. DSA (削除ここまで) (追記) the (追記ここまで) XML Signature (削除) Example (削除ここまで) (追記) 1.1 Schema Instance (追記ここまで)

(削除) signature-example-dsa.xml (削除ここまで) (追記) 9.2 (追記ここまで)(追記) RNG Schema (追記ここまで)

(追記) This section is non-normative. (追記ここまで)

(追記) Non-normative RELAX NG schema [ (追記ここまで)(追記) RELAXNG-SCHEMA (追記ここまで) (削除) Similar to above but uses DSA. 10.0 Definitions (削除ここまで) (追記) ] information is available in a separate document [ (追記ここまで)(追記) XMLSEC-RELAXNG (追記ここまで) (追記) ]. (追記ここまで)

(追記) 10. (追記ここまで)(追記) Definitions (追記ここまで)

Authentication Code ( Protected Checksum )
A value generated from the application of a shared key to a message via a cryptographic algorithm such that it has the properties of message authentication (and integrity ) but not signer authentication . Equivalent to protected checksum , "A checksum that is computed for a data object by means that protect against active attacks that would attempt to change the checksum to make it match changes made to the data object." [ (削除) SEC (削除ここまで) (追記) RFC4949 (追記ここまで) ]
Authentication, Message
The property, given an authentication code / protected checksum , that tampering with both the data and checksum, so as to introduce changes while seemingly preserving integrity , are still detected. "A signature should identify what is signed, making it impracticable to falsify or alter either the signed matter or the signature without detection." [ (削除) Digital Signature Guidelines , ABA (削除ここまで) (追記) ABA-DSIG-GUIDELINES (追記ここまで) ].
Authentication, Signer
The property that the identity of the signer is as claimed. "A signature should indicate who signed a document, message or record, and should be difficult for another person to produce without authorization." [ (削除) Digital Signature Guidelines , ABA (削除ここまで) (追記) ABA-DSIG-GUIDELINES (追記ここまで) ] Note, signer authentication is an application decision (e.g., does the signing key actually correspond to a specific identity) that is supported by, but out of scope, of this specification.
Checksum
"A value that (a) is computed by a function that is dependent on the contents of a data object and (b) is stored or transmitted together with the object, for the purpose of detecting changes in the data." [ (削除) SEC (削除ここまで) (追記) RFC4949 (追記ここまで) ]
Core
The syntax and processing defined by this specification, including core validation . We use this term to distinguish other markup, processing, and applications semantics from our own.
Data Object (Content/Document)
The actual binary/octet data being operated on (transformed, digested, or signed) by an application -- frequently an HTTP entity [ (削除) HTTP (削除ここまで) (追記) HTTP11 (追記ここまで) ]. Note that the proper noun Object designates a specific XML element. Occasionally we refer to a data object as a document or as a resource 's content . The term element content is used to describe the data between XML start and end tags [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ]. The term XML document is used to describe data objects which conform to the XML specification [ (削除) XML (削除ここまで) (追記) XML10 (追記ここまで) ].
Integrity
"The property that data has not been changed, destroyed, or lost in an unauthorized or accidental manner." [ (削除) SEC (削除ここまで) (追記) RFC4949 (追記ここまで) ] A simple checksum can provide integrity from incidental changes in the data; message authentication is similar but also protects against an active attack to alter the data whereby a change in the checksum is introduced so as to match the change in the data.
Object
An XML Signature element wherein arbitrary (non- core ) data may be placed. An Object element is merely one type of digital data (or document) that can be signed via a Reference .
Resource
"A resource can be anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., 'today's weather report for Los Angeles'), and a collection of other resources.... The resource is the conceptual mapping to an entity or set of entities, not necessarily the entity which corresponds to that mapping at any particular instance in time. Thus, a resource can remain constant even when its content---the entities to which it currently corresponds---changes over time, provided that the conceptual mapping is not changed in the process." [ URI ] In order to avoid a collision of the term entity within the URI and XML specifications, we use the term data object , content or document to refer to the actual bits/octets being operated upon.
Signature
Formally speaking, a value generated from the application of a private key to a message via a cryptographic algorithm such that it has the properties of integrity , message authentication and/or signer authentication . (However, we sometimes use the term signature generically such that it encompasses Authentication Code values as well, but we are careful to make the distinction when the property of signer authentication is relevant to the exposition.) A signature may be (non-exclusively) described as detached , enveloping , or enveloped .
Signature, Application
An application that implements the MANDATORY (削除) (REQUIRED/MUST) (削除ここまで) (追記) ( (追記ここまで)(追記) REQUIRED (追記ここまで)(追記) / (追記ここまで)(追記) MUST (追記ここまで)(追記) ) (追記ここまで) portions of this specification; these conformance requirements are over application behavior, the structure of the Signature element type and its children (including SignatureValue ) and the specified algorithms.
Signature, Detached
The signature is over content external to the Signature element, and can be identified via a URI or transform. Consequently, the signature is "detached" from the content it signs. This definition typically applies to separate data objects, but it also includes the instance where the Signature and data object reside within the same XML document but are sibling elements.
Signature, Enveloping
The signature is over content found within an Object element of the signature itself. The Object (or its content) is identified via a Reference (via a URI fragment identifier or transform).
Signature, Enveloped
The signature is over the XML content that contains the signature as an element. The content provides the root XML document element. Obviously, enveloped signatures must take care not to include their own value in the calculation of the SignatureValue .
Transform
The processing of a data from its source to its derived form. Typical transforms include XML Canonicalization, XPath, and XSLT.
Validation, Core
The core processing requirements of this specification requiring signature validation and SignedInfo reference validation .
Validation, Reference
The hash value of the identified and transformed content, specified by Reference , matches its specified DigestValue .
Validation, Signature
The SignatureValue matches the result of processing SignedInfo with CanonicalizationMethod and SignatureMethod as specified in Core Validation (section 3.2).
Validation, Trust/Application
The application determines that the semantics associated with a signature are valid. For example, an application may validate the time stamps or the integrity of the signer key -- though this behavior is external to this core specification.

(削除) 11.0 References (削除ここまで) (追記) A. (追記ここまで)(追記) References (追記ここまで)

(削除) ABA (削除ここまで)

(追記) Dated references below are to the latest known or appropriate edition of the referenced work. The referenced works may be subject to revision, and conformant implementations may follow, and are encouraged to investigate the appropriateness of following, some or all more recent editions or replacements of the works cited. It is in each case implementation-defined which editions are supported. (追記ここまで)

(追記) A.1 (追記ここまで)(追記) Normative references (追記ここまで)

(追記) [ECC-ALGS] (追記ここまで)
(追記) D. McGrew; K. Igoe; M. Salter. (追記ここまで) (削除) Digital Signature Guidelines. (削除ここまで) (追記) RFC 6090: Fundamental Elliptic Curve Cryptography Algorithms (追記ここまで) (削除) http://www.abanet.org/scitech/ec/isc/dsgfree.html (削除ここまで) . (追記) February 2011. IETF Informational RFC. URL: (追記ここまで)(追記) http://www.rfc-editor.org/rfc/rfc6090.txt (追記ここまで)
(削除) DOM (削除ここまで)
(追記) [FIPS-180-3] (追記ここまで)
(削除) Document Object Model (DOM) Level 1 Specification. W3C Recommendation. V. Apparao, S. Byrne, M. Champion, S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, R. Sutor, C. Wilson, L. Wood. October 1998. http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/ (削除ここまで) (追記) FIPS PUB 180-3 Secure Hash Standard (追記ここまで) (削除) DSS (削除ここまで) . (追記) U.S. Department of Commerce/National Institute of Standards and Technology. URL: (追記ここまで)(追記) http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf (追記ここまで)
(追記) [FIPS-186-3] (追記ここまで)
FIPS PUB (削除) 186-2 . (削除ここまで) (追記) 186-3: (追記ここまで) Digital Signature Standard (削除) (DSS). (削除ここまで) (追記) (DSS) (追記ここまで).(追記) June 2009. (追記ここまで) U.S. Department of Commerce/National Institute of Standards and Technology. (削除) http://csrc.nist.gov/publications/fips/fips186-2/fips186-2-change1.pdf (削除ここまで) (追記) URL: (追記ここまで)(追記) http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf (追記ここまで)
(削除) HMAC (削除ここまで)
(追記) [HMAC] (追記ここまで)
(削除) RFC 2104 . HMAC: Keyed-Hashing for Message Authentication. (削除ここまで)
H. Krawczyk, M. Bellare, R. Canetti. (追記) HMAC: Keyed-Hashing for Message Authentication (追記ここまで). February 1997. (追記) IETF RFC 2104. URL: (追記ここまで) http://www.ietf.org/rfc/rfc2104.txt
(削除) HTTP (削除ここまで)
(追記) [HTTP11] (追記ここまで)
(追記) R. Fielding et al. (追記ここまで) (削除) RFC 2616 . (削除ここまで) Hypertext Transfer Protocol (削除) -- (削除ここまで) (追記) - (追記ここまで) HTTP/1.1 (削除) . J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee. (削除ここまで) . June 1999. (追記) RFC 2616. URL: (追記ここまで) http://www.ietf.org/rfc/rfc2616.txt
(削除) KEYWORDS (削除ここまで)
(追記) [LDAP-DN] (追記ここまで)
(削除) RFC 2119. Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. March 1997. http://www.ietf.org/rfc/rfc2119.txt (削除ここまで) (削除) LDAP-DN (削除ここまで)
(追記) K. Zeilenga. (追記ここまで) (削除) RFC4514 . (削除ここまで) Lightweight Directory Access Protocol : String Representation of Distinguished (削除) Names. K. Zeilenga, Ed. (削除ここまで) (追記) Names (追記ここまで). June 2006. (追記) IETF RFC 4514. URL: (追記ここまで) http://www.ietf.org/rfc/rfc4514.txt
(削除) MD5 (削除ここまで)
(追記) [NFC] (追記ここまで)
(追記) M. Davis, Ken Whistler. (追記ここまで)(追記) TR15, Unicode Normalization Forms. (追記ここまで).(追記) 17 September 2010, URL: (追記ここまで)(追記) http://www.unicode.org/reports/tr15/ (追記ここまで)
(追記) [PGP] (追記ここまで)
(追記) J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer. (追記ここまで)(追記) OpenPGP Message Format (追記ここまで) (削除) RFC 1321 (削除ここまで) . (削除) The MD5 Message-Digest Algorithm. R. Rivest. April 1992. http://www.ietf.org/rfc/rfc1321.txt (削除ここまで) (追記) IETF RFC 4880. November 2007. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc4880.txt (追記ここまで)
(削除) MIME (削除ここまで)
(追記) [PKCS1] (追記ここまで)
(追記) J. Jonsson and B. Kaliski. (追記ここまで)(追記) Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1. (追記ここまで) (追記) RFC 3447 (Informational), February 2003. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc3447.txt (追記ここまで)
(追記) [RFC2045] (追記ここまで)
(追記) N. Freed and N. Borenstein. (追記ここまで) (削除) RFC 2045 . (削除ここまで) Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message (削除) Bodies . N. Freed & N. Borenstein. (削除ここまで) (追記) Bodies. (追記ここまで) November 1996. (追記) URL: (追記ここまで) http://www.ietf.org/rfc/rfc2045.txt
(削除) NFC (削除ここまで)
(追記) [RFC2119] (追記ここまで)
(削除) TR15, Unicode Normalization Forms. M. Davis, M. Dürst. Revision 18: November 1999. http://www.unicode.org/unicode/reports/tr15/tr15-18.html . NFC-Corrigendum (削除ここまで)
(追記) S. Bradner. (追記ここまで) (削除) Normalization Corrigendum . The Unicode Consortium. http://www.unicode.org/unicode/uni2errata/Normalization_Corrigendum.html . (削除ここまで) (追記) Key words for use in RFCs to Indicate Requirement Levels. (追記ここまで) (削除) PGP (削除ここまで) (追記) March 1997. Internet (追記ここまで) RFC (削除) 2440 . OpenPGP Message Format. J. Callas, L. Donnerhacke, H. Finney, R. Thayer. November 1998. http://www.ietf.org/rfc/rfc2440.txt (削除ここまで) (追記) 2119. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc2119.txt (追記ここまで)
(削除) RANDOM (削除ここまで)
(追記) [RFC3279] (追記ここまで)
(追記) W. Polk, R. Housley, L. Bassham. (追記ここまで) (削除) RFC 1750 . Randomness Recommendations (削除ここまで) (追記) Algorithmupdates and Identifiers (追記ここまで) for (削除) Security. D. Eastlake, S. Crocker, J. Schiller. December 1994. http://www.ietf.org/rfc/rfc1750.txt (削除ここまで) (追記) the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (追記ここまで) (削除) RDF (削除ここまで) . (追記) April 2002. Internet RFC 3279. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc3279.txt (追記ここまで)
(追記) [RFC3406] (追記ここまで)
(削除) Resource Description Framework (RDF) Schema Specification 1.0. W3C Candidate Recommendation. (削除ここまで)
(追記) L. Daigle, (追記ここまで) D. (削除) Brickley, R.V. Guha. March 2000. http://www.w3.org/TR/2000/CR-rdf-schema-20000327/ (削除ここまで) (追記) van Gulik, R. Iannella, P. Faltstrom. (追記ここまで) (追記) URN Namespace Definition Mechanisms. (追記ここまで) (削除) Resource Description Framework (RDF) Model and Syntax Specification (削除ここまで) . (削除) W3C Recommendation. O. Lassila, R. Swick. February 1999. http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/ (削除ここまで) (追記) IETF RFC 3406 October 2002. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc3406.txt (追記ここまで)
(削除) 1363 (削除ここまで)
(追記) [RFC4055] (追記ここまで)
(削除) IEEE 1363: Standard Specifications (削除ここまで) (追記) J. Schaad, B. Kaliski, R. Housley. (追記ここまで)(追記) Additional Algorithms and Identifiers for RSA Cryptography (追記ここまで) for (追記) use in the Internet X.509 (追記ここまで) Public Key (削除) Cryptography. August 2000. (削除ここまで) (追記) Infrastructure Certificate and Certificate Revocation List (CRL) Profile (追記ここまで) (削除) PKCS1 (削除ここまで) . (追記) June 2005. IETF RFC 4055. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc4055.txt (追記ここまで)
(追記) [RFC5280] (追記ここまで)
(追記) D. Cooper, et. al. (追記ここまで)(追記) Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile. (追記ここまで) (削除) RFC 2437 (削除ここまで) . (削除) PKCS #1: RSA Cryptography Specifications Version 2.0. B. Kaliski, J. Staddon. October 1998. http://www.ietf.org/rfc/rfc2437.txt (削除ここまで) (追記) IETF RFC 5280 May 2008. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc5280.txt (追記ここまで)
(削除) SAX (削除ここまで)
(追記) [RFC5480] (追記ここまで)
(削除) SAX: The Simple API for XML . D. Megginson, et (削除ここまで)
(追記) S. Turner, et. (追記ここまで) al. (削除) May 1998. http://www.megginson.com/downloads/SAX/ (削除ここまで) (追記) Elliptic Curve Cryptography Subject Public Key Information. (追記ここまで) (削除) SEC (削除ここまで) . (追記) IETF RFC 5480 March 2009. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc5480.txt (追記ここまで)
(追記) [RFC6931] (追記ここまで)
(追記) D. Eastlake 3rd. (追記ここまで) (削除) RFC 2828 . Internet (削除ここまで) (追記) Additional XML (追記ここまで) Security (削除) Glossary. R. Shirey. May 2000. http://www.faqs.org/rfcs/rfc2828.html (削除ここまで) (追記) Uniform Resource Identifiers (追記ここまで) (削除) SHA-1 (削除ここまで) . (追記) RFC 6931 April 2013. URL: (追記ここまで)(追記) http://tools.ietf.org/html/rfc6931 (追記ここまで)
(追記) [SP800-57] (追記ここまで)
(削除) FIPS PUB 180-2 (削除ここまで) (追記) Recommendation for Key Management – Part 1: General (Revision 3) (追記ここまで) . (削除) Secure Hash Standard. (削除ここまで) (追記) SP800-57. July 2012. (追記ここまで) U.S. Department of Commerce/National Institute of Standards and Technology. (削除) http://csrc.nist.gov/publications/fips/fips180-2/fips180-2withchangenotice.pdf (削除ここまで) (追記) URL: (追記ここまで)(追記) http://csrc.nist.gov/publications/nistpubs/800-57/sp800-57_part1_rev3_general.pdf (追記ここまで)
(削除) SOAP (削除ここまで)
(追記) [URI] (追記ここまで)
(削除) Simple Object Access Protocol (SOAP) Version 1.1 . W3C Note. D. Box, D. Ehnebuske, G. Kakivaya, A. Layman, N. Mendelsohn, H. Frystyk Nielsen, S. Thatte, D. Winer. May 2001. (削除ここまで)
(追記) T. Berners-Lee; R. Fielding; L. Masinter. (追記ここまで) (削除) http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ (削除ここまで) (追記) Uniform Resource Identifiers (URI): generic syntax (追記ここまで) (削除) TESTCASES (削除ここまで) . (追記) January 2005. RFC 3986. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc3986.txt (追記ここまで)
(追記) [URN] (追記ここまで)
(削除) Test Cases for C14N 1.1 and XMLDSig Interoperability . W3C Working Group Note. J.C. Cruellas, K. Lanz, S. Mullan. June 2008. (削除ここまで)
(追記) R. Moats. (追記ここまで) (削除) http://www.w3.org/TR/2008/NOTE-xmldsig2ed-tests-20080610/ (削除ここまで) (追記) URN Syntax. (追記ここまで) (削除) UTF-16 (削除ここまで) (追記) IETF RFC 2141. May 1997. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc2141.txt (追記ここまで)
(追記) [URN-OID] (追記ここまで)
(追記) M. Mealling. (追記ここまで) (削除) RFC 2781 . UTF-16, an encoding (削除ここまで) (追記) A URN Namespace (追記ここまで) of (削除) ISO 10646. P. Hoffman , F. Yergeau. (削除ここまで) (追記) Object Identifiers. (追記ここまで).(追記) IETF RFC 3061. (追記ここまで) February (削除) 2000. http://www.ietf.org/rfc/rfc2781.txt (削除ここまで) (追記) 2001. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc3061.txt (追記ここまで)
(削除) UTF-8 (削除ここまで)
(追記) [UTF-8] (追記ここまで)
(追記) F. Yergeau. (追記ここまで) (削除) RFC 2279 . (削除ここまで) UTF-8, a transformation format of ISO 10646 (削除) . F. Yergeau. January 1998. http://www.ietf.org/rfc/rfc2279.txt URI (削除ここまで) (削除) RFC 3986 (削除ここまで) . (削除) Uniform Resource Identifiers (URI): Generic Syntax. T. Berners-Lee, R. Fielding, L. Masinter. January 2005. http://www.ietf.org/rfc/rfc3986.txt URL (削除ここまで) (追記) IETF (追記ここまで) RFC (削除) 1738. Uniform Resource Locators (URL). T. Berners-Lee, L. Masinter, and M. McCahill. December 1994. http://www.ietf.org/rfc/rfc1738.txt (削除ここまで) (追記) 3629. November 2003. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc3629.txt (追記ここまで)
(削除) URN (削除ここまで)
(追記) [X509V3] (追記ここまで)
(削除) RFC 2141 . URN Syntax. R. Moats. May 1997. http://www.ietf.org/rfc/rfc2141.txt (削除ここまで)
(削除) RFC 2611 . URN Namespace Definition Mechanisms. L. Daigle, D. van Gulik, R. Iannella, P. Falstrom. June 1999. http://www.ietf.org/rfc/rfc2611.txt X509v3 (削除ここまで) ITU-T Recommendation X.509 version 3 (1997). "Information Technology - Open Systems Interconnection - The Directory Authentication Framework" ISO/IEC (削除) 9594-8:1997. (削除ここまで) (追記) 9594-8:1997 (追記ここまで).
(削除) XHTML (削除ここまで)
(追記) [XML-C14N] (追記ここまで)
(追記) John Boyer. (追記ここまで)(追記) Canonical XML Version (追記ここまで) 1.0 . (追記) 15 March 2001. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2001/REC-xml-c14n-20010315 (追記ここまで)
(追記) [XML-C14N11] (追記ここまで)
(追記) John Boyer; Glenn Marcy. (追記ここまで)(追記) Canonical XML Version 1.1 (追記ここまで) (削除) XHTML(tm) 1.0: The Extensible Hypertext Markup Language (削除ここまで) . (追記) 2 May 2008. (追記ここまで) W3C Recommendation. (削除) S. Pemberton, D. Raggett, et al. January 2000. http://www.w3.org/TR/2000/REC-xhtml1-20000126/ (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/ (追記ここまで)
(削除) XLink (削除ここまで)
(追記) [XML-EXC-C14N] (追記ここまで)
(追記) Donald E. Eastlake 3rd; Joseph Reagle; John Boyer. (追記ここまで) (追記) Exclusive (追記ここまで) XML (削除) Linking Language. (削除ここまで) (追記) Canonicalization Version 1.0 (追記ここまで).(追記) 18 July 2002. (追記ここまで) W3C Recommendation. (削除) S. DeRose, E. Maler, D. Orchard. June 2001. (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/ (追記ここまで)
(追記) [XML-MEDIA-TYPES] (追記ここまで)
(追記) Ümit Yalçınalp; Anish Karmarkar. (追記ここまで) (削除) http://www.w3.org/TR/2001/REC-xlink-20010627/ (削除ここまで) (追記) Describing Media Content of Binary Data in XML (追記ここまで) . (追記) 4 May 2005. W3C Note. URL: (追記ここまで)(追記) http://www.w3.org/TR/2005/NOTE-xml-media-types-20050504/ (追記ここまで)
(追記) [XML-NAMES] (追記ここまで)
(追記) Richard Tobin et al. (追記ここまで)(追記) Namespaces in (追記ここまで) XML (追記) 1.0 (Third Edition) (追記ここまで).(追記) 8 December 2009. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2009/REC-xml-names-20091208/ (追記ここまで)
(追記) [XML10] (追記ここまで)
(追記) C. M. Sperberg-McQueen et al. (追記ここまで) Extensible Markup Language (XML) 1.0 (削除) (Fourth Edition). (削除ここまで) (追記) (Fifth Edition) (追記ここまで).(追記) 26 November 2008. (追記ここまで) W3C (削除) Recommendation T. Bray, E. Maler, J. Paoli, C. M. Sperberg-McQueen, F.Yergeau. 16 August 2006, edited in place 29 September 2006. (削除ここまで) (追記) Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2008/REC-xml-20081126/ (追記ここまで)
(削除) http://www.w3.org/TR/2006/REC-xml-20060816/ (削除ここまで)
(追記) [XMLDSIG-XPATH-FILTER2] (追記ここまで)
(追記) Merlin Hughes; John Boyer; Joseph Reagle. (追記ここまで) (削除) XML-C14N (削除ここまで) (追記) XML-Signature XPath Filter 2.0 (追記ここまで).(追記) 8 November 2002. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/ (追記ここまで)
(追記) [XMLENC-CORE1] (追記ここまで)
(追記) J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. (追記ここまで) (削除) Canonical XML. (削除ここまで) (追記) XML Encryption Syntax and Processing Version 1.1 (追記ここまで).(追記) 11 April 2013. (追記ここまで) W3C Recommendation. (削除) J. Boyer. March 2001. (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2013/REC-xmlenc-core1-20130411/ (追記ここまで)
(追記) [XMLSCHEMA-1] (追記ここまで)
(追記) Henry S. Thompson et al. (追記ここまで) (削除) http://www.w3.org/TR/2001/REC-xml-c14n-20010315 (削除ここまで) (追記) XML Schema Part 1: Structures Second Edition (追記ここまで) (削除) http://www.ietf.org/rfc/rfc3076.txt (削除ここまで) . (追記) 28 October 2004. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/ (追記ここまで)
(削除) XML-C14N11 (削除ここまで)
(追記) [XMLSCHEMA-2] (追記ここまで)
(追記) Paul V. Biron; Ashok Malhotra. (追記ここまで) (削除) Canonical (削除ここまで) XML (削除) 1.1. (削除ここまで) (追記) Schema Part 2: Datatypes Second Edition (追記ここまで).(追記) 28 October 2004. (追記ここまで) W3C Recommendation. (削除) J. Boyer, G. Marcy. 2 May 2008. http://www.w3.org/TR/2008/REC-xml-c14n11-20080502/ (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/ (追記ここまで)
(削除) XML-exc-C14N (削除ここまで)
(追記) [XPATH] (追記ここまで)
(追記) James Clark; Steven DeRose. (追記ここまで) (削除) Exclusive (削除ここまで) XML (削除) Canonicalization (削除ここまで) (追記) Path Language (XPath) (追記ここまで) Version 1.0 . (追記) 16 November 1999. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/1999/REC-xpath-19991116/ (追記ここまで)
(追記) [XPTR-ELEMENT] (追記ここまで)
(追記) Norman Walsh et al. (追記ここまで)(追記) XPointer element() Scheme (追記ここまで).(追記) 25 March 2003. (追記ここまで) W3C Recommendation. (削除) J. Boyer, D. Eastlake 3rd., J. Reagle. July 2002. http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/ (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2003/REC-xptr-element-20030325/ (追記ここまで)
(追記) [XPTR-FRAMEWORK] (追記ここまで)
(追記) Paul Grosso et al. (追記ここまで)(追記) XPointer Framework (追記ここまで).(追記) 25 March 2003. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ (追記ここまで)
(削除) XML-Japanese (削除ここまで)
(追記) [XSL10] (追記ここまで)
(追記) Jeremy Richman et al. (追記ここまで)(追記) Extensible Stylesheet Language (XSL) Version 1.0 (追記ここまで).(追記) 15 October 2001. W3C Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/2001/REC-xsl-20011015/ (追記ここまで)
(追記) [XSLT] (追記ここまで)
(追記) James Clark. (追記ここまで)(追記) XSL Transformations (XSLT) Version 1.0 (追記ここまで) (削除) XML Japanese Profile (削除ここまで) . (追記) 16 November 1999. (追記ここまで) W3C (削除) Note. M. Murata (削除ここまで) (追記) Recommendation. URL: (追記ここまで)(追記) http://www.w3.org/TR/1999/REC-xslt-19991116 (追記ここまで)

(追記) A.2 (追記ここまで) (削除) April 2000 http://www.w3.org/TR/2000/NOTE-japanese-xml-20000414/ (削除ここまで) (追記) Informative references (追記ここまで)

(削除) XML-MT (削除ここまで)
(追記) [ABA-DSIG-GUIDELINES] (追記ここまで)
(追記) Digital Signature Guidelines (追記ここまで).(追記) 1 August 1996. Information Security Committee, American Bar Association. URL: (追記ここまで)(追記) http://www.signelec.com/content/download/digital_signature_guidelines.pdf (追記ここまで)
(追記) [CVE-2009-0217] (追記ここまで)
(削除) RFC 2376 . XML Media Types . E. Whitehead, M. Murata. July 1998. http://www.ietf.org/rfc/rfc2376.txt (削除ここまで) (追記) Common Vulnerabilities and Exposures List, CVE-2009-0217 (追記ここまで) (削除) XML-ns (削除ここまで) (追記) URL: (追記ここまで)(追記) http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0217 (追記ここまで)
(追記) [DOM-LEVEL-1] (追記ここまで)
(追記) Vidur Apparao et al. (追記ここまで)(追記) Document Object Model (DOM) Level 1 (追記ここまで) (削除) Namespaces in XML 1.0 (Second Edition) (削除ここまで) . (追記) 1 October 1998. (追記ここまで) W3C Recommendation. (削除) T. Bray, D. Hollander, A. Layman, R. Tobin. 16 August 2006. (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/ (追記ここまで)
(追記) [IEEE1363] (追記ここまで)
(削除) http://www.w3.org/TR/2006/REC-xml-names-20060816/ (削除ここまで) (追記) IEEE 1363: Standard Specifications for Public Key Cryptography (追記ここまで).(追記) August 2000. URL: (追記ここまで)(追記) http://grouper.ieee.org/groups/1363/ (追記ここまで)
(削除) XML-schema (削除ここまで)
(追記) [RANDOM] (追記ここまで)
(追記) D. Eastlake, S. Crocker, J. Schiller. (追記ここまで)(追記) Randomness Recommendations for Security. (追記ここまで).(追記) IETF RFC 4086. June 2005. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc4086.txt (追記ここまで)
(追記) [RDF-PRIMER] (追記ここまで)
(追記) Frank Manola; Eric Miller. (追記ここまで)(追記) RDF Primer (追記ここまで) (削除) XML Schema Part 1: Structures (削除ここまで) . (追記) 10 February 2004. (追記ここまで) W3C Recommendation. (削除) H. Thompson,D. Beech, M. Maloney, N. Mendelsohn. October 2004. (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2004/REC-rdf-primer-20040210/ (追記ここまで)
(追記) [RELAXNG-SCHEMA] (追記ここまで)
(削除) http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/ (削除ここまで) (削除) XML (削除ここまで) (追記) Information technology -- Document (追記ここまで) Schema (追記) Definition Language (DSDL) -- (追記ここまで) Part 2: (削除) Datatypes W3C Recommendation. P. Biron, A. Malhotra. May 2001. (削除ここまで) (追記) Regular-grammar-based validation -- RELAX NG (追記ここまで) (削除) http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/ (削除ここまで) . (追記) ISO/IEC 19757-2:2008. URL: (追記ここまで)(追記) http://standards.iso.org/ittf/PubliclyAvailableStandards/c052348_ISO_IEC_19757-2_2008(E).zip (追記ここまで)
(削除) XML-Signature-RD (削除ここまで)
(追記) [RFC4050] (追記ここまで)
(追記) S. Blake-Wilson; G. Karlinger; T. Kobayashi; Y. Wang. (追記ここまで) (削除) RFC 2807 . XML (削除ここまで) (追記) Using the Elliptic Curve (追記ここまで) Signature (削除) Requirements. W3C Working Draft. J. Reagle, (削除ここまで) (追記) Algorithm (ECDSA) for XML Digital Signatures (RFC 4050) (追記ここまで). April (削除) 2000. http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014 (削除ここまで) (追記) 2005. RFC. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc4050.txt (追記ここまで)
(削除) http://www.ietf.org/rfc/rfc2807.txt (削除ここまで)
(追記) [RFC4949] (追記ここまで)
(追記) R. Shirey. (追記ここまで) (削除) http://www.w3.org/TR/2002/REC-xmldsig-core-20020212// (削除ここまで) (追記) Internet Security Glossary, Version 2. (追記ここまで) (削除) XMLDSIG-2002 (削除ここまで) . (追記) IETF RFC 4949. August 2007. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc4949.txt (追記ここまで)
(追記) [SAX] (追記ここまで)
(追記) D. Megginson, et al. (追記ここまで)(追記) SAX: The Simple API for XML (追記ここまで) (削除) XML-Signature Syntax and Processing (削除ここまで) . (削除) D. Eastlake, J. Reagle, and D. Solo. W3C Recommendation, February 2002. (削除ここまで) (追記) May 1998. URL: (追記ここまで)(追記) http://www.megginson.com/downloads/SAX/ (追記ここまで)
(追記) [SHA-1-Analysis] (追記ここまで)
(追記) McDonald, C., Hawkes, P., and J. Pieprzyk. (追記ここまで) (削除) http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/ (削除ここまで) (追記) SHA-1 collisions now 2 (追記ここまで)(追記) 52 (追記ここまで) . (追記) EuroCrypt 2009 Rump session. URL: (追記ここまで)(追記) http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf (追記ここまで)
(削除) XPath (削除ここまで)
(追記) [SHA-1-Collisions] (追記ここまで)
(追記) X. Wang, Y.L. Yin, H. Yu. (追記ここまで)(追記) Finding Collisions in the Full SHA-1 (追記ここまで).(追記) In Shoup, V., editor, Advances in Cryptology - CRYPTO 2005, 25th Annual International Cryptology Conference, Santa Barbara, California, USA, August 14-18, 2005, Proceedings, volume 3621 of LNCS, pages 17–36. Springer, 2005. URL: (追記ここまで)(追記) http://people.csail.mit.edu/yiqun/SHA1AttackProceedingVersion.pdf (追記ここまで) (追記) (also published in (追記ここまで)(追記) http://www.springerlink.com/content/26vljj3xhc28ux5m/ (追記ここまで) (追記) ) (追記ここまで)
(追記) [SOAP12-PART1] (追記ここまで)
(追記) Noah Mendelsohn et al. (追記ここまで) (削除) XML Path Language (XPath) (削除ここまで) (追記) SOAP (追記ここまで) Version (削除) 1.0 (削除ここまで) (追記) 1.2 Part 1: Messaging Framework (Second Edition) (追記ここまで) . (追記) 27 April 2007. (追記ここまで) W3C Recommendation. (削除) J. Clark, S. DeRose. October 1999. http://www.w3.org/TR/1999/REC-xpath-19991116 (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2007/REC-soap12-part1-20070427/ (追記ここまで)
(削除) XPath Filter-2 (削除ここまで)
(追記) [UTF-16] (追記ここまで)
(追記) P. Hoffman , F. Yergeau. (追記ここまで)(追記) UTF-16, an encoding of ISO 10646. (追記ここまで) (追記) IETF RFC 2781. February 2000. URL: (追記ここまで)(追記) http://www.ietf.org/rfc/rfc2781.txt (追記ここまで)
(追記) [XHTML10] (追記ここまで)
(追記) Steven Pemberton. (追記ここまで)(追記) XHTMLTM 1.0 The Extensible HyperText Markup Language (Second Edition) (追記ここまで) (削除) XML-Signature XPath Filter 2.0 (削除ここまで) . (追記) 1 August 2002. (追記ここまで) W3C Recommendation. (削除) J. Boyer, M. Hughes, J. Reagle. November 2002. http://www.w3.org/TR/2002/REC-xmldsig-filter2-20021108/ (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2002/REC-xhtml1-20020801/ (追記ここまで)
(削除) XPTR-2001 (削除ここまで)
(追記) [XML-Japanese] (追記ここまで)
(追記) M. Murata. (追記ここまで) XML (削除) Pointer Language (XPointer) (削除ここまで) (追記) Japanese Profile (2nd Edition) (追記ここまで) . (追記) March 2005. (追記ここまで) W3C (削除) Candidate Recommendation. S. DeRose, R. Daniel, E. Maler. January 2001. http://www.w3.org/TR/2001/CR-xptr-20010911/ (削除ここまで) (追記) Member Submission. URL: (追記ここまで)(追記) http://www.w3.org/Submission/2005/SUBM-japanese-xml-20050324/ (追記ここまで)
(削除) XPointer-Element (削除ここまで)
(追記) [XMLDSIG-BESTPRACTICES] (追記ここまで)
(追記) Pratik Datta; Frederick Hirsch. (追記ここまで)(追記) XML Signature Best Practices (追記ここまで) (削除) XPointer element() Scheme (削除ここまで) . (追記) 11 April 2013. (追記ここまで) W3C (削除) Recommendation. P. Grosso, E. Maler, J. Marsh, N. Walsh. March 2003. http://www.w3.org/TR/2003/REC-xptr-element-20030325/ (削除ここまで) (追記) Working Group Note. URL: (追記ここまで)(追記) http://www.w3.org/TR/2013/NOTE-xmldsig-bestpractices-20130411/ (追記ここまで)
(削除) XPointer-Framework (削除ここまで)
(追記) [XMLDSIG-CORE] (追記ここまで)
(追記) Joseph Reagle et al. (追記ここまで)(追記) XML Signature Syntax and Processing (Second Edition) (追記ここまで) (削除) XPointer Framework (削除ここまで) . (追記) 10 June 2008. (追記ここまで) W3C Recommendation. (削除) P. Grosso, E. Maler, J. Marsh, N. Walsh. March 2003. (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2008/REC-xmldsig-core-20080610/ (追記ここまで)
(削除) http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ (削除ここまで)
(追記) [XMLDSIG-CORE1-CHGS] (追記ここまで)
(追記) Frederick Hirsch. (追記ここまで) (削除) XPointer-xpointer (削除ここまで) (追記) Functional Explanation of Changes in XML Signature 1.1 (追記ここまで).(追記) 11 April 2013. W3C Working Group Note. URL: (追記ここまで)(追記) http://www.w3.org/TR/2013/NOTE-xmldsig-core1-explain-20130411/ (追記ここまで)
(追記) [XMLDSIG-REQUIREMENTS] (追記ここまで)
(追記) Joseph Reagle Jr. (追記ここまで)(追記) XML-Signature Requirements (追記ここまで) (削除) XPointer xpointer() Scheme (削除ここまで) . (追記) 14 October 1999. (追記ここまで) W3C Working Draft. (削除) S. DeRose, E. Maler, R. Daniel. December 2002. (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/1999/WD-xmldsig-requirements-19991014 (追記ここまで)
(追記) [XMLSEC-RELAXNG] (追記ここまで)
(追記) Makoto Murata; Frederick Hirsch. (追記ここまで) (削除) http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219/ (削除ここまで) (追記) XML Security RELAX NG Schemas (追記ここまで) . (追記) 11 April 2013. W3C Working Group Note. URL: (追記ここまで)(追記) http://www.w3.org/TR/2013/NOTE-xmlsec-rngschema-20130411/ (追記ここまで)
(削除) XPointer-xmlns (削除ここまで)
(追記) [XMLSEC11-REQS] (追記ここまで)
(追記) Frederick Hirsch; Thomas Roessler. (追記ここまで)(追記) XML Security 1.1 Requirements and Design Considerations (追記ここまで).(追記) 11 April 2013. W3C Working Group Note. URL: (追記ここまで)(追記) http://www.w3.org/TR/2013/NOTE-xmlsec-reqs-20130411/ (追記ここまで)
(追記) [XPTR-XMLNS] (追記ここまで)
(追記) Jonathan Marsh et al. (追記ここまで) XPointer xmlns() Scheme . (削除) W3C Working Recommendation. S. DeRose, R. Daniel, E. Maler, J. Marsh. (削除ここまで) (追記) 25 (追記ここまで) March 2003. (追記) W3C Recommendation. URL: (追記ここまで) http://www.w3.org/TR/2003/REC-xptr-xmlns-20030325/
(削除) http://www.w3.org/TR/2001/REC-xsl-20011015/ (削除ここまで)
(追記) [XPTR-XPOINTER] (追記ここまで)
(追記) Ron Daniel Jr; Eve Maler; Steven DeRose. (追記ここまで) (削除) XSLT (削除ここまで) (追記) XPointer xpointer() Scheme (追記ここまで).(追記) 19 December 2002. W3C Working Draft. URL: (追記ここまで)(追記) http://www.w3.org/TR/2002/WD-xptr-xpointer-20021219/ (追記ここまで)
(追記) [XPTR-XPOINTER-CR2001] (追記ここまで)
(追記) Ron Daniel Jr; Eve Maler; Steven DeRose. (追記ここまで)(追記) XPointer xpointer() Scheme (追記ここまで) (削除) XSL Transforms (XSLT) Version 1.0 (削除ここまで) . (追記) September 2001. (追記ここまで) W3C (追記) Candidate (追記ここまで) Recommendation. (削除) J. Clark. November 1999. http://www.w3.org/TR/1999/REC-xslt-19991116.html (削除ここまで) (追記) URL: (追記ここまで)(追記) http://www.w3.org/TR/2001/CR-xptr-20010911/ (追記ここまで)
(削除) 12. Authors' Address Donald E. Eastlake 3rd Motorola Laboratories 111 Locke Drive Marlborough, MA 01752 USA Phone: +1-508-786-7554 Email: d3e3e3@gmail.com (削除ここまで) (削除) Joseph M. Reagle Jr. Department of Media, Culture, and Communication New York University Email: reagle@mit.edu (削除ここまで)
(削除) David Solo Citigroup 909 Third Ave, 16th Floor NY, NY 10043 USA Phone +1-212-559-2900 Email: dsolo@alum.mit.edu (削除ここまで)

AltStyle によって変換されたページ (->オリジナル) /