Skip to main content

crypto-condor

The logo of crypto-condor, depicting a condor holding a key.

crypto-condor is a tool for compliance testing of cryptographic primitives, in the form of a Python library and CLI. It is complemented by an extensive documentation, featuring guides on the primitives supported.

Q: What is a cryptographic primitive?

A: A low-level cryptographic algorithm, generally used to build a protocol. For example, AES is an encryption primitive that is used in the TLS protocol, which is the protocol your browser used to securely get this page.

Q: What is compliance testing?

A: Algorithms are described in specifications, such as FIPS publications or RFCs. When implementing these algorithms, we want to ensure that they comply with the specification, i.e. the implementation behaves as the algorithm described.

Q: How to test for compliance then?

A: We can use test vectors, which are sets of inputs and their corresponding outputs. For example, encrypting with AES is a deterministic operation: for a given key and message, AES will always return the same ciphertext. So we can choose some input values, run the algorithm, and record the value returned. All implementations of AES are then expected to return the same ciphertext for this given key and message. If it does not, then it is not compliant.

Q: And so, what does crypto-condor do?

A: crypto-condor provides both a nice Python API and a wrapper system to test implementations with sets of test vectors that come from sources such as the NIST CAVP.

The Python API exposes test functions that take an implementation as input, in the form of a Python function or class, passes the inputs defined by the test vectors to that implementation, and checks if the outputs are those defined by the vectors.

The wrappers are small programs that already define the function prototype. The user calls the implementation to test inside this function, and crypto-condor runs it with the test vectors as with the Python API.

And it comes with a documentation, wrapper examples, and guides on supported primitives.

Requirements

crypto-condor requires Python 3.10+. For information, it is developed using Python 3.13 on Fedora 41.

The implementations of AES, ML-KEM, ML-DSA, and TestU01 are written in C and are compiled directly on the user's machine. As such, they require a C compiler (by default GCC on Linux and Clang on MacOS) and GNU Make. These primitives are only compiled when required, and not when installing the package:

  • AES: when testing the output of an implementation using classic modes of operation (not CCM or GCM).
  • ML-KEM: when testing the output of an implementation or when using test vectors on the encapsulate function.
  • ML-DSA: when testing the output of an implementation.
  • TestU01: when used to test a file.

The compiler can be chosen by setting the CC environment variable on Linux. On MacOS, only Clang has been confirmed to work.

Installation

It is available on PyPI:

python -m pip install crypto-condor

An up-to-date list of the requirements can be found in the [tool.poetry.dependencies] section of the pyproject.toml file.

Usage

The documentation is available at https://quarkslab.github.io/crypto-condor/latest/index.html.

Once installed, the CLI is available as crypto-condor-cli. It is structured in commands, similar to Git. Run it without arguments or with --help to display the help message detailing the available subcommands. You can check the documentation for a quick rundown of all the commands.

As for the Python library, it is available as crypto_condor (note the underscore). Each primitive has its own module under primitives, e.g. crypto_condor.primitives.AES. It contains the functions used to test implementations.

Development

See CONTRIBUTING.

Changelog and versioning

A changelog is available. This projects adheres to CalVer. The format used is YYYY.MM.DD[.MICRO][-MODIFIER]:

  • YYYY: full year (2023).
  • 0M: zero-padded month (01, 02, ..., 12).
  • 0D: zero-padded day (01, 02, ..., 31).
  • MICRO: an increasing counter, used for patches published in the same day.
  • MODIFIER: usually rc<n> to indicate a release candidate.

Authors

  • Julio Loayza Meneses, Quarkslab.
  • Angèle Bossuat, Quarkslab.
  • Dahmun Goudarzi, Quarkslab.

Logo idea by Robin David, drawing by Irene Loayza.

License

Apache License Version 2.0, see LICENSE.

Metadata

Release files for crypto-condor 2025.9.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for crypto-condor 2025.9.8
File Size Uploaded Provenance Actions
crypto_condor-2025.9.8.tar.gz 59.3 MB With provenance Details for crypto_condor-2025.9.8.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for crypto-condor 2025.9.8
File Interpreter ABI Platform Actions
crypto_condor-2025.9.8-py3-none-any.whl Python 3 none any Details for crypto_condor-2025.9.8-py3-none-any.whl

Total release size: 119.2 MB

Release files / crypto_condor-2025.9.8.tar.gz

Download URL crypto_condor-2025.9.8.tar.gz
Size 59.3 MB
Tags Source
SHA-256 checksum
How to use checksums
07e0932690d73868157941d204ac562b31c641c02d7604145b5c3e355ab85e55
BLAKE2b-256 checksum
How to use checksums
940e9f26c06e1f8941d90dc935be2d0bb65ca9e2b96a0b79d9599d085a377f19
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2025.

Transparency log

Release files / crypto_condor-2025.9.8-py3-none-any.whl

Download URL crypto_condor-2025.9.8-py3-none-any.whl
Size 59.9 MB
Tags Python 3
SHA-256 checksum
How to use checksums
0cac72d6861964c7d14bcc5e69ac01d7466de4e21bdd79a08997c2317b2b0899
BLAKE2b-256 checksum
How to use checksums
2d5c09764876725cf3b3394c12936a2c6dd7bbb2f998f5b5e1b144471edfc85c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2025.

Transparency log

Security for crypto-condor 2025.9.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for crypto_condor-2025.9.8.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2025.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2025.9.8 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page