This release is a pre-release and may not be stable for production use.
README
Simple python3 library built using only the standard library. This library contains
utility methods for AES/ECB/PKCS5 encryption[to base64] and decryption[from base64].
INSTALLATION
Install aes-ecb-pkcs5 via pip:
$ pip install aes-ecb-pkcs5
AUTHOR
Rishabh Mehta eternal.blizzard23@gmail.com
I forget stuff, this section is for anyone who wants to build the package.
$ python setup.py sdist
$ twine upload dist/*
LICENSE 
This code falls under the MIT license which permits the reuse of the proprietary software provided that all copies of the licensed software include a copy of the MIT License terms and the copyright notice. Go crazy!
1 maintainer
Metadata
1 maintainer
Release files for aes-ecb-pkcs5 0.0.1a0
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 |
|---|---|---|---|---|
| aes-ecb-pkcs5-0.0.1a0.tar.gz | 3.5 kB | Without provenance | Details for aes-ecb-pkcs5-0.0.1a0.tar.gz |
Release files / aes-ecb-pkcs5-0.0.1a0.tar.gz
| Download URL | aes-ecb-pkcs5-0.0.1a0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f076160b3236ee385316a51aa579358e7cd7b600cf31d909f492220f75fac54
|
|
BLAKE2b-256 checksum How to use checksums |
25cb56771b0bb61c18681433a1e1bdfb919c813b120ef6d2bf2ce316632c86bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.4
|
Security for aes-ecb-pkcs5 0.0.1a0
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.
