AES encrypted ZIP files and Tombo CHI encryption file support #156
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Requires:
python -m pip install pycryptodome
# And https://github.com/clach04/chi_io
Read and write works for a demo, assuming hard coded (debug) password
lookup mechanism (not suitable for real use).
Internal filename in zip is encrypted.md File extension is .aes.zip or .aes256.zip
Contributor
Author
|
The aim of this PR is to start a conversation. In the unlikely event that it is merged as-is, I recommend squashing and merging. |
Owner
|
This change is too big. Would you mind if you divide this into smaller PRs which are solving just one thing. Thanks for the support and help! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements a proof of concept to allow reading and writing of encrypted files (#99).
Missing is a way to set (and unset) password, this demo picks up the password from the operating system environment variable
DEBUG_CRYPTO_KEY(and if missing defaults to "test").Also there is no error reporting to the client on bad passwords, there is currently no reporting to the client for any error (see #152)
The change also includes workarounds (or solutions) for:
I have no idea how to tackle: