Library of cryptographic key generation and data preparation procedures associated with the PAIR protocol.
This library provides a Python interface for the cryptographic operations necessary to conduct the workflows that are described within the Publisher Advertiser Identity Reconciliation (PAIR) protocol. The commutative encryption and decryption functions are realized using Curve25519 and the Ristretto group (via a dependency on the libsodium and ge25519 libraries).
This library is available as a package on PyPI:
python -m pip install pairid
The library can be imported in the usual ways:
import pairid
from pairid import *
This library makes it possible to perform the key generation, data salting, encryption, and decryption steps that are required for the PAIR protocol.
>>> ks = key_salt()
>>> ka = key_commutative()
>>> kb = key_commutative()
>>> ciphertext_s = salt(ks, '[email protected]')
>>> ciphertext_sa = encrypt(ka, ciphertext_s)
>>> ciphertext_sab = encrypt(kb, ciphertext_sa)
>>> decrypt(ka, ciphertext_sab) == encrypt(kb, ciphertext_s)
True
All installation and development dependencies are fully specified in pyproject.toml
. The project.optional-dependencies
object is used to specify optional requirements for various development tasks. This makes it possible to specify additional options (such as docs
, lint
, and so on) when performing installation using pip:
python -m pip install ".[docs,lint]"
The documentation can be generated automatically from the source files using Sphinx:
python -m pip install ".[docs]"
cd docs
sphinx-apidoc -f -E --templatedir=_templates -o _source .. && make html
All unit tests are executed and their coverage is measured when using pytest (see the pyproject.toml
file for configuration details):
python -m pip install ".[test]"
python -m pytest
Alternatively, all unit tests are included in the module itself and can be executed using doctest:
python src/pairid/pairid.py -v
Style conventions are enforced using Pylint:
python -m pip install ".[lint]"
python -m pylint src/pairid
The version number format for this library and the changes to the library associated with version number increments conform with Semantic Versioning 2.0.0.
This library can be published as a package on PyPI via the GitHub Actions workflow found in .github/workflows/build-publish-sign-release.yml
that follows the recommendations found in the Python Packaging User Guide.
Ensure that the correct version number appears in pyproject.toml
, and that any links in this README document to the Read the Docs documentation of this package (or its dependencies) have appropriate version numbers. Also ensure that the Read the Docs project for this library has an automation rule that activates and sets as the default all tagged versions.
To publish the package, create and push a tag for the version being published (replacing ?.?.?
with the version number):
git tag ?.?.?
git push origin ?.?.?