choppy
chop -> encrypt -> (?) -> decrypt -> merge
Choppy partitions files and encrypts using symmetric authenticated cryptography. After decryption, embedded metadata provides for the original input file to be recreated and verified.
selectable number of partitions and randomized file size
secure cryptographic key/password input or via file
sequential numeric or randomized file names
encrypted file chunks can have name and extension altered with no detriment to recreating input file
chunks from multiple files can be located within the same directory and the merge command will locate and reassemble original input files
Installation
Using pip:
pip install choppy
Without pip - clone repository:
python setup.py install
Command Line Usage
See Usage for advanced use and expanded options.
generate cryptographic key file (key.txt)
choppy gen -k
create 10 partitions of infile.txt, randomize partition size by 50% and encrypt with key file
choppy chop infile.txt -n 10 -w 50 --use-key -i key.txt
decrypt partitions and merge to reassemble original file
choppy merge *.chp.* --use-key -i key.txt
Requirements
Python 3.6 or greater
cryptography 2.1.3
License
choppy is released under the BSD 2-clause license. See LICENSE for details.
1 maintainer
Metadata
1 maintainer
Release files for choppy 0.0.5
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 |
|---|---|---|---|---|
| choppy-0.0.5.tar.gz | 16.0 kB | Without provenance | Details for choppy-0.0.5.tar.gz |
Release files / choppy-0.0.5.tar.gz
| Download URL | choppy-0.0.5.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98956aa6944efc24826ce65ab9c17d0d99b033e99e4d6cef7c81267bcc0a4e1b
|
|
BLAKE2b-256 checksum How to use checksums |
7b7aca27fdfd842282edb1ca8e889da5969e069d4bd9c8fed761d99c183713e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for choppy 0.0.5
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.
