hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
6.3 Testing signature-policy-store
|
This clause defines the test assertion for signature-policy-identifier attribute presence in CMS signature. The CAdES_BB/SPS/1 check in ETSI TS 119 124-4 [3] shall apply. 7 Testing conformance to CAdES-E-T extended signatures
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
7.1 Introduction
|
The present clause specifies the set of assertions to be tested on signatures claiming conformance to the CAdES-E-T signatures level as specified by ETSI EN 319 122-2 [2]. CAdES-E-T signatures are built on CAdES-E-BES signatures. In consequence, CAdES-E-T signatures shall fulfill the requirements specified in clause 5 of the present document and all the requirements defined in clause 7.2.
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
7.2 Testing SignatureTimeStamp
|
This clause defines the test assertion for SignatureTimeStamp attribute presence in CMS signature. The CAdES_BB/STS/1 check in ETSI TS 119 124-4 [3] shall apply. ETSI ETSI TS 119 124-5 V1.1.1 (2016-06) 11 8 Testing conformance to CAdES-E-A extended signatures
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
8.1 Introduction
|
The present clause specifies the set of assertions to be tested on signatures claiming conformance to the CAdES-E-A signatures level as specified by ETSI EN 319 122-2 [2]. CAdES-E-A signatures are built on CAdES-E-T signatures. In consequence, CAdES-E-A signatures shall fulfill the requirements specified in clause 5 and 7 of the present document and all the requirements defined in the clauses 8.2 to 8.5.
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
8.2 Testing ArchiveTimeStampV3
|
This clause defines the test assertion for archive-time-stamp-v3 attribute presence in CAdES signature. The CAdES_BB/ATSV3/1 and CAdES_BB/ATSHI/1 checks in ETSI TS 119 124-4 [3] shall apply.
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
8.3 Testing Certificate and Revocation references
|
This clause defines the test assertion for certificate, attribute and revocation references attributes presence in CAdES signature. TA id: CAdES_ES/CCR/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures format as specified in [2] Predicate: For new signatures, applications include complete-certificate-references attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. TA id: CAdES_ES/CRR/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures format as specified in [2] Predicate: For new signatures, applications include complete-revocation-references attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. TA id: CAdES_ES/ACR/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures format as specified in [2] Predicate: For new signatures, applications include attribute-certificate-references attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. TA id: CAdES_ES/ARR/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures format as specified in [2] Predicate: For new signatures, applications include attribute-revocation-references attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. ETSI ETSI TS 119 124-5 V1.1.1 (2016-06) 12
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
8.4 Testing Certificate and Revocation values
|
This clause defines the test assertion for certificate and revocation values attributes presence in CAdES signature. TA id: CAdES_ES/CER/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES-E-A signatures format as specified in [2] Predicate: For new signatures, applications include the full set of certificates, including the trust anchors when they are available in the form of certificates, that have been used to validate the CAdES signature. Prescription level: mandatory Tag: CAdES-E-A signatures. TA id: CAdES_ES/REV/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES-E-A signatures format as specified in [2] Predicate: For new signatures, applications include the full set of revocation data (CRL or OCSP responses) that have been used to validate the CAdES signature. Prescription level: mandatory Tag: CAdES-E-A signatures. TA id: CAdES_ES/CV/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES-E-A signatures format as specified in [2] Predicate: For new signatures, applications include certificate-values attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. TA id: CAdES_ES/RV/1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES-E-A signatures format as specified in [2] Predicate: For new signatures, applications include revocation-values attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. TA id: CAdES_ES/CV/2 Normative source: [3] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures as specified in [2] Predicate: For new signatures, applications avoid duplication of certificate values in the certificate-values attribute in CAdES signature. Prescription level: recommended Tag: Extended CAdES signatures. TA id: CAdES_ES/RV/2 Normative source: [3] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures as specified in [2] Predicate: For new signatures, applications avoid duplication of revocation values in the revocation-values attribute in CAdES signature. Prescription level: recommended Tag: Extended CAdES signatures.
|
77fca53da8facd3195154cd5f20630ff
|
119 124-5
|
8.5 Testing time-stamp attributes
|
This clause defines the test assertion for time-stamp attributes presence in CAdES signature. TA id: CAdES_ES/ESCTS-1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures as specified in [2] Predicate: For new signatures, applications include CAdES-C-time-stamp attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. TA id: CAdES_ES/TSCCR-1 Normative source: [2] - Clause 4.3 Target: CAdES signature generator claiming conformance to CAdES signatures as specified in [2] Predicate: For new signatures, applications include time-stamped-certs-crls-references attribute in CAdES signature. Prescription level: permitted Tag: Extended CAdES signatures. The CAdES_BB/ATS/1, CAdES_BB/ATSV2/1, CAdES_BB/LTV/1 checks in ETSI TS 119 124-4 [3] shall apply. ETSI ETSI TS 119 124-5 V1.1.1 (2016-06) 13 History Document history V1.1.1 June 2016 Publication
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
1 Scope
|
The present document defines two approaches for issuing qualified certificates for website authentication, deploying them to websites, and their consumption by web browsers. Objectives of Approach #1 (i.e. "1-QWAC Approach") 1-QWACs: a) Support coexistence of trust controls based upon meeting requirements from both the Web Browser Vendor within the meaning of Recital 65 of the Regulation (EU) 2024/1183 [i.3] and EU Trusted Lists with ETSI standards aimed at supporting EU trust controls. b) Include requirements for TLS certificates based on CA/Browser Forum Requirements [i.4] and [i.5] as applied in ETSI standards [4]. c) Authenticate the website directly by using the QWAC to establish a TLS connection between the web browser and the server. NOTE: TLS uses encryption to secure data transmitted over a network providing confidentiality, integrity, and authentication. Objectives of Approach #2 (i.e. "2-QWAC with Certificate Binding Validation Approach") 2-QWACs with Certificate Binding Validation: - Support trust controls based upon EU Trusted Lists with ETSI standards aimed at supporting EU trust controls for a QWAC, which is used to bind the identity in the QWAC to the TLS certificate(s) to be used by the web browser to establish a TLS connection between the web browser and the server. - Support trust controls based upon Web Browser Vendor Root Stores for the TLS certificate which is used to establish a TLS connection between the web browser and the server. All approaches: • aim to meet the requirements of Article 45, Article 45a, and Recital 65 of Regulation (EU) 2024/1183 [i.3]; • include requirements of qualified certificates for website authentication as specified in Regulation (EU) 2024/1183 [i.3]; and • enable the display of identity data contained in qualified certificates for website authentication and validated by the EU trust schemes in a user-friendly manner. Clause 4 specifies Trust Service Provider requirements for issuing QWACs. Clause 5 provides website operator guidance for using QWACs. Clause 6 specifies web browser requirements for consuming QWACs.
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
2 References
| |
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non- specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 7 The following referenced documents are necessary for the application of the present document. [1] ETSI TS 119 615: "Electronic Signatures and Infrastructures (ESI); Trusted lists; Procedures for using and interpreting European Union Member States national trusted lists". [2] ETSI EN 319 102-1: "Electronic Signatures and Trust Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [3] ETSI EN 319 411-2: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 2: Requirements for trust service providers issuing EU qualified certificates". [4] ETSI EN 319 412-4: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 4: Certificate profile for web site certificates". [5] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". [6] IETF RFC 8288: "Web Linking". [7] ETSI TS 119 182-1: "Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures". [8] ETSI TS 119 312: "Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites". [9] IETF RFC 7519: "JSON Web Token (JWT)". [10] IETF RFC 7515: "JSON Web Signature (JWS)". [11] Recommendation ITU-T X.680 (2008): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non- specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [i.2] ETSI EN 319 411-1: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 1: General requirements". [i.3] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. [i.4] CA/Browser Forum: "Guidelines for The Issuance and Management of Extended Validation Certificates". [i.5] CA/Browser Forum: "Baseline Requirements Certificate Policy for the Issuance and Management of Publicly-Trusted Certificates". [i.6] ETSI EN 301 549: "Accessibility requirements suitable for public procurement of ICT products and services in Europe". [i.7] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transaction. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 8 [i.8] IETF RFC 7518: "JSON Web Algorithms (JWA)". [i.9] Commission Implementing Decision (EU) 2015/1505 of 8 September 2015 laying down technical specifications and formats relating to trusted lists pursuant to Article 22(5) of Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market (Text with EEA relevance).
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
3 Definition of terms, symbols and abbreviations
| |
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI EN 319 401 [i.1], ETSI EN 319 411-1 [i.2], ETSI EN 319 411-2 [3] and the following apply: 1-QWAC: qualified certificate for website authentication based on Approach #1 in clause 1 of the present document 2-QWAC: qualified certificate for website authentication based on Approach #2 in clause 1 of the present document Transport Layer Security: protocol standardized by the IETF RFC 8446 [5] which is used by web browsers to establish encrypted connections to websites Transport Layer Security Certificate: X.509 public key certificate with an extended key usage extension that contains the id-kp-serverAuth KeyPurposeId, used to authenticate a website in accordance with a transport layer security protocol web browser: software application that acts on behalf of a user to retrieve, render, and interact with websites web browser vendor: legal entity who provides a web browser web browser vendor root store: set of transport layer security root certificates that transport layer security certificates have to chain up to in order to be trusted by the web browser web browser vendor root store policy: policy defining the individual rules on the issuers of the transport layer security root certificates in the root store by the web browser vendor
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
3.2 Symbols
|
Void.
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI EN 319 401 [i.1], ETSI EN 319 411-1 [i.2], ETSI EN 319 411-2 [3] and the following apply: HTTP Hypertext Transfer Protocol TLS Transport Layer Security QTSP Qualified Trust Service Provider QWAC Qualified Website Authentication Certificate NOTE: QWAC is termed qualified certificate for website authentication in Regulation (EU) 2024/1183 [i.3]. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 9 4 Trust Service Provider Requirements for issuing Qualified Certificates for Website Authentication
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
4.1 1-QWAC Approach
| |
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
4.1.1 Policy Requirements
|
The 1-QWAC certificate shall be issued in accordance with one of the following certificate policies as specified in ETSI EN 319 411-2 [3]: a) QEVCP-w; or b) QNCP-w.
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
4.1.2 Certificate Profile Requirements
|
The 1-QWAC certificate shall be issued in accordance with ETSI EN 319 412-4 [4] for the relevant certificate policy as identified in clause 4.1.1 of the present document.
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
4.2 2-QWAC Approach
| |
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
4.2.1 Policy Requirements
|
The 2-QWAC certificate shall be issued in accordance with the QNCP-w-gen certificate policy as specified in ETSI EN 319 411-2 [3].
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
4.2.2 Certificate Profile Requirements
|
The 2-QWAC certificate shall be issued in accordance with ETSI EN 319 412-4 [4] for the relevant certificate policy as identified in clause 4.2.1 of the present document, except as described below: • the extKeyUsage value shall only assert the extendedKeyUsage purpose of id-kp-tls-binding as specified in Annex A. 5 Website Operator Guidance for using Qualified Certificates for Website Authentication
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
5.1 Usage of 1-QWACs
|
The website operator requests a 1-QWAC from a QTSP as defined in clause 4.1 of the present document and configures its use (e.g. provisions the 1-QWAC on a TLS terminator).
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
5.2 Usage of 2-QWACs
|
The website operator requests: • a Qualified Website Authentication Certificate (i.e. 2-QWAC) from a QTSP; and • a TLS certificate from a TLS Certificate issuer (e.g. TSP or Certification Authority) whose corresponding root CA certificate is included in the desired Web Browser Vendor Root Store(s). ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 10 When using a 2-QWAC, website operators shall: 1) Enumerate the TLS certificate(s) they wish relying parties to use to establish secure connections with their website; 2) Produce a TLS Certificate Binding over their selected TLS certificate(s) with their 2-QWAC as described in Annex B and place it on their website; and 3) Configure their website to serve: a) an HTTP 'Link' response header (as defined in IETF RFC 8288 [6]) with a relative reference to the TLS Certificate Binding, and a rel value of tls-certificate-binding; and b) the TLS certificate(s). Website operators should deploy the appropriate HTTP caching directives for their TLS Certificate Binding file. The cache lifetime should not extend beyond the lifetime of the TLS Certificate Binding, in order to ensure consistent behaviour for relying parties, but there are no security implications if the caching directives are incorrectly set. Website operators may choose to rely upon a unique binding filename or location to reduce the potential of cache errors. Periodically, website operators will receive new QWACs and TLS certificates. When the operator wishes to roll over from an existing QWAC to a new QWAC, it produces a fresh TLS Certificate Binding and deploys it using the ordinary mechanism. Website operators should also remove no-longer-used TLS certificates from the TLS Certificate Binding to optimize certificate validation. 6 Web Browser Requirements for consuming Qualified Certificates for Website Authentication
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.1 General Procedures
| |
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.1.1 Determining Usage
|
If a certificate is received as part of the TLS Handshake protocol which has QCStatements indicating that it is a QWAC, it shall be processed under procedures for 1-QWAC. If a certificate is received as part of the TLS Certificate Binding which has QCStatements indicating that it is a QWAC, it shall be processed under procedures for 2-QWAC.
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.1.2 Validation of QWACs
|
For 1-QWACs and 2-QWACs, validation shall include: 1) that the QWAC includes QCStatements as specified in clause 4.2 of ETSI EN 319 412-4 [4] and the appropriate Policy OID specified in ETSI EN 319 411-2 [3]; 2) that the QWAC chains back through appropriate & valid digital signatures to an issuer on the EU Trusted List which is authorized to issue Qualified Certificates for Website Authentication as specified in ETSI TS 119 615 [1]; 3) that the QWAC's validity period covers the current date and time; 4) that the website domain name in question appears in the QWAC's subject alternative name(s); and 5) that the QWAC's certificate profile conforms with: a) For a 1-QWAC, clause 4.1.2 of the present document; or b) For a 2-QWAC, clause 4.2.2 of the present document. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 11 The web browser may also perform further checks on the security and authenticity of the QWAC as appropriate (e.g. for checking revocation status).
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.2 Usage of QWACs
| |
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.2.1 Usage of 1-QWACs (i.e. "Approach #1")
|
When using 1-QWACs for the establishment of secure TLS connections with websites authenticated with identity information, web browsers shall: 1) Establish a secure TLS connection with the site using the web browsers' procedures and configuration, and evaluate the presented TLS Certificate with the security requirements of the web browser vendor and their policies for web security, domain authentication and the encryption of web traffic as outlined in Recital 65 of the Regulation (EU) 2024/1183 [i.3]. - If this step fails, the procedure finishes negatively. 2) Evaluate the presented TLS certificate with the validation criteria laid out in clause 6.1.2 of the present document to establish if it is considered a 1-QWAC. - If this step fails for any reason, the procedure finishes negatively. 3) Display the outcome as specified in clause 6.3 of the present document.
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.2.2 Usage of 2-QWACs with TLS Certificate Binding (i.e. "Approach #2")
|
When using 2-QWACs with secure TLS connections to websites, web browsers shall: 1) Establish a secure TLS connection with the site using the web browsers' procedures and configuration, and evaluate the presented TLS Certificate with the security requirements of the web browser vendor and their policies for web security, domain authentication and the encryption of web traffic as outlined in Recital 65 of the Regulation (EU) 2024/1183 [i.3]. - If this step fails, the procedure finishes negatively. 2) Examine the HTTP headers included in any main frame navigation response from the server (relating to navigation by the web browser to the address as displayed in the address bar) for a HTTP 'Link' response header (as defined in IETF RFC 8288 [6]) with a rel value of tls-certificate-binding. - If this step is absent, the procedure finishes negatively. 3) Fetch the resource located at this link and evaluate it for conformance with the profile laid out in Annex B. - If this step fails or the resource is non-conformant, the procedure finishes negatively. 4) Examine the QWAC presented in the binding with the validation criteria laid out in clause 6.1.2 of the present document. - If this step fails or the certificate is not considered a '2-QWAC' under clause 6.1.2 of the present document, the procedure finishes negatively. 5) Validate the JAdES signature on the TLS Certificate binding according to ETSI EN 319 102-1 [2]. - If this step fails or the TLS Certificate binding is not considered valid, the procedure finishes negatively. 6) Validate that the TLS Certificate used to establish this connection in Step 1 appears in the list contained in the validated binding. - If this step fails or the list does not contain the certificate, the procedure finishes negatively. 7) Display the outcome as specified in clause 6.3 of the present document. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 12
|
ef5ff2d4601859bfd6c42ad669e69bc0
|
119 411-5
|
6.3 Validation outcomes
|
Regardless of how the QWAC was delivered (i.e. as a 1-QWAC or 2-QWAC), if the applicable procedure described in clause 6.2 of the present document finishes: • successfully (with a valid QWAC), the web browser: - shall indicate that the QWAC is validated as being qualified as specified in Regulation (EU) 2024/1183 [i.3] using the EU Trust Mark if technically feasible. When using the EU Trust Mark the web browser may provide a link to the relevant Trusted List entry. - shall display the identity data contained in qualified certificates for website authentication to the web browser user in a user-friendly manner. The web browser should take the accessibility requirements defined in ETSI EN 301 549 [i.6] into account. • negatively (without a valid QWAC), the web browser: - may use its discretion in presenting the website to the user, with or without warnings or bypassable errors, however it shall not display a "EU Qualified Status" indicator (e.g. EU Trust Mark). - may include a warning that a QWAC failed to validate. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 13 Annex A (normative): id-kp-tlsBinding EKU specification The following ASN.1 module shall be interpreted using the syntax defined in Recommendation ITU-T X.680 [11]. It defines the KeyPurposeID id-kp-tls-binding. TLSBindingMod { itu-t(0) identified-organization(4) etsi(0) id-qwacImplementation(194115) id-mod(0) id-mod-tlsbinding(1) v1(0) } DEFINITIONS EXPLICIT TAGS ::= BEGIN -- EXPORTS ALL -- IMPORTS NOTHING -- Object Identifier arc for extended Key Usage purpose id-kp-tls-binding id-tlsBinding OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) id-qwacImplementation(194115) tls-binding (1) } id-kp-tls-binding OBJECT IDENTIFIER ::= { id-tlsBinding id-kp-tls-binding(0) } END ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 14 Annex B (normative): TLS Certificate Binding Profile A website operator can use a public key certificate to produce a binding to one or multiple TLS certificates as specified in this annex. This binding is produced by generating a JAdES signature over the fields described below using the certificate private key corresponding to the QWAC and according to ETSI TS 119 182-1 [7]. Only header parameters specified in this profile may be present in the header of the generated JAdES signature. The JAdES signatures shall be serialized using JWS Compact Serialization as specified in IETF RFC 7515 [10]. Table B.1: Signed header parameters Header Parameter Description alg Specifies the cryptographic algorithm used for signing the binding. This field shall not conflict with the type of public key in the signing certificate. kid Identifies the key used for signing the binding. cty This field identifies the purpose of the JAdES signature and ensures context separation. It shall be "TLS-Certificate-Binding-v1". x5t#S256 The SHA-256 hash of the DER encoding of the X.509 certificate that corresponds with the private key used for signing the binding. x5c The signing certificate and Certificate Chain (Base64 encoded). The Chain shall be ordered as described in IETF RFC 7515 [10] and shall finish in a trust anchor on the EU Trusted List which is authorized to issue QWACs (ETSI TS 119 615 [1]). iat This field contains the claimed signing time. The value shall be encoded as specified in IETF RFC 7519 [9]. exp This field contains the expiry date of the binding. The maximum effective expiry time is whichever is soonest of this field, the longest-lived TLS certificate identified in the sigD member payload (below), or the notAfter time of the signing certificate. The value shall be encoded as specified in IETF RFC 7519 [9]. sigD Includes a data object following the format below: { "mId": "http://uri.etsi.org/19182/ObjectIdByURIHash", "pars": [A comma-separated list of TLS certificate file names.], "hashM": [The string identifying one of the approved hashing algorithms identified by ETSI TS 119 312 [8] for JAdES. This hashing algorithm is used to calculate the hashes described in the "hashV" member below.], "hashV": [A comma-separated list of TLS certificate file hashes. Each hash is produced by taking the corresponding X.509 certificate, computing its base64url encoding, and calculating its hash using the algorithm identified in the "hashM" member above.] } NOTE: At the time of publication of the present document, in line with the hash algorithms required as part of the digital signature algorithms in IETF RFC 7518 [i.8] and the requirements for AdES formats listed in the latest version of ETSI TS 119 312 [8] V1.5.1, Annex A, it is required that SHA-256, SHA-384, and SHA-512 are supported, and it is assumed that strings identifying them are S256, S384, and S512 respectively. Signature: Produced by the signing certificate private key over the fields above, according to ETSI TS 119 182-1 [7]. Future versions of the present document may use a different format or hash function and will be distinguished by a different type in the cty field. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 15 Annex C (informative): Web Browser Recommendations C.1 General Web Browser Recommendations a) Web browsers should support both 1-QWAC and 2-QWAC as defined in the present document. b) Web browser vendors should make available to issuers of 1-QWACs any requirements in addition to those required under clause 4.1 of the present document (TSP policy and certificate profile requirements). c) When adding requirements relevant to issuers of 1-QWACs, as in b) above, Web browser vendors should substantiate the positive impact of those additions to user security and privacy. C.2 Basic Recommendations on Web Browser Vendor Root Store Policies for TLS certificates When a web browser vendor runs a web browser vendor root store for TLS certificates, it should publish and maintain a web browser vendor root store policy which defines the rules that apply to the root store. If instead, a web browser vendor relies on either the operating system's root store or a root store run by an upstream web browser vendor, it should publicly disclose the location of the corresponding root store policy. The following conditions define the basic requirements on web browser vendor root store policies for TLS certificates so that the web browser vendor and its root store are in compliance with the present document. Additional requirements of the root store policy should not weaken the CA/Browser Forum Requirements [i.5] or reduce its effect. C.3 Content of the Root Store Policy When a web browser vendor runs a web browser vendor root store for TLS certificates, its web browser vendor root store policy should contain at least the following content: 1) Scope of the root store policy 2) Contact address and means of contact 3) Revisions 4) A non-exhaustive list of requirements to be included in the root store 5) A non-exhaustive list of requirements to remain in the root store 6) A non-exhaustive list of requirements to be excluded from the root store 7) Description of the application process to be added to the root store and its processing time 8) Description of the removal process from the root store and its processing time 9) Description of the updating process of the root store policy and ways of participation The web browser vendor may publish interpretation guidelines and examples that support a better understanding of its root store policy. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 16 C.4 Application of a Root Store Policy When there is a root store policy that complies with the present document, the TLS certificate issuer should fully comply with that root store policy. Web browser vendors should respond to general inquiries or questions from TSPs related to their stated policies within 14 calendar days. ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 17 Annex D (informative): Change history Date Version Information about changes June 2024 v1.1.2 Initial draft September 2024 v1.1.3 Update after call on July 11 October 2024 v1.1.4 Update after call on October 22 November 20224 v1.1.5 Update after ESI#84 November 2024 v1.1.6 Update for RC December 2024 v1.1.7 Update after comments on RC January 2025 v1.1.8 Update after comments from public review February 2025 v1.1.9 Update after comments on v1.1.8 ETSI ETSI TS 119 411-5 V2.1.1 (2025-02) 18 History Document history V1.1.1 January 2023 Publication as ETSI TR 119 411-5 V2.1.1 February 2025 Publication
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
1 Scope
|
The present document defines the set of checks to be performed for testing conformance of PAdES signatures against additional PAdES signatures profiles as specified in ETSI EN 319 142-2 [3]. It defines only the checks that are specific to additional PAdES signatures. The set of checks that are common to both additional and baseline PAdES signatures, are defined in ETSI TS 119 144-4 [6]. The complete set of checks to be performed by any tool on additional PAdES signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 142-1 [1] and ETSI EN 319 142-2 [3] defined in ETSI TS 119 144-4 [6], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by PAdES [1]. Regarding PAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for additional PAdES signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by PAdES [1].
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
2 References
| |
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [2] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [3] ETSI EN 319 142-2: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 2: Additional PAdES signatures profiles". [4] ETSI TS 119 134-4: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of XAdES baseline signatures". [5] IETF RFC 2315: "PKCS #7: Cryptographic Message Syntax Version 1.5". [6] ETSI TS 119 144-4: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance against building blocks and PAdES baseline signatures". ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 6
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 119 144-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview". [i.2] OASIS Committee Notes: "Test Assertions Guidelines Version 1.0" Committee Note 02, 19 June 2013. [i.3] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations".
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
3 Definitions and abbreviations
| |
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.3] apply.
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.3] apply.
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
4 Overview
|
The present clause describes the main aspects of the technical approach used for specifying the set of checks to be performed for testing conformance to ETSI EN 319 142-2 [3]. ETSI EN 319 142-1 [1] defines requirements for building blocks and PAdES baseline signatures. For the purpose of identifying the whole set of test assertions required for testing conformance against additional PAdES signatures as specified in ETSI EN 319 142-2 [3], the present document classifies the whole set of requirements specified in ETSI EN 319 142-1 [1] and in ETSI EN 319 142-2 [3] in two groups as follows: 1) Requirements "PAdES_BB" (after "PAdES building blocks"): requirements defined in clause 4, clause 5, clause 6 of ETSI EN 319 142-1 [1] to be satisfied by both PAdES baseline signatures as specified in ETSI EN 319 142-1 [1] and additional PAdES signatures as specified in ETSI EN 319 142-2 [3]. The checks for these requirements are defined in ETSI TS 119 144-4 [6]. When needed in the present document, such checks are referred by their TA_id. 2) Requirements "PAdES_AS" (after "Additional PAdES signatures"): requirements defined in clauses 4, 5 and 6 of ETSI EN 319 142-2 [3]. These are requirements specific to Extended CAdES signatures. a) In order to test conformance to ETSI EN 319 142-2 [3], several types of tests are identified, namely: 1) Tests on the signature structure. 2) Tests on values of specific elements and/or attributes. 3) Tests on interrelationship between different elements present in the signature. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 7 4) Tests on computations reflected in the contents of the signatures (message imprints for a time-stamping service, computed by digesting the concatenation of a number of elements of the signature, for instance). b) No tests are included testing actual validity of the cryptographic material that might be present at the signature or to be used for its verification (status of certificates for instance). c) Tests are defined as test assertions following the work produced by OASIS in "Test Assertions Guidelines Version 1.0" [i.2]. Each test assertion includes: 1) Unique identifier for further referencing. The identifiers start with "PAdES_AS", after "Additional PAdES signature". 2) Reference to the Normative source for the test. 3) The Target of the assertion. In the normative part, this field identifies one of the format specified in Additional PAdES signatures specification [3]. 4) Prerequisite (optional) is, according to [i.2], "a logical expression (similar to a Predicate) which further qualifies the Target for undergoing the core test (expressed by the Predicate) that addresses the Normative Statement". It is used for building test assertions corresponding to requirements that are imposed under certain conditions. 5) Predicate fully and unambiguously defining the assertion to be tested. 6) Prescription level. Three levels are defined: mandatory, recommended and optional, whose semantics is to be interpreted as described in clause 3.1.2 of [i.2]. 7) Tag: information on the element tested by the assertion. The presentation of the checks is organized following the formats of Additional PAdES signatures specified in ETSI EN 319 142-2 [3]. The following signature formats is considered: • CMS Signatures in PDF. • PAdES-E-BES. • PAdES-E-EPES. • PAdES-E-LTV. • XAdES Signatures signing XML content in PDF. 5 Testing conformance to CMS signatures in PDF profile
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
5.1 Introduction
|
The present clause specifies the set of assertions to be tested on signatures claiming conformance to the CMS signatures in PDF profile as specified by clause 4 of ETSI EN 319 142-2 [3]. The next clauses specify the assertions for testing the elements that are profiled by clause 4 of ETSI EN 319 142-2 [3]. The constraints imposed by clause 4 of ETSI EN 319 142-2 [3] and PKCS #7 syntax [5] to the signature elements are tested. Clause 5.2 specifies the assertions for testing the elements that are profiled by clause 4 of ETSI EN 319 142-2 [3]. Clause 5.3 specifies the assertions for testing the properties that are specified by the PKCS #7 syntax [5]. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 8
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
5.2 Testing signature dictionary elements
|
This clause defines the test assertion for signature dictionary elements requirements. PAdES_BB/SDC/1 check as specified in ETSI TS 119 144-4 [6] shall apply. TA id: PAdES_AS/SDC/1 Normative source: [3] – Clause 4.2.1 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Prerequisites: PAdES_BB/DSC/1 Predicate: For new signatures, applications encode the signature, included in the signature dictionary entry with the key Contents, as a DER-encoded PKCS#7 binary data object. Prescription level: mandatory Tag: Additional PAdES signatures. PAdES_BB/SDBR/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDF/1 check as specified in ETSI TS 119 144-4 [6] shall apply. TA id: PAdES_AS/SDSF/1 Normative source: [3] – Clause 4.2.2 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include the string "adbe.pkcs7.detached" in the SubFilter entry of the signature dictionary. Prescription level: mandatory Tag: Additional PAdES signatures. TA id: PAdES_AS/SDSF/2 Normative source: [3] – Clause 4.2.2 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: While validating signatures, applications accept the string "adbe.pkcs7.detached" or "adbe.pkcs7.sha1" in the SubFilter entry of the signature dictionary. Prescription level: recommended Tag: Additional PAdES signatures. TA id: PAdES_AS/SDM/1 Normative source: [3] – Clause 4 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include the claimed time of signing in the M entry of the signature dictionary. Prescription level: permitted Tag: Additional PAdES signatures. PAdES_BB/SDL/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDR/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDCERT/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDCI/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDNAME/1 check as specified in ETSI TS 119 144-4 [6] shall apply.
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
5.3 Testing PKCS #7 signature elements
|
This clause defines the test assertions for the signature, included in the signature dictionary entry with the key Contents, requirements. Test assertions for SignedData.certificates attribute: PAdES_BB/CER/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for revocation data attribute: TA id: PAdES_AS/CRL/1 Normative source: [3] – Clause 4.2.1 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include all crls or ocsp responses needed for certificates validation in the signed attributes of the signature. Prescription level: recommended Tag: Additional PAdES signatures. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 9 Test assertion for timestamp signature attribute: TA id: PAdES_AS/TST/1 Normative source: [1] – Clause 4.2.1 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include a timestamp in the unsigned attributes of the signature. Prescription level: recommended Tag: Additional PAdES signatures. Test assertion for signing time attribute: TA id: PAdES_AS/STI/1 Normative source: [1] – Clause 4 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include a claimed signing time in the signed attributes of the signature. Prescription level: permitted Tag: Additional PAdES signatures. Test assertion for signer-location attribute: TA id: PAdES_AS/SL/1 Normative source: [1] – Clause 4 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include a signer-location in the signed attributes of the signature. Prescription level: permitted Tag: Additional PAdES signatures. 6 Testing conformance to PAdES-E-BES and PAdES-E-EPES additional signatures
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
6.1 Introduction
|
The present clause specifies the set of assertions to be tested on signatures claiming conformance to PAdES-E-BES and PAdES-E-EPES signatures level as specified by clause 5 of ETSI EN 319 142-2 [3]. The next clauses specify the assertions for testing whether the elements that are profiled by ETSI EN 319 142-2 [3], are actually conformant to these levels. The constraints imposed by the PAdES-E-BES and PAdES-E-EPES levels and CAdES specification [2] to the signature elements are tested. Clause 6.2 specifies the assertions for testing whether the elements that are profiled by PAdES-E-BES level in ETSI EN 319 142-2 [3], are actually conformant to this level. Clause 6.3 specifies the assertions for testing whether the elements that are profiled by PAdES-E-EPES level in ETSI EN 319 142-2 [3] are actually conformant to this level. 6.2 Testing PAdES-E-BES signature dictionary and CMS signature elements
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
6.2.1 Testing signature dictionary elements
|
This clause specifies assertions for testing those constraints imposed by the CAdES specification [2] and the PAdES-E-BES level [3] to the signature dictionary elements. PAdES_BB/SDC/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDBR/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDF/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDSF/1 check as specified in ETSI TS 119 144-4 [6] shall apply. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 10 PAdES_AS/SDM/1 check in clause 5.1 shall apply. PAdES_BB/SDL/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDR/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDCERT/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDCI/1 check as specified in ETSI TS 119 144-4 [6] shall apply. PAdES_BB/SDNAME/1 check as specified in ETSI TS 119 144-4 [6] shall apply.
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
6.2.2 Testing CMS signature elements
|
This clause specifies assertions for testing those constraints imposed by the CAdES specification [2] and the PAdES-E-BES level [3] to the CMS signature elements. Test assertions for SignedData.certificates attribute: • PAdES_BB/CER/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for timestamp signature attribute: • PAdES_AS/TST/1 in clause 5.2 shall apply. Test assertion for signing time attribute: • PAdES_AS/STI/1 in clause 5.2 shall apply. Test assertion for signer-location attribute: • PAdES_AS/SL/1 in clause 5.2 shall apply. Test assertions for ESS attribute: • PAdES_BB/ESS/1-2-3-4 checks as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for message-digest attribute presence in CMS signature: • PAdES_BB/MD/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertions for ContentType attribute in CMS signature: • PAdES_BB/CTY/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for counter-signature attribute presence in CMS signature: • PAdES_BB/CS/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for content-reference attribute presence in CMS signature: • PAdES_BB/CR/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for content-identifier attribute presence in CMS signature: • PAdES_BB/CI/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for content-hints attribute presence in CMS signature: • PAdES_BB/CH/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for commitment-type-indication attribute presence in CMS signature: • PAdES_BB/CTI/1 check as specified in ETSI TS 119 144-4 [6] shall apply. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 11 Test assertion for signer-location attribute presence in CMS signature: • PAdES_BB/SL/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for signer-attributes-v2 attribute presence in CMS signature: • PAdES_BB/SA/1 check as specified in ETSI TS 119 144-4 [6] shall apply. Test assertion for content-time-stamp attribute presence in CMS signature: • PAdES_BB/CTS/1 check as specified in ETSI TS 119 144-4 [6] shall apply. 6.3 Testing PAdES-E-EPES signature dictionary and CMS signature elements
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
6.3.1 Testing signature dictionary elements
|
This clause specifies assertions for testing those constraints imposed by the CAdES specification [2] and the PAdES-E-EPES level [3] to the signature dictionary elements. PAdES_BB/SDBR/1-2 checks as specified in ETSI TS 119 144-4 [6] shall apply.
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
6.3.2 Testing CMS signature elements
|
This clause specifies assertions for testing those constraints imposed by the CAdES specification [2] and the PAdES-E-EPES level [3] to the CMS signature elements. It defines the test assertion for signature-policy-identifier attribute presence in CMS signature. TA id: PAdES_AS/SPID/1 Normative source: [3] – Clause 5.4 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [3] Predicate: For new signatures, applications include signature-policy-identifier attribute in CMS signature. Prescription level: mandatory Tag: Additional PAdES signatures. 7 Testing conformance to PAdES-E-LTV additional signatures
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
7.1 General requirements
|
The present clause specifies the set of assertions to be tested on signatures claiming conformance to the PAdES-E-LTV signatures level as specified by clause 5 of ETSI EN 319 142-2 [3]. The next clauses specify the assertions for testing whether the elements that are profiled by ETSI EN 319 142-2 [3], are actually conformant to this level. The constraints imposed by the PAdES-E-LTV signatures level to the signature elements are tested. Clause 7.1 specifies the assertions for testing Document Security Store dictionary elements requirements. Clause 7.2 specifies the assertions for testing Document Time-Stamp dictionary elements requirements. PAdES signatures conformant to PAdES-E-LTV level as specified in ETSI EN 319 142-2 [3] are built on PAdES signatures already conformant to PAdES-E-BES or PAdES-E-EPES levels. In consequence, PAdES signatures conformant to PAdES-E-LTV level shall fulfil the requirements specified in clauses 5.1 or 5.2 of the present document and all the requirements defined in the clauses 7.2 and 7.3. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 12
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
7.2 Testing DSS dictionary
|
This clause defines the test assertion for Document Security Store dictionary elements requirements. PAdES_BB/DSS/1-2-3-4-5 checks as specified in ETSI TS 119 144-4 [6] shall apply.
|
15464d2cb35e56a6f04feba86a8fe760
|
119 144-5
|
7.3 Testing DTS dictionary
|
This clause defines the test assertion for Document Time-Stamp dictionary element requirements. PAdES_BB/DTS/2-3-4-5 checks as specified in ETSI TS 119 144-4 [6] shall apply. 8 Testing conformance to profiles for XAdES signatures signing XML content in PDF specification A PAdES signature conformant to the profiles for XAdES signatures signing XML content in PDF specified in ETSI EN 319 142-2 [3] is built on arbitrary XML document signed with XAdES signatures that is embedded within a PDF file. In consequence, PAdES signatures conformant to the above profiles specified in ETSI EN 319 142-2 [3] contain XAdES signatures that shall fulfil the requirements specified in clause 5 of ETSI TS 119 134-4 [4]. ETSI ETSI TS 119 144-5 V1.1.1 (2016-06) 13 History Document history V1.1.1 June 2016 Publication
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
1 Scope
|
The present document defines the set of checks to be performed for testing conformance of PAdES signatures against PAdES baseline signatures as specified in ETSI EN 319 142-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by PAdES [1]. Regarding PAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for PAdES baseline signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by PAdES [1].
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
2 References
| |
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [2] ETSI EN 319 142-2: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 2: Additional PAdES signatures profiles".
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 119 144-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview". [i.2] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 6 [i.3] OASIS Committee Notes: "Test Assertions Guidelines Version 1.0" Committee Note 02, 19 June 2013.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
3 Definitions and abbreviations
| |
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.2] apply.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] apply.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
4 Overview
|
The present clause describes the main aspects of the technical approach used for specifying the whole set of checks to be performed for testing conformance to ETSI EN 319 142-1 [1]. ETSI EN 319 142-1 [1] defines requirements for building blocks and PAdES baseline signatures. For the purpose of identifying the whole set of test assertions required for testing conformance against PAdES baseline signatures as specified in ETSI EN 319 142-1 [1], the present document classifies the whole set of requirements specified in ETSI EN 319 142-1 [1] in two groups as follows: 1) Requirements "PAdES_BS" (after "PAdES baseline signatures"): requirements defined in clauses 5 and 6 of ETSI EN 319 142-1 [1]. These are requirements specific to PAdES baseline signatures. 2) Requirements "PAdES_BB" (after "PAdES building blocks"): requirements defined in clauses 4 and 5 of ETSI EN 319 142-1 [1] and clauses 4 and 5 of ETSI EN 319 142-2 [2] to be satisfied by both PAdES baseline signatures as specified in ETSI EN 319 142-1 [1] and additional PAdES signatures as specified in ETSI EN 319 142-2 [2]. a) In order to test conformance against the aforementioned specification, several types of tests are identified, namely: 1) Tests on the signature structure. 2) Tests on values of specific elements and/or attributes. 3) Tests on interrelationship between different elements present in the signature. 4) Tests on computations reflected in the contents of the signatures (message imprints for a time-stamping service, computed by digesting the concatenation of a number of elements of the signature, for instance). b) No tests is included testing actual validity of the cryptographic material that might be present at the signature or to be used for its verification (status of certificates for instance). c) Tests are defined as test assertions following the work produced by OASIS in "Test Assertions Guidelines Version 1.0" [i.3]. Each test assertion includes: 1) Unique identifier for further referencing. The identifiers of the assertions start with "PAdES_BS", after "PAdES baseline signatures" and with "PAdES_BB", after "PAdES building blocks". 2) Reference to the Normative source for the test. 3) The Target of the assertion. In the normative part, this field identifies one of the four PAdES baseline signatures [1] Conformance Levels. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 7 4) Prerequisite (optional) is, according to [i.3], "a logical expression (similar to a Predicate) which further qualifies the Target for undergoing the core test (expressed by the Predicate) that addresses the Normative Statement". It is used for building test assertions corresponding to requirements that are imposed under certain conditions. 5) Predicate fully and unambiguously defining the assertion to be tested. 6) Prescription level. Three levels are defined: mandatory, recommended and permitted, whose semantics is to be interpreted as described in clause 3.1.2 of [i.3]. 7) Tag: information on the element tested by the assertion.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
5 Testing conformance to PAdES-B-B signatures
| |
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
5.1 Introduction
|
The present clause specifies the whole set of assertions to be tested on applications claiming conformance to PAdES-B-B signatures as specified in ETSI EN 319 142-1 [1]. Clause 5.2 specifies assertions for testing those constraints imposed by the PAdES building blocks and baseline signatures specification [1] to the signature dictionary elements. Clause 5.3 specifies assertions for testing those constraints imposed by the PAdES building blocks and baseline signatures specification [1] to the CMS signature included in the signature dictionary entry with the key Contents.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
5.2 Testing signature dictionary elements
|
This clause defines the test assertions for signature dictionary elements requirements. TA id: PAdES_BS/SDM/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] Predicate: For new signatures, applications include the claimed time of signing in the signature dictionary entry with the key M. Prescription level: mandatory Tag: PAdES baseline signatures. TA id: PAdES_BB/SDL/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the CPU host name or physical location of the signing in the signature dictionary entry with the key Location. Prescription level: permitted Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDR/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not include the reason for the signing in the signature dictionary entry with the key Reason if the signature-policy-identifier attribute is present in the CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDR/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not include the reason for the signing in the signature dictionary entry with the key Reason if the commitment-type-indication attribute is present in the CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 8 TA id: PAdES_BB/SDC/1 Normative source: [1] – Clause 4.1 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the CMS signature in the signature dictionary entry with the key Contents. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDCERT/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not set the signature dictionary entry with the key Cert. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDSF/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the value "ETSI.CAdES.detached" in the signature dictionary entry with the key SubFilter. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDF/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the preferred signature handler to use when validating the signature itself in the signature dictionary entry with the key Filter. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDBR/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include an array of pairs of integers that shall describe the exact byte range for the digest calculation in the signature dictionary entry with the key ByteRange. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDBR/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BS/SDBR/1 Predicate: For new signatures, the ByteRange value covers the entire file, including the signature dictionary but excluding the Contents value. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDNAME/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the name of the person or authority signing the document in the signature dictionary entry with the key Name. Prescription level: permitted Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/SDCI/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include a contact information of the signer in the signature dictionary entry with the key ContactInfo. Prescription level: permitted Tag: PAdES baseline and additional signatures. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 9
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
5.3 Testing CMS signature elements
|
This clause defines the test assertions for the CMS signature, included in the signature dictionary entry with the key Contents, requirements. Test assertions for SignedData.certificates attribute: TA id: PAdES_BB/CER/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the signing certificate in the SignedData.certificates attribute of the CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/CER/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/CER/1 Predicate: For new signatures, applications include all certificates needed for path building in the SignedData.certificates attribute. Prescription level: recommended Tag: PAdES baseline and additional signatures. Test assertions for ESS attribute: TA id: PAdES_BB/ESS/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the ESS signing-certificate or signing- certificate-v2 attribute in signedAttrs for every signerInfo in CMS signature. Prescription level: mandatory Tag: conformance layer = B-Level of PAdES baseline profile. TA id: PAdES_BB/ESS/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BS/ESS/1 Predicate: For new signatures, applications include the ESS-signing-certificate in signedAttrs for every signerInfo in CMS signature if SHA-1 hash algorithm is used. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/ESS/3 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BS/ESS/1 Predicate: For new signatures, applications include the ESS-signing-certificate-v2 in signedAttrs for every signerInfo in CMS signature if another hash algorithm than SHA-1 is used. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/ESS/4 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BS/ESS/1 Predicate: For new signatures, applications include the ESS signing-certificate-v2 attribute in signedAttrs for every signerInfo in CMS signature. Prescription level: recommended Tag: PAdES baseline and additional signatures. Test assertion for message-digest attribute presence in CMS signature: TA id: PAdES_BB/MD/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include message-digest attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 10 Test assertions for ContentType attribute: TA id: PAdES_BB/CTY/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include ContentType attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/CTY/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/CTY/1 Predicate: For new signatures, applications set the value id-data in ContentType attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. Test assertion for signature-policy-identifier attribute presence in CMS signature: TA id: PAdES_BB/SPID/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include signature-policy-identifier attribute in CMS signature. Prescription level: permitted Tag: PAdES baseline and additional signatures. Test assertion for signing time requirements: TA id: PAdES_BS/CMSST/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] Predicate: For new signatures, applications do not include the claimed time of signing in the signing time attribute of the CMS signature. Prescription level: mandatory Tag: PAdES baseline signatures. The test assertion for counter-signature attribute presence in CMS signature: TA id: PAdES_BB/CS/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For any signer, CMS signature doesn’t include counter-signature attribute. Prescription level: mandatory Tag: PAdES baseline and additional signatures. Test assertion for content-reference attribute presence in CMS signature: TA id: PAdES_BB/CR/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not include content-reference attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. Test assertion for content-identifier attribute presence in CMS signature: TA id: PAdES_BB/CI/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not include content-identifier attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 11 Test assertion for content-hints attribute presence in CMS signature: TA id: PAdES_BB/CH/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not include content-hints attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. Test assertion for commitment-type-indication attribute presence in CMS signature: TA id: PAdES_BB/CTI/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/SDR/2 Predicate: For new signatures, applications don’t include commitment-type-indication attribute in CMS signature if the signature dictionary entry with the key Reason is present. Prescription level: mandatory Tag: PAdES baseline and additional signatures. Test assertion for signer-location attribute presence in CMS signature: TA id: PAdES_BB/SL/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications do not include signer-location attribute in CMS signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. Test assertion for signer-attributes-v2 attribute presence in CMS signature: TA id: PAdES_BB/SA/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include signer-attributes-v2 attribute in CMS signature. Prescription level: permitted Tag: PAdES baseline and additional signatures. Test assertion for content-time-stamp attribute presence in CMS signature: TA id: PAdES_BB/CTS/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include content-time-stamp attribute in CMS signature. Prescription level: permitted Tag: PAdES baseline and additional signatures.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
6 Testing conformance to PAdES-B-T signatures
| |
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
6.1 General requirements
|
PAdES-B-T signatures as specified in ETSI EN 319 142-1 [1] are built on PAdES-B-B signatures. In consequence, PAdES-B-T signatures shall fulfil the requirements specified in clause 5 of the present document and all the requirements defined in clause 6.2.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
6.2 Testing trusted signing time
|
This clause defines the test assertions for trusted time attribute presence in CMS and/or PAdES signature. TA id: PAdES_BS/TT/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 12 Predicate: For new signatures, applications include signature-time-stamp attribute in CMS signature or Document Time Stamp in PAdES signature. Prescription level: mandatory Tag: PAdES baseline signatures. TA id: PAdES_BB/STS/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include signature-time-stamp attribute in CMS signature. Prescription level: permitted Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DTS/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include Document Time Stamp in PAdES signature. Prescription level: permitted Tag: PAdES baseline and additional signatures.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
7 Testing conformance to PAdES-B-LT signatures
| |
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
7.1 General requirements
|
PAdES-B-LT signatures as specified in ETSI EN 319 142-1 [1] are built on PAdES-B-T signatures. In consequence, PAdES-B-LT signatures shall fulfil the requirements specified in clauses 5 and 6 of the present document and all the requirements defined in clause 7.2.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
7.2 Testing DSS dictionary
|
This clause defines the test assertion for Document Security Store dictionary elements requirements. TA id: PAdES_BB/DSS/1 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the DSS dictionary in the PAdES signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DSS/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/DSS/1 Predicate: For new signatures, applications include the full set of certificates used to validate the signature, not yet included in the SignedData.certificates attribute of the CMS signature, in the DSS dictionary entry with the key Certs. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DSS/3 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/DSS/1 Predicate: For new signatures, applications include the full set of revocation data used to validate the signature in the DSS dictionary entries with the keys CRLs or OCSPs. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DSS/4 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/DSS/1 Predicate: For new signatures, applications do not include any VRI entry in the DSS dictionary. Prescription level: recommended Tag: PAdES baseline and additional signatures. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 13 TA id: PAdES_BB/DSS/5 Normative source: [1] – Clause 5.4.2 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include the value "DSS" in the Document Security Store dictionary entry with the key Type. Prescription level: mandatory Tag: PAdES baseline and additional signatures.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
8 Testing conformance to PAdES-B-LTA signatures
| |
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
8.1 General requirements
|
PAdES-B-LTA signatures as specified in ETSI EN 319 142-1 [1] are built on PAdES-B-LT signatures. In consequence, PAdES-B-LTA signatures shall fulfil the requirements specified in clauses 5, 6 and 7 of the present document and all the requirements defined in clause 8.2.
|
5c0b350c91042dc33e3f254a26cb35a1
|
119 144-4
|
8.2 Testing DTS dictionary
|
This clause defines the test assertion for Document Security Store and Document Time-Stamp dictionary elements requirements. TA id: PAdES_BB/DTS/2 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Predicate: For new signatures, applications include Document Time Stamp dictionary in PAdES signature. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DTS/3 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/DTS/2 Predicate: For new signatures, applications include the value DocTimeStamp in the DTS dictionary entry with the key Type. Prescription level: mandatory Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DTS/4 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/DTS/2 Predicate: For new signatures, applications include the value "ETSI.RFC3161" in the DTS dictionary entry with the key SubFilter. Prescription level: recommended Tag: PAdES baseline and additional signatures. TA id: PAdES_BB/DTS/5 Normative source: [1] – Clause 6.3 Target: PAdES signature generator claiming conformance to PAdES signatures as specified in [1] or in [2] Prerequisites: PAdES_BB/DTS/2 Predicate: For new signatures, applications include the TimeStampToken, see [i.2], in the DTS dictionary entry with the key Contents. Prescription level: mandatory Tag: PAdES baseline and additional signatures. ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 14 Annex A (informative): Bibliography ETSI EN 319 422: "Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles". ETSI ETSI TS 119 144-4 V1.1.1 (2016-06) 15 History Document history V1.1.1 June 2016 Publication
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
1 Scope
|
The present document provides a generic schema for machine-readable cryptographic algorithms, and cipher suites catalogues based on IETF RFC 5698 [1] and specifies different formats such as XML [i.4] and JSON [i.5]. The present document is limited to a descriptive schema for algorithms and all parameters involved. No assessment of the suitability of any cryptographic algorithm, or cipher suite is given in the present document. The present document focuses on signature-related algorithms, and cipher suites, and puts an emphasis on enabling a refined suitability description of the algorithms with respect to its status of recommendation as well as the specific context of usage an algorithm is assessed for.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
2 References
| |
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] IETF RFC 5698 (11-2009): "Data Structure for the Security Suitability of Cryptographic Algorithms (DSSC)".
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.2] ETSI TS 119 312: "Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites". [i.3] SOG-IS Crypto Working Group: "SOG-IS Crypto Evaluation Scheme - Agreed Cryptographic Mechanisms" Version 1.2, January 2020. [i.4] The World Wide Web Consortium (W3C®): "Extensible Markup Language (XML)". [i.5] IETF RFC 8259 (12-2017): "The JavaScript Object Notation (JSON) Data Interchange Format". [i.6] JSON Schema Specification. [i.7] The World Wide Web Consortium (W3C®): "XML namespace definition". ETSI ETSI TS 119 322 V1.2.1 (2024-12) 7 [i.8] ETSI TS 119 182-1: "Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures". [i.9] ETSI EN 319 132-1: "Electronic Signatures and Trust Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures".
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
3 Definition of terms, symbols and abbreviations
| |
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.1], IETF RFC 5698 [1] and the following apply: AdES (digital) signature: digital signature that is either a CAdES signature (CMS), or a PAdES signature (PDF), or a XAdES signature (XML), or a JAdES signature (JSON)
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
3.2 Symbols
|
Void.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: CMS Cryptographic Message Syntax DSA Digital Signature Algorithm DSSC Data Structure for the Security Suitability of Cryptographic Algorithms JSON JavaScript Object Notation OCSP Online Certificate Status Protocol OID Object IDentifier RSA RSA cryptosystem, named after Rivest, Shamir, Adleman SHA Secure Hash Algorithm SOG-IS Senior Officials Group Information Systems Security URI Uniform Resource Identifier XML eXtensible Markup Language 4 Overall structure of algorithms, and cipher suites catalogues
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.1 Overview
|
The present document is based on IETF RFC 5698 [1]. A machine-readable catalogue may contain only a subset of the defined algorithms. Clause 4.2 describes the semantic of the different elements of the machine-readable algorithm catalogue independent of the specific format used. Annexes A and B specify the format-specific syntax for XML [i.4], [i.7] and JSON [i.5], [i.6] instances of this schema, respectively. All the semantic of elements shall remain as defined in IETF RFC 5698 [1] where not stated otherwise. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 8
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2 Elements of a machine-readable algorithm catalogue
| |
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.1 Security-suitability-policy
|
The security-suitability-policy element shall be the root element of the machine-readable catalogue. The semantic of the security-suitability-policy element shall be as defined IETF RFC 5698 [1], clause 3.1.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.2 Policy-name
|
The semantic of the policy-name element shall be as defined in IETF RFC 5698 [1], clause 3.2.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.3 Publisher
|
The semantic of the publisher element shall be as defined in IETF RFC 5698 [1], clause 3.3.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.4 Policy-issue-date
|
The semantic of the policy-issue-date element shall be as defined in IETF RFC 5698 [1], clause 3.4.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.5 NextUpdate
|
The semantic of the next-update element shall be as defined in IETF RFC 5698 [1], clause 3.5.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.6 Usage
|
The semantic of the usage element shall be as defined in IETF RFC 5698 [1], clause 3.6.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.7 Algorithm
|
The semantic of the algorithm element shall be as defined in IETF RFC 5698 [1], clause 3.7.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.8 Algorithm-identifier
|
The semantic of the algorithm-identifier element shall be as defined in IETF RFC 5698 [1], clause 3.8.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.9 Evaluation
| |
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.9.1 General description
|
The semantic of the evaluation element shall be as defined in IETF RFC 5698 [1], clause 3.9. The evaluation element may contain a more-details element. The more-details element may contain zero, one or more algorithm-usage elements as defined in clause 4.2.9.2 to allow parameter- and context-specific evaluations of cryptographic mechanisms. The more-details element may contain a recommendation element as defined in clause 4.2.9.3 to distinguish between recommended and legacy mechanisms, as defined in ETSI TS 119 312 [i.2], clause 3.1. The syntax is specified in clauses A.9 (XML) and B.2.9 (JSON), respectively.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.9.2 Algorithm-usage
|
The algorithm-usage element shall contain a URI which allows to further distinguish the validity period of an algorithm based on the usage. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 9 EXAMPLE 1: It allows to differentiate between signature creation and signature validation use cases. NOTE 1: The amount of data of certificates is comparably small to arbitrary documents, hence when applying a hash algorithm to certificates they are less affected by lowered collision-resistance of the hash algorithm, which in turn could allow for a prolonged suitability period in this specific use case. Omitting all usage types shall be equivalent to no restriction at all. When the validity element is provided in the corresponding evaluation element containing an algorithm-usage element, all use cases hierarchical below the one given are included according to the hierarchy diagram (figure 1). Figure 1: Algorithm usage type hierarchy EXAMPLE 2: Sign data will include all other types, i.e. it is equivalent to no restriction when no further restriction is provided for the use cases lying below. NOTE 2: The hierarchy tree inherently includes ambiguity, i.e. there is more than one path from root (sign data) to tree leaves of validation types. The following algorithm-usage URIs are defined: • http://uri.etsi.org/19322/sign_data shall be used to indicate that the evaluation is applicable for any signed data. • http://uri.etsi.org/19322/sign_data/sign_certificates shall be used to indicate that the evaluation is applicable for signing certificates. • http://uri.etsi.org/19322/sign_data/sign_ocsp shall be used to indicate that the evaluation is applicable for signing OCSP responses. • http://uri.etsi.org/19322/sign_data/sign_timestamps shall be used to indicate that the evaluation is applicable for signing timestamps. • http://uri.etsi.org/19322/sign_data/sign_certificates shall be used to indicate that the evaluation is applicable for signing certificates. • http://uri.etsi.org/19322/sign_data/sign_certificates shall be used to indicate that the evaluation is applicable for signing certificates. • http://uri.etsi.org/19322/sign_data/validate_data shall be used to indicate that the evaluation is applicable for the validation of any signed data. • http://uri.etsi.org/19322/sign_data/validate_data/validate_certificates shall be used to indicate that the evaluation is applicable for the validation of certificates. • http://uri.etsi.org/19322/sign_data/validate_data/validate_ocsp shall be used to indicate that the evaluation is applicable for the validation of OCSP responses. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 10 • http://uri.etsi.org/19322/sign_data/validate_data/validate_timestamps shall be used to indicate that the evaluation is applicable for the validation of timestamps. NOTE 3: The present document defines URIs which are not used as pointers to a specific location but are used as unique identifiers.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.9.3 Recommendation
|
The recommendation element shall be used to indicate that a mechanism and its parameters are either Recommended (R) or Legacy (L), as defined in ETSI TS 119 312 [i.2], clause 3.1. Omitting this element shall be equivalent to a recommended mechanism when the end date is absent or lies in the future.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.10 Parameter
|
The semantic of the parameter element shall be as defined in IETF RFC 5698 [1], clause 3.10.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.11 Validity
|
The semantic of the validity element shall be as defined in IETF RFC 5698 [1], clause 3.11.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.12 Information
|
The semantic of the information element shall be as defined in IETF RFC 5698 [1], clause 3.12.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
4.2.13 Signature
|
The signature element shall be as defined in IETF RFC 5698 [1], clause 3.13. 5 Machine-readable cryptographic algorithms, and cipher suites catalogues Machine-readable cryptographic algorithms, and cipher suites catalogues may be defined in different formats. Two formats are specified in the annexes A (XML [i.4]) and B (JSON [i.5]). Additional formats may be defined in a future version of the present document. Machine-readable cryptographic algorithms, and cipher suites catalogues should be published in all defined formats, i.e. in XML and JSON format until further additions.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
6 Definition of Parameters
|
For interoperability reasons the recommendation of parameters names for RSA and DSA of IETF RFC 5698 [1], clause 5 should be followed.
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
7 Processing
|
The processing shall be as defined in IETF RFC 5698 [1], clause 6. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 11
|
5598eb5c085b1600fb1024360b9fc028
|
119 322
|
8 Security Considerations
|
The security considerations shall be as defined in IETF RFC 5698 [1], clause 7. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 12 Annex A (normative): XML Policy Schema A.1 SecuritySuitabilityPolicy The SecuritySuitabilityPolicy element shall be as defined in IETF RFC 5698 [1], clause 3.1. The id attribute shall be included when the catalogue is signed. A.2 PolicyName The PolicyName element shall be as defined in IETF RFC 5698 [1], clause 3.2. A.3 Publisher The Publisher element shall be as defined in IETF RFC 5698 [1], clause 3.3. A.4 Policy-issue-date The Policy-issue-date element shall be as defined in IETF RFC 5698 [1], clause 3.4. A.5 NextUpdate The NextUpdate element shall be as defined in IETF RFC 5698 [1], clause 3.5. A.6 Usage NOTE: This element is defined as part of the SecuritySuitabilityPolicy element (see clause A.1). A.7 Algorithm The Algorithm element shall be as defined in IETF RFC 5698 [1], clause 3.7. A.8 AlgorithmIdentifier The AlgorithmIdentifier shall be as defined in IETF RFC 5698 [1], clause 3.8. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 13 A.9 Evaluation A.9.1 MoreDetails NOTE: Instead of the any element of the Evaluation element of IETF RFC 5698 [1], clause 3.9 the MoreDetails element of ExtentionType is used for XML instances of the present schema. <?xml version="1.0" encoding="UTF-8"?> <xs:schema elementFormDefault="qualified" targetNamespace="http://uri.etsi.org/19322/v1.1.1#" xmlns="http://uri.etsi.org/19322/v1.1.1#" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="MoreDetails" type="ExtensionType"/> <xs:complexType mixed="true" name="ExtensionType"> <xs:sequence> <xs:element name="AlgorithmUsage" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Recommendation" minOccurs="0" maxOccurs="1"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:enumeration value="R"/> <xs:enumeration value="L"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:sequence maxOccurs="unbounded" minOccurs="0"> <xs:any namespace="##other" processContents="lax"/> </xs:sequence> </xs:sequence> <xs:anyAttribute namespace="##any"/> </xs:complexType> </xs:schema> A.9.2 AlgorithmUsage NOTE: This element is defined as part of the MoreDetails element (see clause A.9.1). A.9.3 Recommendation NOTE: This element is defined as part of the MoreDetails element (see clause A.9.1). A.10 Parameter The Parameter element shall be as defined in IETF RFC 5698 [1], clause 3.10. A.11 Validity The Validity element shall be as defined in IETF RFC 5698 [1], clause 3.11. A.12 Information The Information element shall be as defined in IETF RFC 5698 [1], clause 3.12. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 14 A.13 Signature The Signature element shall be as defined in IETF RFC 5698 [1], clause 3.13. XAdES [i.9] should be used to sign XML catalogue instances. A.14 XML Schema file location for namespace http://uri.etsi.org/19322/v1.1.1# The file available at https://forge.etsi.org/rep/esi/x19_322_algocat_schema/raw/v1.2.1/19322algocatxmlschema.xsd ("19322algocatxmlschema.xsd") contains the definitions of elements and types defined within the namespace whose URI value is http://uri.etsi.org/19322/v1.1.1#. NOTE: Independent of the present document, the latest version of the XML Schema file is linked to https://forge.etsi.org/rep/esi/x19_322_algocat_schema/-/blob/master/19322algocatxmlschema.xsd. The hash values of the XML Schema file depending on the used line ends using SHA-256 are: • CR LF: a8678baae17b328727c52c6bf0b277526821380b0353149b75af141d9ccec1ad; • LF: a5a812f5eee845d7d692612dad77d41ceae16d8e3089d853c89bde5fd103dfb9; or • CR: 927e7b3cd895477e2af7936aeb4a3f85d74b35c52604158b66832c7b8efd6339. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 15 Annex B (normative): JSON format B.1 General information NOTE: The JSON schema defined in [i.6] is used. All suitability policy elements are entries of the array anyOf as indicated in clause B.2. The object definitions contains all type definitions of the suitability policy elements as indicated in clause B.2. B.2 JSON schema B.2.1 SecuritySuitabilityPolicy "definitions": { "SecuritySuitabilityPolicyType": { "type": "object", "required": [ "PolicyName", "Publisher", "PolicyIssueDate", "Algorithm" ], "properties": { "PolicyName": {"$ref": "#/definitions/PolicyNameType"}, "Publisher": {"$ref": "#/definitions/PublisherType"}, "PolicyIssueDate": { "type": "string", "format": "date-time" }, "NextUpdate": { "type": "string", "format": "date-time" }, "Usage": {"type": "string"}, "Algorithm": { "type": "array", "items": {"$ref": "#/definitions/AlgorithmType"}, "minItems": 1 }, "Signature": {"$ref": "#/definitions/SignatureType"}, "version": { "type": "string", "default": "1" }, "lang": { "type": "string", "default": "en" } } }, "additionalProperties": false } B.2.2 PolicyName "PolicyNameType": { "type": "object", "required": ["Name"], "properties": { "Name": {"type": "string"}, "ObjectIdentifier": {"type": "string"}, "URI": { "type": "string", ETSI ETSI TS 119 322 V1.2.1 (2024-12) 16 "format": "uri" } }, "additionalProperties": false } B.2.3 Publisher "PublisherType": { "type": "object", "required": ["Name"], "properties": { "Name": {"type": "string"}, "Address": {"type": "string"}, "URI": { "type": "string", "format": "uri" } }, "additionalProperties": false } B.2.4 PolicyIssueDate NOTE: This element is defined as part of the SecuritySuitabilityPolicy element (see clause B.2.1). B.2.5 NextUpdate NOTE: This element is defined as part of the SecuritySuitabilityPolicy element (see clause B.2.1). B.2.6 Usage NOTE: This element is defined as part of the SecuritySuitabilityPolicy element (see clause B.2.1). B.2.7 Algorithm "AlgorithmType": { "type": "object", "required": [ "AlgorithmIdentifier", "Evaluation" ], "properties": { "AlgorithmIdentifier": {"$ref": "#/definitions/AlgorithmIdentifierType"}, "Evaluation": { "type": "array", "items": {"$ref": "#/definitions/EvaluationType"}, "minItems": 1 }, "Information": {"$ref": "#/definitions/InformationType"} }, "additionalProperties": false } B.2.8 AlgorithmIdentifier "AlgorithmIdentifierType": { "type": "object", "required": [ "Name", "ObjectIdentifier" ], "properties": { "Name": {"type": "string"}, "ObjectIdentifier": { "type": "string", "format": "oid", "minItems": 1 ETSI ETSI TS 119 322 V1.2.1 (2024-12) 17 }, "URI": { "type": "string", "format": "uri", "minItems": 0 }, "additionalProperties": false } } B.2.9 Evaluation B.2.9.1 General description "EvaluationType": { "type": "object", "required": ["Validity"], "properties": { "Parameter": { "type": "array", "items": {"$ref": "#/definitions/ParameterType"}, "minItems": 0 }, "Validity": {"$ref": "#/definitions/ValidityType"}, "AlgorithmUsage": { "type": "string", "format": "uri" }, "Recommendation": { "type": "string", "pattern": "L|R" }, "Any": {"type": "object"} }, "additionalProperties": true } B.2.9.2 AlgorithmUsage NOTE: This element is defined as part of the Evaluation element (see clause B.2.9.1). B.2.9.3 Recommendation NOTE: This element is defined as part of the Evaluation element (see clause B.2.9.1). B.2.10 Parameter "ParameterType": { "type": "object", "required": ["name"], "properties": { "Min": {"type": "integer"}, "Max": {"type": "integer"}, "Any": {"type": "object"}, "name": {"type": "string"} }, "additionalProperties": true } B.2.11 Validity "ValidityType": { "type": "object", "properties": { "Start": { "type": "string", "format": "date" }, "End": { ETSI ETSI TS 119 322 V1.2.1 (2024-12) 18 "type": "string", "format": "date" } }, "additionalProperties": false } B.2.12 Information "InformationType": { "type": "object", "required": ["Text"], "properties": { "Text": { "type": "array", "items": {"type": "string"}, "minItems": 1 } }, "additionalProperties": false } B.2.13 Signature JAdES [i.8] should be used to sign JSON catalogue instances. B.3 JSON Schema file location The file available at https://forge.etsi.org/rep/esi/x19_322_algocat_schema/raw/v1.2.1/19322algocatjsonschema.json ("19322algocatjsonschema.json") contains the definitions of elements and types defined within the JSON schema associated to the present document. NOTE: Independent of the present document, the latest version of the JSON Schema file is linked to https://forge.etsi.org/rep/esi/x19_322_algocat_schema/-/blob/master/19322algocatjsonschema.json. The hash values of the JSON Schema file depending on the used line ends using SHA-256 are: • CR LF: 7f15c62df0ea6ed731b679d428adb3921df720ea029f10147b6116099458d225; • LF: 096e024ce57f2589d00c1cc354a19e84c22d7ae5beb4c6de07e74c993f7c1cd3; or • CR: ce272be358054f2521aaca1db8d68fbc5f67cd70a248986e1e6a121bed4bfaa9. ETSI ETSI TS 119 322 V1.2.1 (2024-12) 19 History Document history V1.1.1 November 2022 Publication V1.2.1 December 2024 Publication
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.