generated from martinthomson/internet-draft-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Script updating gh-pages from 3ce7d22. [ci skip]
- Loading branch information
ID Bot
committed
Aug 27, 2024
1 parent
7cae7f0
commit 8a9e79f
Showing
3 changed files
with
15 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,11 +13,11 @@ | |
| This mechanism enables faster validation as access to the original payload is not required for signature validation. | ||
| Additionally, hints of the detached payload's content format and availability are defined providing references to optional discovery mechanisms that can help to find original payload content. | ||
| " name="description"> | ||
| <meta content="xml2rfc 3.22.0" name="generator"> | ||
| <meta content="xml2rfc 3.23.0" name="generator"> | ||
| <meta content="Internet-Draft" name="keyword"> | ||
| <meta content="draft-ietf-cose-hash-envelope-latest" name="ietf.draft"> | ||
| <!-- Generator version information: | ||
| xml2rfc 3.22.0 | ||
| xml2rfc 3.23.0 | ||
| Python 3.12.3 | ||
| ConfigArgParse 1.7 | ||
| google-i18n-address 3.1.0 | ||
|
|
@@ -1032,7 +1032,7 @@ | |
| </tr></thead> | ||
| <tfoot><tr> | ||
| <td class="left">Steele, et al.</td> | ||
| <td class="center">Expires 22 February 2025</td> | ||
| <td class="center">Expires 28 February 2025</td> | ||
| <td class="right">[Page]</td> | ||
| </tr></tfoot> | ||
| </table> | ||
|
|
@@ -1045,12 +1045,12 @@ | |
| <dd class="internet-draft">draft-ietf-cose-hash-envelope-latest</dd> | ||
| <dt class="label-published">Published:</dt> | ||
| <dd class="published"> | ||
| <time datetime="2024-08-21" class="published">21 August 2024</time> | ||
| <time datetime="2024-08-27" class="published">27 August 2024</time> | ||
| </dd> | ||
| <dt class="label-intended-status">Intended Status:</dt> | ||
| <dd class="intended-status">Standards Track</dd> | ||
| <dt class="label-expires">Expires:</dt> | ||
| <dd class="expires"><time datetime="2025-02-22">22 February 2025</time></dd> | ||
| <dd class="expires"><time datetime="2025-02-28">28 February 2025</time></dd> | ||
| <dt class="label-authors">Authors:</dt> | ||
| <dd class="authors"> | ||
| <div class="author"> | ||
|
|
@@ -1110,7 +1110,7 @@ <h2 id="name-status-of-this-memo"> | |
| time. It is inappropriate to use Internet-Drafts as reference | ||
| material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> | ||
| <p id="section-boilerplate.1-4"> | ||
| This Internet-Draft will expire on 22 February 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p> | ||
| This Internet-Draft will expire on 28 February 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p> | ||
| </section> | ||
| </div> | ||
| <div id="copyright"> | ||
|
|
@@ -1231,7 +1231,7 @@ <h2 id="name-introduction"> | |
| <p id="section-1-3">When producing COSE_sign1 with remote signing services, such as a signing api exposed over HTTPS and backed by an HSM, the "ToBeSigned" bytes as described in <span><a href="https://rfc-editor.org/rfc/rfc9052#section-4.4" class="relref">Section 4.4</a> of [<a href="#RFC9052" class="cite xref">RFC9052</a>]</span> need to be transmitted to the HSM in order to be signed.<a href="#section-1-3" class="pilcrow">¶</a></p> | ||
| <p id="section-1-4">Some signature algorithms such as ES256 or ES384 allow the "ToBeSigned" to be hashed on the client and sent to the server along with metadata in order to produce a signature.<a href="#section-1-4" class="pilcrow">¶</a></p> | ||
| <p id="section-1-5">Other signature algorithms such as EdDSA with Ed25519, or ML-DSA do not expose such a capability.<a href="#section-1-5" class="pilcrow">¶</a></p> | ||
| <p id="section-1-6">By producing the "ToBeSigned" on the client, and ensuring that the payload is always a hashed value, the total size of the message to be sent to the servce for signing is constrained.<a href="#section-1-6" class="pilcrow">¶</a></p> | ||
| <p id="section-1-6">By producing the "ToBeSigned" on the client, and ensuring that the payload is always a hashed value, the total size of the message to be sent to the service for signing is constrained.<a href="#section-1-6" class="pilcrow">¶</a></p> | ||
| <p id="section-1-7">It is still possible for the protected header to be large, but the payload will always be of a fixed size, associated with the hash function chosen.<a href="#section-1-7" class="pilcrow">¶</a></p> | ||
| </section> | ||
| </div> | ||
|
|
@@ -1596,7 +1596,7 @@ <h3 id="name-digicert-preview"> | |
| <p id="appendix-A.3-5">Coverage: The current version ('main') implements this specification and demonstrates hash envelope signing with DigiCert Software Trust Manager.<a href="#appendix-A.3-5" class="pilcrow">¶</a></p> | ||
| <p id="appendix-A.3-6">License: MIT<a href="#appendix-A.3-6" class="pilcrow">¶</a></p> | ||
| <p id="appendix-A.3-7">Implementation Experience: Interop testing has been performed between DigiCert and DataTrails. The code works as proof of concept, but is not yet production ready.<a href="#appendix-A.3-7" class="pilcrow">¶</a></p> | ||
| <p id="appendix-A.3-8">Contact: Corey Bonnell ([email protected]>)<a href="#appendix-A.3-8" class="pilcrow">¶</a></p> | ||
| <p id="appendix-A.3-8">Contact: Corey Bonnell ([email protected])<a href="#appendix-A.3-8" class="pilcrow">¶</a></p> | ||
| </section> | ||
| </div> | ||
| </section> | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,10 +5,10 @@ | |
| Network Working Group O. Steele | ||
| Internet-Draft Transmute | ||
| Intended status: Standards Track S. Lasker | ||
| Expires: 22 February 2025 DataTrails | ||
| Expires: 28 February 2025 DataTrails | ||
| H. Birkholz | ||
| Fraunhofer SIT | ||
| 21 August 2024 | ||
| 27 August 2024 | ||
|
|
||
|
|
||
| COSE Hash Envelope | ||
|
|
@@ -56,7 +56,7 @@ Status of This Memo | |
| time. It is inappropriate to use Internet-Drafts as reference | ||
| material or to cite them other than as "work in progress." | ||
|
|
||
| This Internet-Draft will expire on 22 February 2025. | ||
| This Internet-Draft will expire on 28 February 2025. | ||
|
|
||
| Copyright Notice | ||
|
|
||
|
|
@@ -124,7 +124,7 @@ Table of Contents | |
|
|
||
| By producing the "ToBeSigned" on the client, and ensuring that the | ||
| payload is always a hashed value, the total size of the message to be | ||
| sent to the servce for signing is constrained. | ||
| sent to the service for signing is constrained. | ||
|
|
||
| It is still possible for the protected header to be large, but the | ||
| payload will always be of a fixed size, associated with the hash | ||
|
|
@@ -447,7 +447,7 @@ A.3. DigiCert Preview | |
| DigiCert and DataTrails. The code works as proof of concept, but is | ||
| not yet production ready. | ||
|
|
||
| Contact: Corey Bonnell ([email protected]>) | ||
| Contact: Corey Bonnell ([email protected]) | ||
|
|
||
| Acknowledgments | ||
|
|
||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters