What good approach to PGP version control encrypted text files?
The goal is to
they store only PGP text files encrypted (preferably with ASCII) somewhere in the local repository (working copy) and in the remote repository (the "central" repository is logical).
maintain confidentiality enabled using PGP encryption (for example, using GnuPG) in the repositories in which the history of changes will be stored
when possible, reduce storage overhead
If only the revision manages the encrypted and protected PGP and ASCII text file, since all of its content will change each time it is decrypted for editing and then encrypted before it is saved and transferred to the version control repository, diff will be approximately proportional to file size, and will grow rapidly, even if the change in the decrypted text is small.
source
share