aboutsummaryrefslogtreecommitdiff
path: root/doc/special_remotes
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-28 16:35:59 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-28 16:35:59 -0400
commitcaef7c82213e00695679bd9c934a4edef0a04eaa (patch)
tree3c2f93c69ec39c49127c2ed6c83a6e8e1bb0fbcf /doc/special_remotes
parent996e5eee01c83e6a95b51ac10ed5d2b39616d092 (diff)
nix on revocation
Diffstat (limited to 'doc/special_remotes')
-rw-r--r--doc/special_remotes/Amazon_S3.mdwn6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/special_remotes/Amazon_S3.mdwn b/doc/special_remotes/Amazon_S3.mdwn
index 67bea3b1c..ae3990a76 100644
--- a/doc/special_remotes/Amazon_S3.mdwn
+++ b/doc/special_remotes/Amazon_S3.mdwn
@@ -34,10 +34,8 @@ The data stored in S3 is encrypted by gpg with a symmetric cipher. The
passphrase of the cipher is itself checked into your git repository,
encrypted using one or more gpg public keys. This scheme allows new private
keys to be given access to a bucket's content, after the bucket is created
-and is in use. It also allows revoking compromised private keys without
-having to throw out the contents of the bucket. The symmetric cipher
-is also hashed together with filenames used in the bucket, obfuscate
-the filenames.
+and is in use. The symmetric cipher is also hashed together with filenames
+used in the bucket, in order to obfuscate the filenames.
To add a new gpg key to an existing bucket, just re-run `git annex
s3bucket`, specifying the new key id. For example: