Omniblack Secret
Classes for safer handling of secrets. We use libsodium to store secrets in memory that is protected by guard pages, a canary, and is set to readonly when the library is not reading from it. These protections should help mitigate exploits in other parts of the program allow for arbitrary reads of memory, and should reduce the risk of buffer overflows and similar memory writing bugs from corrupting the secret.
Further more Secret instance's repr will not reveal the secret
so if a secret object is accidentally logged the secret value
will not be exposed, and the value is stored in a C slot not
in a python dict or slot so introspection tools like rich.inspect
will not reveal the secret.
1 maintainer
Metadata
1 maintainer
Release files for omniblack.secret 0.0.14
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 |
|---|---|---|---|---|
| omniblack_secret-0.0.14.tar.gz | 9.2 kB | Without provenance | Details for omniblack_secret-0.0.14.tar.gz |
Release files / omniblack_secret-0.0.14.tar.gz
| Download URL | omniblack_secret-0.0.14.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd88bb917db74c4d49958dc2fc370c4db28a4ec17c459414e2a4f60f7dba6fb9
|
|
BLAKE2b-256 checksum How to use checksums |
9ac6abdd9e6c5dcbf72b422f715e5434cbb861cf102a3023581319129c6911e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for omniblack.secret 0.0.14
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.
