Github crypt
A tool to encrypt things (for humans, primarily of the developer type) using keys that already exist (connected to nearly everyones personal github account to do things like checkout and clone and such).
Warning: not nuke proof, not recommended for extremely secure things so don’t whine if the NSA or other agency/country is still able to break the encryption applied here.
How to use
Copy ghcrypt.ini to ~/.ghcrypt.ini (skip if already done).
Fill in values in ~/.ghcrypt.ini (skip if already done).
Create and install this folder into a virtualenv (skip if already done) or pip install ghcrypt (whichever works for you).
Use $ ghcrypt to send and read things.
Profit!
1 maintainer
Metadata
1 maintainer
Release files for ghcrypt 0.0.9
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 |
|---|---|---|---|---|
| ghcrypt-0.0.9.tar.gz | 5.6 kB | Without provenance | Details for ghcrypt-0.0.9.tar.gz |
Release files / ghcrypt-0.0.9.tar.gz
| Download URL | ghcrypt-0.0.9.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
787eb41a7f29e827d9cebc027febd8f2dcd1f5bf6387b6d4db3032f0871fc279
|
|
BLAKE2b-256 checksum How to use checksums |
5f13c1ef22d08a047d75261b9535cc7f37f5afeba247798ee2b2cdfbd76badac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.6.0 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.6.10
|
Security for ghcrypt 0.0.9
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.
