MultiCrypt
A high-level python API for encryption and cryptographic signing, agnostic of underlying mathematical cryptographic algorithms.
Structure of This Module
This module serves the purpose of providing clear and easy-to-use cryptography tools to programmers. It hides away the complexity of hybrid cryptography while still giving the user the choice between different algorithms and hybridisation protocols.
It provides exactly three pairs of functions to the user:
encrypt&decryptsign&verify_signaturegenerate_keys&verify_key_pair
Each of these functions takes the fundamental cryptographic algorithm family to be used as a parameter.
encrypt and decrypt can additionally take a configuration string specifying additional algorithms and protocols to be used for hybrid encryption.
What This Library Doesn't Implement
- key derivation & exchange protocols: these cryptographic procedures require negotiation between the participants, so I haven't implemented this feature so far to keep this API simple and straight forward to use. I may implement them in the future.
- hashing: this module probably should implement that!
Rationale
The basis of cryptographic operations are mathematical algorithms. New mathematical operations are always being developed with different advantages and disadvantages. These algorithms can be used to perform a range of different cryptographic operations:
- encryption & decryption
- signing and signature verification Often, an algorithm can be used in different ways to perform the same cryptographic operation, for example it could use multiple key lengths.
Often, we compound different algorithms to perform a cryptographic operation, for example plaintext might be encrypted with a symmetric algorithm for efficiency with the key encrypted asymmetrically for security and encoded into the cipher for practicality.
This library aims to abstract away these details as much as possible to provide a clean API that is compatible with many cryptographic algorithms and the alternative options for using them (various key lengths, compounded operations etc.)
Development Status EXPERIMENTAL
This library is subject to breaking changes to improve the API. Feel free to provide feedback (Github issues/discussions).
Can it really be that nobody else hasn't built a library or standards like this before? I searched but maybe I'm not good enough! Please let me know if you do! (Github issues/discussions)
Cryptographic Algorithm Families
In this library, a family of cryptographic algorithms is a collection of different sets of compounded algorithms for performing cryptographic operations that use intercompatible public & private keys because they share the same algorithm for the first layer in their cryptographic stacks.
The operations within a cryptographic family can use all keys generated by the family's generate_keys() function, even if it has the flexibility of receiving user-defined parameters such as variable key length.
Usage
Here is the simplest usage of multi_crypt, without specific encryption and signing options. For details on encryption and signing options, or to learn how to use a purely functional, non-object-oriented approach, see tests/test_multi_crypt.py
from multi_crypt import Crypt
CRYPTO_FAMILY = "EC-secp256k1"
# generate new keys
private_crypt = Crypt.new(CRYPTO_FAMILY)
# load public key for encryption and signature verification
public_key = private_crypt.get_public_key()
public_crypt = Crypt(CRYPTO_FAMILY, public_key=public_key)
# encrypt and decrypt
original_data = b"Hello there!"
encrypted_data = public_crypt.encrypt(original_data)
decrypted_data = private_crypt.decrypt(encrypted_data)
assert decrypted_data == original_data, "Encryption works!"
# sign and verify
data = b"Hello there!"
false_data = b"Hello, World!"
signature = private_crypt.sign(data)
is_verified = public_crypt.verify_signature(signature, data)
false_signature = private_crypt.sign(false_data)
# this verification should return False
is_false_sig_verified = public_crypt.verify_signature(false_signature, data)
assert is_verified and not is_false_sig_verified, "Signing & verification work!"
Metadata
Release files for multi-crypt 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| multi_crypt-0.1.3.tar.gz | 19.4 kB | Without provenance | Details for multi_crypt-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| multi_crypt-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for multi_crypt-0.1.3-py3-none-any.whl |
Total release size: 41.0 kB
Release files / multi_crypt-0.1.3.tar.gz
| Download URL | multi_crypt-0.1.3.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d803af1a7eb781e7cbe70c064988c9306f52d5b30b8097da7d6fd25c820ab6fa
|
|
BLAKE2b-256 checksum How to use checksums |
132dec67d676489c6ad4a83bafd3753dcf99daec8bee31b4f5dacac684401f76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Release files / multi_crypt-0.1.3-py3-none-any.whl
| Download URL | multi_crypt-0.1.3-py3-none-any.whl |
|---|---|
| Size | 21.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf2b756e78d0c7ef1b450dbb5697d2a31f97a36e9864e47b388f064c3a9f5715
|
|
BLAKE2b-256 checksum How to use checksums |
53b903a9da4f5e824e5afe9034bf70182a824ad1e759d5202176c2f6121341a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.3
|
Security for multi-crypt 0.1.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.