Skip to content

Commit

Permalink
Script updating gh-pages from 01194b6. [ci skip]
Browse files Browse the repository at this point in the history
  • Loading branch information
ID Bot committed Sep 11, 2024
1 parent 956b693 commit 9c5caaf
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 25 deletions.
38 changes: 18 additions & 20 deletions draft-ietf-lamps-pq-composite-sigs.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1036,7 +1036,7 @@
</tr></thead>
<tfoot><tr>
<td class="left">Ounsworth, et al.</td>
<td class="center">Expires 12 March 2025</td>
<td class="center">Expires 15 March 2025</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
Expand All @@ -1049,12 +1049,12 @@
<dd class="internet-draft">draft-ietf-lamps-pq-composite-sigs-latest</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2024-09-08" class="published">8 September 2024</time>
<time datetime="2024-09-11" class="published">11 September 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-03-12">12 March 2025</time></dd>
<dd class="expires"><time datetime="2025-03-15">15 March 2025</time></dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
Expand Down Expand Up @@ -1104,7 +1104,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 12 March 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
This Internet-Draft will expire on 15 March 2025.<a href="#section-boilerplate.1-4" class="pilcrow"></a></p>
</section>
</div>
<div id="copyright">
Expand Down Expand Up @@ -1165,11 +1165,9 @@ <h2 id="name-copyright-notice">
</li>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="auto internal xref">4.2</a>.  <a href="#name-signature-generation" class="internal xref">Signature Generation</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2.2.1">
<p id="section-toc.1-1.4.2.2.2.1.1"><a href="#section-4.2.1" class="auto internal xref">4.2.1</a>.  <a href="#name-signature-verify" class="internal xref">Signature Verify</a></p>
</li>
</ul>
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3">
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="auto internal xref">4.3</a>.  <a href="#name-signature-verify" class="internal xref">Signature Verify</a></p>
</li>
</ul>
</li>
Expand Down Expand Up @@ -1616,17 +1614,19 @@ <h3 id="name-signature-generation">
</figcaption></figure>
</div>
<p id="section-4.2-6">It is possible to construct <code>CompositePrivateKey</code>(s) to generate signatures from component keys stored in separate software or hardware keystores. Variations in the process to accommodate particular private key storage mechanisms are considered to be conformant to this document so long as it produces the same output as the process sketched above.<a href="#section-4.2-6" class="pilcrow"></a></p>
</section>
</div>
<div id="sec-comp-sig-verify">
<section id="section-4.2.1">
<h4 id="name-signature-verify">
<a href="#section-4.2.1" class="section-number selfRef">4.2.1. </a><a href="#name-signature-verify" class="section-name selfRef">Signature Verify</a>
</h4>
<p id="section-4.2.1-1">Verification of a composite signature involves reconstructing the M' message first by concatenating the Domain separator (i.e., the DER encoding of the used Composite scheme's OID) with the Hash of the original message and then applying each component algorithm's verification process to the new message M'.<a href="#section-4.2.1-1" class="pilcrow"></a></p>
<p id="section-4.2.1-2">Compliant applications MUST output "Valid signature" (true) if and only if all component signatures were successfully validated, and "Invalid signature" (false) otherwise.<a href="#section-4.2.1-2" class="pilcrow"></a></p>
<p id="section-4.2.1-3">The following process is used to perform this verification.<a href="#section-4.2.1-3" class="pilcrow"></a></p>
<section id="section-4.3">
<h3 id="name-signature-verify">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-signature-verify" class="section-name selfRef">Signature Verify</a>
</h3>
<p id="section-4.3-1">Verification of a composite signature involves reconstructing the M' message first by concatenating the Domain separator (i.e., the DER encoding of the used Composite scheme's OID) with the Hash of the original message and then applying each component algorithm's verification process to the new message M'.<a href="#section-4.3-1" class="pilcrow"></a></p>
<p id="section-4.3-2">Compliant applications MUST output "Valid signature" (true) if and only if all component signatures were successfully validated, and "Invalid signature" (false) otherwise.<a href="#section-4.3-2" class="pilcrow"></a></p>
<p id="section-4.3-3">The following process is used to perform this verification.<a href="#section-4.3-3" class="pilcrow"></a></p>
<span id="name-composite-verifypk-message-"></span><div id="alg-composite-verify">
<figure id="figure-3">
<div class="alignLeft art-text artwork" id="section-4.2.1-4.1">
<div class="alignLeft art-text artwork" id="section-4.3-4.1">
<pre>
Composite Verify(pk, Message, signature)
Input:
Expand Down Expand Up @@ -1680,11 +1680,9 @@ <h4 id="name-signature-verify">
</div>
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
<a href="#name-composite-verifypk-message-" class="selfRef">Composite Verify(pk, Message, signature)</a>
</figcaption></figure>
</div>
<p id="section-4.2.1-5">It is possible to construct <code>CompositePublicKey</code>(s) to verify signatures from component keys stored in separate software or hardware keystores. Variations in the process to accommodate particular private key storage mechanisms are considered to be conformant to this document so long as it produces the same output as the process sketched above.<a href="#section-4.2.1-5" class="pilcrow"></a></p>
</section>
</figcaption></figure>
</div>
<p id="section-4.3-5">It is possible to construct <code>CompositePublicKey</code>(s) to verify signatures from component keys stored in separate software or hardware keystores. Variations in the process to accommodate particular private key storage mechanisms are considered to be conformant to this document so long as it produces the same output as the process sketched above.<a href="#section-4.3-5" class="pilcrow"></a></p>
</section>
</div>
</section>
Expand Down
10 changes: 5 additions & 5 deletions draft-ietf-lamps-pq-composite-sigs.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@
LAMPS M. Ounsworth
Internet-Draft J. Gray
Intended status: Standards Track Entrust
Expires: 12 March 2025 M. Pala
Expires: 15 March 2025 M. Pala
OpenCA Labs
J. Klaussner
Bundesdruckerei GmbH
S. Fluhrer
Cisco Systems
8 September 2024
11 September 2024


Composite ML-DSA for use in Internet PKI
Expand Down Expand Up @@ -47,7 +47,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 12 March 2025.
This Internet-Draft will expire on 15 March 2025.

Copyright Notice

Expand All @@ -74,7 +74,7 @@ Table of Contents
4. Cryptographic Primitives
4.1. Key Generation
4.2. Signature Generation
4.2.1. Signature Verify
4.3. Signature Verify
5. Composite Key Structures
5.1. pk-CompositeSignature
5.2. CompositeSignaturePublicKey
Expand Down Expand Up @@ -426,7 +426,7 @@ Signature Generation Process:
conformant to this document so long as it produces the same output as
the process sketched above.

4.2.1. Signature Verify
4.3. Signature Verify

Verification of a composite signature involves reconstructing the M'
message first by concatenating the Domain separator (i.e., the DER
Expand Down

0 comments on commit 9c5caaf

Please sign in to comment.