Git-crypt – transparent file encryption in Git

(agwa.name)

15 points | by yamrzou 15 hours ago

7 comments

  • nikeee 9 minutes ago

    There is also git-agecrypt [1], which is the same but uses age instead of gpg. I've used both, they work pretty well.

    [1]: https://github.com/vlaci/git-agecrypt

  • zaptheimpaler 18 minutes ago

    How does this compare to mozilla's sops[1]. I've heard sops is also used for this kind of usecase, although it seems to do much more.

    [1] https://github.com/getsops/sops

  • siroma 23 minutes ago

    git-crypt is great. I use it on a daily basis to encrypt code of some of my repositories. Some of the software I write contains industry secrets I don't want GitHub to know or train AI with. I don't trust them in keeping my private repos safe, so I use git-crypt. Honestly works way better than I expected initially. Once you configure it it's pretty seamless.

    • FredPret 7 minutes ago

      In your usecase, is a self-rolled Gitea not even more secure and also easier to use?

      Who knows if your trade secrets get decrypted by an AI years from now

  • asymmetric an hour ago

    Is there anything comparable/support for this in jujutsu? The files git-crypt handles are not added to .gitignore — they’re instead added to .gitattributes.

    The result is that jj commits them, which is not what you want.