Skip to content

Commit

Permalink
Fix up code block in comment (added back ticks)
Browse files Browse the repository at this point in the history
  • Loading branch information
johngray-dev authored Jan 29, 2025
1 parent 3548bbe commit 9dd0052
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion draft-ietf-lamps-pq-composite-sigs.md
Original file line number Diff line number Diff line change
Expand Up @@ -1532,7 +1532,7 @@ There are mechanisms within Internet PKI where trusted public keys do not appear

## Use of Prefix to for attack mitigation

The Prefix value specified in the message format calculated in {{sec-sigs}} can be used by a traditional verifier to detect if the composite signature has been stripped apart. An attacker would need to compute M' = Prefix || Domain || len(ctx) || ctx || M or M' := Prefix || Domain || len(ctx) || ctx || HashOID || PH(M). Since the Prefix is the constant String "CompositeAlgorithmSignatures2025" (Byte encoding 436F6D706F73697465416C676F726974686D5369676E61747572657332303235 ) a traditional verifier can check if the Message starts with this prefix and reject the message.
The Prefix value specified in the message format calculated in {{sec-sigs}} can be used by a traditional verifier to detect if the composite signature has been stripped apart. An attacker would need to compute `M' = Prefix || Domain || len(ctx) || ctx || M` or `M' := Prefix || Domain || len(ctx) || ctx || HashOID || PH(M)`. Since the Prefix is the constant String "CompositeAlgorithmSignatures2025" (Byte encoding 436F6D706F73697465416C676F726974686D5369676E61747572657332303235 ) a traditional verifier can check if the Message starts with this prefix and reject the message.

<!-- End of Security Considerations section -->

Expand Down

0 comments on commit 9dd0052

Please sign in to comment.