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

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo 2012-04-28 22:53:38 +00:00 committed by admin
parent 76102c1c75
commit 090d50a7f7
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/forum/wishlist:_simpler_gpg_usage.mdwn Normal file
View file

@ -0,0 +1,10 @@
This is my current understanding on how one must use gpg with git-annex:
* Generate(or copy around) a gpg key on every machine that needs to access the encrypted remote.
* git annex initremote myremote encryption=KEY for each key that you generated
What I'm trying to figure out is if I can generate a no-passphrase gpg key and commit it to the repository, and have git-annex use that. That way any new clones of the annex automatically have access to any encrypted remotes, without having to do any key management.
I think I can generate a no-passphrase key, but then I still have to manually copy it around to each machine.
I'm not a huge gpg user so part of this is me wanting to avoid having to manage and keeping track of the keys. This would probably be a non-issue if I used gpg on more machines and was more comfortable with it.