mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment: A possible solution

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawkbpbjP5j8MqWt_K4NASwv0WvB8T4rQ-pM 2013-11-02 14:22:13 +00:00 committed by admin
parent 0948b07ffc
commit 31ea392b33
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_2_07feedb4348f8c31176cc744c19368a1._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawkbpbjP5j8MqWt_K4NASwv0WvB8T4rQ-pM"
nickname="Fabrice"
subject="A possible solution"
date="2013-11-02T14:22:13Z"
content="""
I'm answering to myself :-). A possible solution to the annoying pass phrase asking with current gnupg is to use a specialized secret keyring. One first exports the secret key used for this repository in a specific keyring as follows:
`gpg --export-secret-keys keyid | gpg --import --no-default-keyring --secret-keyring mygitannexsecret.gpg`
This will create a keyring in $HOME/.gnupg with only the specific key.
Then, in the git-remote-gcrypt shell script, gpg should be called as follows
`gpg --no-default-keyring --secret-keyring mygitannexsecret.gpg -q -d ...`
when decrypting the manifest in order to try only the specific key. This behavior can be easily triggered via some git configuration variable.
Any comment?
"""]]