This document provides a summary of non-editorial changes in XML Signature 1.1 from the XML Signature Second Edition Recommendation.
Status of This DocumentThis 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/.
In the case of any difference between this document and the XML Signature 1.1 specification [XMLDSIG-CORE1], the XML Signature 1.1 specification is authoritative.
This Note has been updated since the previous publication to remove the text stating that OCSPResponse
was added to XML Signature 1.1, as it has been removed from XML Signature 1.1. References have also been updated (diff).
This document was published by the XML Security Working Group as a Working Group Note. If you wish to make comments regarding this document, please send them to public-xmlsec@w3.org (subscribe, archives). All comments are welcome.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. 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.
Table of Contents 1. IntroductionThis document summarizes non-editorial changes in XML Signature 1.1 from the XML Signature Second Edition Recommendation.
2. Changes 2.1 Algorithms AddedECDSA-SHA1
(OPTIONAL), ECDSA-SHA256
(REQUIRED), ECDSA-SHA384
(OPTIONAL), and ECDSA-SHA512
(OPTIONAL)SHA224
(OPTIONAL), SHA256
(REQUIRED), SHA384
(OPTIONAL), SHA512
(OPTIONAL)RSAwithSHA256
(REQUIRED), RSAwithSHA384
(OPTIONAL),RSAwithSHA512
(OPTIONAL)For all algorithms added, algorithm identifiers and information were added to the specification.
2.2 Algorithms ChangedSHA-1
but allow it for compatibility
SHA-1
use is DISCOURAGED (but support is still REQUIRED).SHA-1
to state that use is DISCOURAGED (but still REQUIRED).HMAC-SHA1
to state that use is DISCOURAGEDDSAwithSHA1
is only REQUIRED as Signature algorithm for Signature verification, but is OPTIONAL for Signature generation. Previously it was REQUIRED for both.RSA-SHA1
and ECDSA-SHA1
is DISCOURAGED.SHA-1
HMAC-SHA256
to REQUIREDHMAC-SHA384
, HMAC-SHA512
to RECOMMENDED (from OPTIONAL).HMACOutputLength
parameter in SignatureMethod
KeyInfo
Changes 2.4.1 General Changes
ECKeyValue
, ECParameters
DEREncodedKeyValue
KeyInfo
child elements
EncryptedKey
and DerivedKey
ElementsDEREncodedKeyValue
- new representation for public keysKeyInfoReference
- alternative to RetrievalMethod
access to a KeyInfo
element that does not require use of a Transform
RetrievalMethod
that a Transform
is needed to obtain content of KeyInfo
referenced by ID
KeyInfoReference
element instead of RetrievalMethod
X509Data
Changes
dsig11:X509Digest
to list of elements that may be included, to support reference via base64-encoded digest of a certificateX509IssuerSerial
and possible issue with schema validation when large serial numbers are used.X509Data
in explicitly trusted scenarios.Reference
validation since changes could occur in serialization after Signature
generation.SHA-256
in preference to SHA-1
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4