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

close

Browse source
This commit is contained in:
Joey Hess 2016-10-17 16:36:35 -04:00
parent f07e2ce87c
commit 3a3f126956
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
2 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/Can__39__t_keep_gpg_quiet/comment_1_ab0ffdf17fb5caf8db70b77220878a1b._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-10-17T20:32:02Z"
content="""
The gnupg-options and gnupg-decrypt-options only apply when git-annex
is running gpg, not when git-annex is running git push which is running
git-remote-gcrypt which is running gpg.
I don't think there's any way to pass gpg options through that chain of
programs. Even if there is, I don't know that it would make sense to use
the git-annex configuration, which normally is used when git-annex is using
gpg in symmetric encryption mode, for git-remote-gcrypt, which is using gpg
in pubic key encryption mode.
I think you should just set gcrypt.gpg-args to whatever options are
appropriate for its use of gpg.
"""]]