summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-28 13:49:48 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-28 13:49:48 -0400
commitbd40e0c777ec164a0edbb716f12587acdfcd09e8 (patch)
treecd20308dce6e5c4cf6c61687f090d33ff4bc3c97 /doc
parent3162a724f1bfdc15efadd939a49ba8740d553d69 (diff)
thinko
Diffstat (limited to 'doc')
-rw-r--r--doc/special_remotes/Amazon_S3.mdwn7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/special_remotes/Amazon_S3.mdwn b/doc/special_remotes/Amazon_S3.mdwn
index dce0a9241..67bea3b1c 100644
--- a/doc/special_remotes/Amazon_S3.mdwn
+++ b/doc/special_remotes/Amazon_S3.mdwn
@@ -27,13 +27,14 @@ the data, should be the only clues to what type of data you are storing in
S3.
[[!template id=note text="""
-This scheme was originally developed by Lars Wirzenius at al [for Obnam](http://braawi.org/obnam/encryption/).
+This scheme was originally developed by Lars Wirzenius at al
+[for Obnam](http://braawi.org/obnam/encryption/).
"""]]
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 public
+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 public keys without
+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.