-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to git-crypt #113
Milestone
Comments
arcticicestudio
added a commit
that referenced
this issue
Sep 8, 2018
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
arcticicestudio
added a commit
that referenced
this issue
Sep 8, 2018
1. Decrypted all `*.igloocrypt` files and backuped them up outside the repository 2. Deleted all `*.igloocrypt` files within the repository GH-113
arcticicestudio
added a commit
that referenced
this issue
Sep 8, 2018
1. Initialized `git-crypt` for the repository: `git-crypt init` (default key) 2. Added the main Arctic Ice Studio GPG key: `git-crypt add-gpg-user -n <ID>` (`-n` flag prevents automatic commit of generated files) GH-113
arcticicestudio
added a commit
that referenced
this issue
Sep 8, 2018
arcticicestudio
added a commit
that referenced
this issue
Sep 8, 2018
1. Unlocked the repository: `git-crypt unlock` 2. Added all backed up `*.igloocrypt` files back into the repository 3. Ensured all `*.igloocrypt` are tracked to be encryped: `git-crypt status` After this commit the encryption can be validated to by locking the repository again: `git-crypt lock` GH-113
Merged
arcticicestudio
added a commit
that referenced
this issue
Apr 5, 2020
…o-git-crypt Migrate to "git-crypt"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #64 (PR #69) a transparent Git encryption was introduced to GPG encrypt specific files using the
smudge
andclean
filters.This approach only worked reasonably well with various problems, e.g. caused files to be flagged as „dirty“ (modified) after checkout even if there have been no changes. The pure Git builtin solution with filters was chosen to prevent dependence to external tools, but the latest release versions of Git causing more and more problems due to changes in the behavior e.g. how
git diff
works (also causingdiff-so-fancy
to be broken).This issue will undo the previous solution and, against contrary to the opinion in #64, migrate the repository to use git-crypt instead. Even if this adds additional files to the repository and adds the external dependency to the tool itself,
git-crypt
is a stable and production proven concept that works safely and allows to really use a transparent encryption.After playing around and testing
git-crypt
locally the resulting migration steps are as follows:git-diff-igloocrypt
script[diff "igloocrypt"]
section from thegitconfig
file"igloocrypt"
from thegitconfig
filefilter
anddiff
custom global Git attributes handler for all*.igloocrypt
files to the newgit-crypt
setup*.igloocrypt
files and backup them up outside the repository*.igloocrypt
files within the repositorygit-crypt
for the repository:git-crypt init
(default key)git-crypt add-gpg-user -n <ID>
(-n
flag prevents automatic commit of generated files).git-crypt
foldergit-crypt unlock
*.igloocrypt
files back into the repository*.igloocrypt
are tracked to be encryped:git-crypt status
*.igloocrypt
filesgit-crypt lock
The text was updated successfully, but these errors were encountered: