summaryrefslogtreecommitdiff
path: root/doc/walkthrough/using_Amazon_S3.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-03-28 08:40:05 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-03-28 08:40:05 -0400
commit3bdc5eb29077add9f2de18ba587ca88bb98cb63e (patch)
tree6af319f70484495f2f9f79908bd8b2364ac01fed /doc/walkthrough/using_Amazon_S3.mdwn
parentc532be4c5deacf50659a54960c581a717c3b2f25 (diff)
will need gpg encryption for s3
Diffstat (limited to 'doc/walkthrough/using_Amazon_S3.mdwn')
-rw-r--r--doc/walkthrough/using_Amazon_S3.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/walkthrough/using_Amazon_S3.mdwn b/doc/walkthrough/using_Amazon_S3.mdwn
index cadd78582..8cb77ab6c 100644
--- a/doc/walkthrough/using_Amazon_S3.mdwn
+++ b/doc/walkthrough/using_Amazon_S3.mdwn
@@ -24,4 +24,6 @@ Now the remote can be used like any other remote.
move video/hackity_hack_and_kaxxt.mov (to mys3...) ok
An Amazon S3 remote works just like a ssh remote, except it does not have
-a git repository at the other end, and it costs you money. :)
+a git repository at the other end, and it costs you money. :) In particular,
+all data is stored encrypted with gpg, so neither Amazon nor anyone in
+between can see it.