Expand description
The Signature-Input and Signature structured fields.
RFC 9421 §3.2 step 7 builds @signature-params by serializing the parsed signature
parameters, never by copying the field’s wire bytes. SignatureParams::serialize is that
serialization, and signers use it to write Signature-Input, so a conforming client produces
the same bytes on the wire and in the signature base. Whitespace that Structured Fields allows
on the wire therefore cannot change the signature base, and neither can any other difference
between what was parsed and what was signed.
Structs§
- Signature
Params - The parsed value of the
integritymember ofSignature-Input.
Enums§
- Nonce
Error - Why a request nonce was refused.
- Param
- A signature parameter of the profile. The profile accepts exactly these three.
- Signature
Field Error - Why a
Signaturefield was refused. - Signature
Input Error - Why a
Signature-Inputfield was refused.
Constants§
- MIN_
NONCE_ BYTES - Decoded length a request nonce must reach.
Functions§
- generate_
nonce - A fresh request nonce:
MIN_NONCE_BYTESbytes from the OS CSPRNG, padded base64. - parse_
signature - Parses a
Signaturefield value into the signature bytes. - signature_
field - The
Signaturefield value carryingsignature. - validate_
nonce - Checks a request nonce: canonical padded base64 decoding to at least
MIN_NONCE_BYTES.