From e47f3f4527aba593ecbebac45417c912d4c2f268 Mon Sep 17 00:00:00 2001 From: Sean Turner Date: Thu, 12 Dec 2024 06:22:38 -0500 Subject: [PATCH] refer to signature vice signatureValue (#28) Since we switched to the parameterized type the field is "signature" not "signatureValue" in the ASN.1 excerpt. --- draft-ietf-lamps-x509-slhdsa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/draft-ietf-lamps-x509-slhdsa.md b/draft-ietf-lamps-x509-slhdsa.md index 836fb2b..ef49afc 100644 --- a/draft-ietf-lamps-x509-slhdsa.md +++ b/draft-ietf-lamps-x509-slhdsa.md @@ -297,7 +297,7 @@ public key is the concatenation of these three elements, i.e. R || SIG_FORS || S The raw octet string representing the signature is encoded directly in the BIT STRING without adding any additional ASN.1 wrapping. For example, in the Certificate structure, the raw signature -value is encoded in the "signatureValue" BIT STRING field. +value is encoded in the "signature" BIT STRING field. This document does not define the use of HashSLH-DSA to sign certificates or CRLs, but it does allow the use of HashSLH-DSA public keys in end-entity