You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a global .gitattributes file and configure the global .gitconfig file to apply a transparent git encryption with smudge and clean filters using GPG.
In the .gitattributes file, set a filter for all *.igloocrypt file extensions. The .gitconfig should include the filter configuration by using gpg for the encryption and decryption, processing files just before they’re checked out and just before they’re staged.
The smudge filter is run on checkout.
The clean filter is run when files are staged.
The described concept is a simplified and cleaner solution instead of adding a using a tool like git-crypt which makes the encryption usage dependent on an external tool and also commit additional files to the repository like the .git-crypt folder in the root of the repository. Such tools are really useful and necessary when the repository is used by many collaborator, but only adds overhead for personal (dotfile) repositories.
1. Deleted the custom `git-diff-igloocrypt` script
2. Removed the custom `[diff "igloocrypt"]` section from the
`gitconfig` file
3. Removed the custom filter "igloocrypt" from the `gitconfig` file
4. Updated the `filter` and `diff` custom global Git attributes handler
for all `*.igloocrypt` files to the new `git-crypt` setup
GH-113
Add a global
.gitattributes
file and configure the global.gitconfig
file to apply a transparent git encryption withsmudge
andclean
filters using GPG.In the
.gitattributes
file, set a filter for all*.igloocrypt
file extensions. The.gitconfig
should include the filter configuration by usinggpg
for the encryption and decryption, processing files just before they’re checked out and just before they’re staged.The described concept is a simplified and cleaner solution instead of adding a using a tool like git-crypt which makes the encryption usage dependent on an external tool and also commit additional files to the repository like the
.git-crypt
folder in the root of the repository. Such tools are really useful and necessary when the repository is used by many collaborator, but only adds overhead for personal (dotfile) repositories.References:
The text was updated successfully, but these errors were encountered: