DateKeys

Commit Graph

Author	SHA1	Message	Date
dev	4ce4d59c8d	Tests of the CMS reader: certificates field by field, every check, fuzzing The builder of the tests, cmstest: - NewCert writes a certificate from the DER of its tbsCertificate, field by field: names of any string type with any bytes (UTF8String, PrintableString with an underscore or an at sign, IA5String, TeletexString, BMPString of odd length or with a surrogate, VisibleString, NumericString), an attribute twice or none, no version, times with a fraction, an extension twice, a compressed EC key, an even modulus, and any signature. A Signer made so serves Signature and Token. - Options for the version of a SignerInfo, the hashAlgorithm and the certHash of an ESSCertIDv2, a signatureAlgorithm other than the one of the key, a certificate twice, two content-type attributes, an attribute with an arc of 2^31, a SignerInfo twice, BER, signerInfos out of order, two signature-time-stamp attributes, and edits of the SignedData and of each SignerInfo. - Token options for any accuracy, a genTime of free text, ordering FALSE, a field after the last, an imprint of any length, no message-digest, a CRL in crls and the certificate of the authority twice. - Edits of the DER after signing: Edit, Retag, Withdraw (a SignerInfo removed), WithoutTimeStamp (a CAdES-T removed), Merge (a co-signature) and Indefinite. The tests of internal/cms and internal/der fail for each check of cms.go, cert.go, verify.go and der.go. A mutation run, which replaces each leaf of each condition by false and by true, one at a time, kills every mutant that is not equivalent to the code it mutates. FuzzParseSignature, FuzzParseToken, FuzzParseCert and FuzzDERCheck, seeded with security_cms.json and with what cmstest builds: no panic, what Check accepts Split reads, and the parsers fail only with ErrForm or ErrAlgorithm. capsule: the case of a seal outside the validity of the certificate gave an invalid seal; it now tests a certificate that expired before a valid seal (out of validity) apart from an authority that was not valid at its time (invalid seal). SIGNERS out of order, empty, too long, with 31 bytes or with a hash twice are F1 beside a CMS signature that is valid for the AUTHOR_MESSAGE of those SIGNERS, and the names of certificates show as spec v0.12 §29.7 says. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	6 days ago

Author

SHA1

Message

Date

dev

4ce4d59c8d

Tests of the CMS reader: certificates field by field, every check, fuzzing

The builder of the tests, cmstest:

- NewCert writes a certificate from the DER of its tbsCertificate, field by
  field: names of any string type with any bytes (UTF8String,
  PrintableString with an underscore or an at sign, IA5String,
  TeletexString, BMPString of odd length or with a surrogate,
  VisibleString, NumericString), an attribute twice or none, no version,
  times with a fraction, an extension twice, a compressed EC key, an even
  modulus, and any signature. A Signer made so serves Signature and Token.
- Options for the version of a SignerInfo, the hashAlgorithm and the
  certHash of an ESSCertIDv2, a signatureAlgorithm other than the one of
  the key, a certificate twice, two content-type attributes, an attribute
  with an arc of 2^31, a SignerInfo twice, BER, signerInfos out of order,
  two signature-time-stamp attributes, and edits of the SignedData and of
  each SignerInfo.
- Token options for any accuracy, a genTime of free text, ordering FALSE,
  a field after the last, an imprint of any length, no message-digest, a
  CRL in crls and the certificate of the authority twice.
- Edits of the DER after signing: Edit, Retag, Withdraw (a SignerInfo
  removed), WithoutTimeStamp (a CAdES-T removed), Merge (a co-signature)
  and Indefinite.

The tests of internal/cms and internal/der fail for each check of cms.go,
cert.go, verify.go and der.go. A mutation run, which replaces each leaf of
each condition by false and by true, one at a time, kills every mutant
that is not equivalent to the code it mutates.

FuzzParseSignature, FuzzParseToken, FuzzParseCert and FuzzDERCheck, seeded
with security_cms.json and with what cmstest builds: no panic, what Check
accepts Split reads, and the parsers fail only with ErrForm or
ErrAlgorithm.

capsule: the case of a seal outside the validity of the certificate gave
an invalid seal; it now tests a certificate that expired before a valid
seal (out of validity) apart from an authority that was not valid at its
time (invalid seal). SIGNERS out of order, empty, too long, with 31 bytes
or with a hash twice are F1 beside a CMS signature that is valid for the
AUTHOR_MESSAGE of those SIGNERS, and the names of certificates show as
spec v0.12 §29.7 says.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1 Commits (39b2033e3ccf54a91bda8d7e3ced39b26dbfa58c)