pairid 0.0.0a0
Library of cryptographic key generation and data preparation procedures associated with the PAIR protocol.
License: MIT
Requires Python: >=3.11

======
pairid
======

Library of cryptographic key generation and data preparation procedures associated with the PAIR protocol.

|pypi| |readthedocs| |actions| |coveralls|

.. |pypi| image:: https://badge.fury.io/py/pairid.svg#
   :target: https://badge.fury.io/py/pairid
   :alt: PyPI version and link.

.. |readthedocs| image:: https://readthedocs.org/projects/pairid/badge/?version=latest
   :target: https://pairid.readthedocs.io/en/latest/?badge=latest
   :alt: Read the Docs documentation status.

.. |actions| image:: https://github.com/choosek/pairid/workflows/lint-test-cover-docs/badge.svg#
   :target: https://github.com/choosek/pairid/actions/workflows/lint-test-cover-docs.yml
   :alt: GitHub Actions status.

.. |coveralls| image:: https://coveralls.io/repos/github/choosek/pairid/badge.svg?branch=main
   :target: https://coveralls.io/github/choosek/pairid?branch=main
   :alt: Coveralls test coverage summary.

Purpose
-------
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 <https://iabtechlab.com/pair/>`__. The commutative encryption and decryption functions are realized using `Curve25519 <https://cr.yp.to/ecdh.html>`__ and the `Ristretto <https://ristretto.group>`__ group (via a dependency on the `libsodium <https://github.com/jedisct1/libsodium>`__ and `ge25519 <https://pypi.org/project/ge25519/>`__ libraries).

Installation and Usage
----------------------
This library is available as a `package on PyPI <https://pypi.org/project/pairid>`__:

.. code-block:: bash

    python -m pip install pairid

The library can be imported in the usual ways:

.. code-block:: python

    import pairid
    from pairid import *

Examples
^^^^^^^^
This library makes it possible to perform the key generation, data salting, encryption, and decryption steps that are required for the PAIR protocol.

.. code-block:: python

    >>> ks = key_salt()
    >>> ka = key_commutative()
    >>> kb = key_commutative()
    >>> ciphertext_s = salt(ks, 'alice@example.com')
    >>> ciphertext_sa = encrypt(ka, ciphertext_s)
    >>> ciphertext_sab = encrypt(kb, ciphertext_sa)
    >>> decrypt(ka, ciphertext_sab) == encrypt(kb, ciphertext_s)
    True

Development
-----------
All installation and development dependencies are fully specified in ``pyproject.toml``. The ``project.optional-dependencies`` object is used to `specify optional requirements <https://peps.python.org/pep-0621>`__ for various development tasks. This makes it possible to specify additional options (such as ``docs``, ``lint``, and so on) when performing installation using `pip <https://pypi.org/project/pip>`__:

.. code-block:: bash

    python -m pip install ".[docs,lint]"

Documentation
^^^^^^^^^^^^^
The documentation can be generated automatically from the source files using `Sphinx <https://www.sphinx-doc.org>`__:

.. code-block:: bash

    python -m pip install ".[docs]"
    cd docs
    sphinx-apidoc -f -E --templatedir=_templates -o _source .. && make html

Testing and Conventions
^^^^^^^^^^^^^^^^^^^^^^^
All unit tests are executed and their coverage is measured when using `pytest <https://docs.pytest.org>`__ (see the ``pyproject.toml`` file for configuration details):

.. code-block:: bash

    python -m pip install ".[test]"
    python -m pytest

Alternatively, all unit tests are included in the module itself and can be executed using `doctest <https://docs.python.org/3/library/doctest.html>`__:

.. code-block:: bash

    python src/pairid/pairid.py -v

Style conventions are enforced using `Pylint <https://pylint.readthedocs.io>`__:

.. code-block:: bash

    python -m pip install ".[lint]"
    python -m pylint src/pairid

Versioning
^^^^^^^^^^
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 <https://semver.org/#semantic-versioning-200>`__.

Publishing
^^^^^^^^^^
This library can be published as a `package on PyPI <https://pypi.org/project/pairid>`__ 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 <https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/>`__.

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 <https://docs.readthedocs.io/en/stable/automation-rules.html>`__ 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):

.. code-block:: bash

    git tag ?.?.?
    git push origin ?.?.?