This release is a pre-release and may not be stable for production use.
Swarmauri MRE Crypto Keyring
Multi-recipient encryption provider using external keyrings/HSMs.
Features
- Uses asynchronous keyring clients that implement
id,wrap_cek, andunwrap_cekto delegate CEK storage and policy enforcement to external systems. - Encrypts payloads with AES-256-GCM by default and automatically enables
XChaCha20-Poly1305 when the
cryptographydependency exposes the implementation. - Accepts additional authenticated data (AAD) during encryption and enforces a
configurable quorum (
opts['quorum_k']) before releasing the payload. - Supports
rewrapoperations to add or revoke keyrings and can rotate the payload CEK when deauthorizing recipients. - Requires the
cryptographypackage at runtime, which is installed alongside this provider.
Installation
Install the package with your preferred Python packaging tool:
pip install swarmauri_mre_crypto_keyring
poetry add swarmauri_mre_crypto_keyring
uv pip install swarmauri_mre_crypto_keyring
Usage
KeyringMreCrypto delegates CEK (content-encryption key) management to
user-provided keyring clients. Each client must implement id,
wrap_cek, and unwrap_cek. Key references supplied to the provider should use
the shape {"kind": "keyring_client", "client": <client>, "context": {...}},
where context is an optional mapping of str to bytes shared with the
client during wrapping and unwrapping. The example below registers an in-memory
keyring and uses it to encrypt and decrypt a payload while the default quorum of
1 is satisfied.
import asyncio
import secrets
from swarmauri_mre_crypto_keyring import KeyringMreCrypto
class MemoryKeyring:
def __init__(self):
self._store = {}
def id(self) -> str:
return "memory"
async def wrap_cek(self, cek: bytes, *, context):
token = secrets.token_bytes(8)
self._store[token] = cek
return token
async def unwrap_cek(self, header: bytes, *, context):
return self._store[header]
async def main():
keyring = MemoryKeyring()
keyref = {"kind": "keyring_client", "client": keyring}
crypto = KeyringMreCrypto()
env = await crypto.encrypt_for_many([keyref], b"sensitive data")
recovered = await crypto.open_for(keyref, env)
assert recovered == b"sensitive data"
asyncio.run(main())
The snippet encrypts b"sensitive data" for the memory keyring and
recovers the original plaintext using the same keyring client.
Want to help?
If you want to contribute to swarmauri-sdk, read up on our guidelines for contributing that will help you get started.
Metadata
Release files for swarmauri_mre_crypto_keyring 0.11.0.dev1
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 |
|---|---|---|---|---|
| swarmauri_mre_crypto_keyring-0.11.0.dev1.tar.gz | 10.4 kB | Without provenance | Details for swarmauri_mre_crypto_keyring-0.11.0.dev1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| swarmauri_mre_crypto_keyring-0.11.0.dev1-py3-none-any.whl | Python 3 | none | any | Details for swarmauri_mre_crypto_keyring-0.11.0.dev1-py3-none-any.whl |
Total release size: 22.0 kB
Release files / swarmauri_mre_crypto_keyring-0.11.0.dev1.tar.gz
| Download URL | swarmauri_mre_crypto_keyring-0.11.0.dev1.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d69bc8ccc44263f8bd47801c005eb2088dcce7867d771def322a5efd346956bc
|
|
BLAKE2b-256 checksum How to use checksums |
36d35de168b8c05edee589865a6a5494f84321235f99e5a991b0aa5871400b00
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / swarmauri_mre_crypto_keyring-0.11.0.dev1-py3-none-any.whl
| Download URL | swarmauri_mre_crypto_keyring-0.11.0.dev1-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a3e7f4e8de92459d868c3ba7323fda7143d6ed5e934d5e5b93c8038e888c754
|
|
BLAKE2b-256 checksum How to use checksums |
817557e026479f6996f669793d3750bf3dae0c4c4548a45ec7c7dbe9ab8cdb2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for swarmauri_mre_crypto_keyring 0.11.0.dev1
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.