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

initremote, enableremote: Support gpg subkeys suffixed with an exclamation mark, which forces gpg to use a specific subkey.

Browse source 
This commit was sponsored by Peter Hogg on Patreon.
This commit is contained in:
Joey Hess 2017-05-24 14:08:02 -04:00
parent dd65ea52c3
commit 35465b6062
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 29 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/encryption/comment_10_6416ee43ffad1c306ef71247ae71a6c5._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 10"""
date="2017-05-24T17:47:46Z"
content="""
@Yurt, git-annex will let you specify the gpg key id using anything that gpg
accepts, including a keyid with a appended '!'. However, when I tried that,
gpg seemed to still pick the master key instead of the subkey. That
happens because git-annex runs the input through `gpg --list-public-keys`
(in order to convert eg, email addresses to key ids)
which always lists the master key even when given a subkey.
I made a small change to git-annex to special case this '!' suffix
behavior. Seems to work in my very limited testing.
Please file bug reports about this kind of thing!
"""]]