Skip to content

Instantly share code, notes, and snippets.

@icy

icy/git-crypt-rekey.sh

Forked from bartv2/git-crypt-rekey.sh
Created May 11, 2020 17:18
Show Gist options
  • Save icy/ec0206b75fcef076852fad17b43871cb to your computer and use it in GitHub Desktop.
Save icy/ec0206b75fcef076852fad17b43871cb to your computer and use it in GitHub Desktop.
Download ZIP
Raw
git-crypt-rekey.sh
#!/bin/bash
# Unlock the directory, we need the unencrypted versions of the files
git crypt unlock
# Re-initialize git crypt, generating a new key
rm .git/git-crypt/keys/default
git crypt init
# Make the key available to the current users
KEY_FILES=`ls .git-crypt/keys/default/0/`
for f in $KEY_FILES; do
gpg -e --always-trust -r ${f%.gpg} < .git/git-crypt/keys/default > .git-crypt/keys/default/0/$f
done
# Re-encrypt the files with the new key
ENCRYPTED_FILES=`git crypt status -e | colrm 1 14`
git rm --cached $ENCRYPTED_FILES
git add $ENCRYPTED_FILES
@icy
Copy link
Author

icy commented Jan 30, 2023

Hi @cfra ,

Thank you for your message, but this is a fork as a backup of the original script https://gist.github.com/bartv2/7e1c127d6af397bc0e4da6d11fb7ea6c and the author takes their credit.

The problem you're facing may be relevant to changes of file paths. Are you sure the file example.txt still does exist. Would you have the same issue when working on a fresh clone of your repository?

I'd suggest you to raise/find the issue from the official page https://github.com/AGWA/git-crypt/issues.

Best luck.

PS: I migrated my repositories to sops (https://github.com/mozilla/sops) which is not perfect, but I don't really need to deal with gpg stuff within the repository ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment