diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-03-31 15:46:00 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-03-31 15:46:00 -0400 |
| commit | 0f8852dd24f1043bc49f44c2e99386e43642af4e (patch) | |
| tree | cf4e58392464c8463752fbb0e8d776a4a82ce5fb /doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn | |
| parent | bbdd35fffadc8c441278a229c5819b619471b46f (diff) | |
close with comment
Diffstat (limited to 'doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn')
| -rw-r--r-- | doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn | 2 |
1 files changed, 2 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 index af05993d4..ff2fe7fae 100644 --- a/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn +++ b/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn @@ -2,3 +2,5 @@ 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. + +> [[closed|done]] per my comment --[[Joey]] |