3 ms·
To solve this problem, I wrote git-crypt[1], which uses git's smudge/clean filters to transparently encrypt/decrypt files when you check them in/out. So it's a
by agwa 14y ago
To solve this problem, I wrote git-crypt[1], which uses git's smudge/clean filters to transparently encrypt/decrypt files when you check them in/out. So it's a lot like this solution except you don't need the manual makefile steps. As an added bonus, git diff/blame still work on the encrypted file.
[1] https://github.com/AGWA/git-crypt https://github.com/AGWA/git-crypt and http://www.agwa.name/projects/git-crypt/ http://www.agwa.name/projects/git-crypt/
- jeresig 14y agogit-crypt is incredibly cool - great work!
- agwa 14y agoThanks!
- raverbashing 14y agoMakes me wonder the overhead of keeping a history which consists of n copies of the files instead of a delta (or the diff is done on the plaintext and then encrypted?)
- Mvandenbergh 14y agogit-crypt is only used on the sensitive files in the repository and only those with the key are going to be changing those files anyway.
- agwa 14y agoRight. If you need to encrypt an entire repo I don't recommend using git-crypt - there are probably better ways. But for most cases where you'd use git-crypt the overhead isn't that much.