GPG encrypt exported archives #1287
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I am always uncomfortable when imaging how exported files of user data might be handled, so it feels responsible to GPG encrypt them with a strong password.
As it's a one-off export/import I made it using symmetric encryption mode (using
AES256), and it generates a 60 character random password (passphrase...).The idea is the person would transfer the file somehow, and transfer the password via a different means so they are not together, then the exported archive file is not readable by anyone without the password.
Default export filename is
export.tar.xz.gpgand you can unpack the archive using standard tools, e.g.:The tests cover the whole export/encryption/import, so all is good!