diff options
author | https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo <Justin@web> | 2012-04-28 22:53:38 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2012-04-28 22:53:38 +0000 |
commit | 090d50a7f7741e1b8d69a416563e86739f747a0b (patch) | |
tree | 7c3b7ea70c8cd4eae532dbe71219a9837720b9c8 | |
parent | 76102c1c7541e7b10c3a3fbe242e9856fef955b3 (diff) |
-rw-r--r-- | doc/forum/wishlist:_simpler_gpg_usage.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/wishlist:_simpler_gpg_usage.mdwn b/doc/forum/wishlist:_simpler_gpg_usage.mdwn new file mode 100644 index 000000000..f09f817af --- /dev/null +++ b/doc/forum/wishlist:_simpler_gpg_usage.mdwn @@ -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. |