https://github.com/randombit/crypto-corpus

Corpus of crypto formats
https://github.com/randombit/crypto-corpus

cryptography fuzzing

Last synced: 3 months ago
JSON representation

Corpus of crypto formats

• Host: GitHub
• URL: https://github.com/randombit/crypto-corpus
• Owner: randombit
• Created: 2016-12-17T01:37:09.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2022-12-02T13:42:03.000Z (about 2 years ago)
• Last Synced: 2023-03-17T22:45:27.599Z (almost 2 years ago)
• Topics: cryptography, fuzzing
• Language: Python
• Size: 6.37 MB
• Stars: 13
• Watchers: 5
• Forks: 3
• Open Issues: 0
• Metadata Files:
  • Readme: README.MD

Awesome Lists containing this project

README

        

Corpus of data for fuzzing crypto parsers of various kinds.

* asn1: ASN.1 data of all kinds, BER encoded

* cert: X.509 certificates, BER encoded

* crl: X.509 CRLs, BER encoded

* ocsp: OCSP responses, BER encoded

* pkcs1: PKCS v1.5 encryption padding

* pkcs8: PKCS #8 private keys, BER encoded

* spki: X.509 subjectPublicKeyInfo structs, BER encoded

* tls_client: TLS server flows (ie, testing a client)

* tls_server: TLS client flows (ie, testing server)

* x509_dn: X.509 DistinguishedNames

* x509_path: A sequence of X.509 certificates (all BER encoded)

  which may or may not be a valid path

All files should be named by their lowercase hex SHA-1 hash

of their contents. This allows easy deduplication.

The initial version is seeded from corpus data from BoringSSL and

OpenSSL, some reference inputs, plus corpus data generated by OSS-Fuzz

while running the Botan fuzzers.

PRs to add new corpus values will be accepted.

The goal is that any datums have a well defined format that can be

shared to test among multiple implementations. So corpus for modexp

and similar mathematical functions are not included yet, but should be.