summaryrefslogtreecommitdiff
path: root/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn')
-rw-r--r--doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn14
1 files changed, 0 insertions, 14 deletions
diff --git a/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn b/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn
deleted file mode 100644
index 2bfc629dd..000000000
--- a/doc/bugs/feature_request:_pubkey-only_encryption_mode.mdwn
+++ /dev/null
@@ -1,14 +0,0 @@
-### 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.