CRNEN (Cryptographic Robust Nested Encryption)
An advanced multi-layer encryption/decryption system that provides high security by combining AES-256-GCM and ChaCha20.
Features
- Multi-layer encryption (AES-256-GCM + ChaCha20)
- Secure key derivation using PBKDF2
- Message integrity verification using HMAC-SHA512
how to use
install
pip install crnde
use in .py file
import crnde
crnde.encrypt(text,key)
crnde.decrypt(encrypted text,key)
Metadata
Release files for crnde 1.0
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 |
|---|---|---|---|---|
| crnde-1.0.tar.gz | 3.8 kB | Without provenance | Details for crnde-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crnde-1.0-py3-none-any.whl | Python 3 | none | any | Details for crnde-1.0-py3-none-any.whl |
Total release size: 8.0 kB
Release files / crnde-1.0.tar.gz
| Download URL | crnde-1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
795e53fe91c69a0986c8163963edd130c7ecfbe5aed904fe36490557c02284f0
|
|
BLAKE2b-256 checksum How to use checksums |
798c799f61ce20500c495477e41c5f8e119dd81b48bf1c34e1999ff005a8dff7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Release files / crnde-1.0-py3-none-any.whl
| Download URL | crnde-1.0-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d60580c4c2917246652d2af04a3c173653dd8a3027addb4ceacfe917d25ee40
|
|
BLAKE2b-256 checksum How to use checksums |
0a8898080d374dec4461d9c6e4cdf435b7f84f12576a197d102e73e5c5fe9033
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.2
|
Security for crnde 1.0
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.