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

notes

Browse source
This commit is contained in:
Joey Hess 2013-09-17 20:08:44 -04:00
parent 3d88559e58
commit 76421872d1
1 changed files with 16 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/design/assistant/gpgkeys.mdwn
View file

@ -2,7 +2,7 @@ Currently the assistant sets up a shared encryption key, which is checked
into git, so anyone who gets the repository can decrypt files that are
stored encrypted on special remotes.
To support using gpg keys in the assistant, we need two things:
To support using gpg keys in the assistant, we need some things:
1. Help user set up a gpg key if they don't have one. This could be a
special-purpose key dedicated to being used by git-annex. It might be
@ -11,10 +11,23 @@ To support using gpg keys in the assistant, we need two things:
webapp. Indeed, the password prompt is the main problem here.
Best solution would be to get gpg agent working on all supported
platforms.
2. Help user learn the gpg keys of people they want to share their repo
Update: For now, git-annex only assists in generating gpg keys that are
intended to only be used to encrypt a repo.
2. After generating a gpg key, back it up. It might be the only way
some data is accessible.
One way I'm considering is generating a QR code
of the key, which could be printed to paper. Preliminary results
are good; a 4096 bit secret key fits in a QR code (a secret key
with many subkeys may not). Debian has command-line utilities that
can generate and read such a QR code.
3. Help user learn the gpg keys of people they want to share their repo
with, and give them access. If the public key was recorded in the git-annex
branch, this could be easily determined when sharing repositories with
friends. Or, use MonkeySphere..
friends. Or, use MonkeySphere, or Monkeysign..
-----