chore: unpin envelope_crypto dependency (track latest release)
envauth used envelope_crypto pinned at v0.1.0, two data-loss fixes behind (the lib is now v0.1.4). envauth uses only stable crypto primitives (initialize, encrypt_data/ decrypt_data, create_aes_key, *_aes_key_with_rsa, get_rsa_key_fingerprint, self_test) — never the record-rotation functions whose contract changed — so tracking latest is safe and keeps the crypto fixes flowing without a manual bump each release. Verified: full CLI round-trip (init -> authorize server -> privilege gate -> envauth-1 self-authorize refusal -> list) against envelope_crypto v0.1.4 source; all 8 used primitives present. v0.1.4. Signed-off-by: disqualifier <dev@disqualifier.me>
This commit is contained in:
+2
-2
@@ -4,11 +4,11 @@ build-backend = "hatchling.build"
|
||||
|
||||
[project]
|
||||
name = "envelope_authorizer"
|
||||
version = "0.1.3"
|
||||
version = "0.1.4"
|
||||
description = "CLI key-authorization manager for envelope_crypto"
|
||||
requires-python = ">=3.10"
|
||||
dependencies = [
|
||||
"envelope_crypto @ git+ssh://git@git.rethinkstudios.io/rethink-public/envelope_crypto.git@v0.1.0",
|
||||
"envelope_crypto @ git+ssh://git@git.rethinkstudios.io/rethink-public/envelope_crypto.git",
|
||||
"tomli>=2.0; python_version<'3.11'",
|
||||
]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user