diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl6rte43qSRK1o2zn7Ww4Z8pgBmJm8gDrc <Rickard@web> | 2015-03-29 20:20:30 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-03-29 20:20:30 +0000 |
| commit | 4fedc889fbbc1a0502648531fa743c46c0ba0148 (patch) | |
| tree | 8afabe6db8cf1236791a3e90c9fed0a1f5e0f6fc | |
| parent | 38fe6e70a0724495199d83a5c8db207ae1388360 (diff) | |
| -rw-r--r-- | doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn b/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn new file mode 100644 index 000000000..af05993d4 --- /dev/null +++ b/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn @@ -0,0 +1,4 @@ +### Feature request +It is not possible to put encrypted content in place on remotes with just a public GPG key. You always need the private key, even for encryption. I guess this is because how the cipher HMAC is used for replacing file names with their hashes. However, if that requirement (having secret file names) was dropped, I assume a pubkey-only mode could be implemented? + +My specific use case is backup archiving. I have my backups packed in archive files and want to use git-annex to copy the archives to offsite remotes (S3). In that case, I don't care much about hiding file names, but would appreciate the increased security of not having the secret key on the backup server. It would only be needed if I wanted to verify or restore backups. |