summaryrefslogtreecommitdiff
path: root/doc/walkthrough
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-04-16 19:30:31 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-04-16 19:35:02 -0400
commitd2e74efdb2e5b819d5c56f167291b006badd94cb (patch)
treee9dea4bcec8519f77b244c0c018b7bec919743cd /doc/walkthrough
parent1247bfeaa7356e766d3ea09fa50bd300650f78af (diff)
document encryption
Diffstat (limited to 'doc/walkthrough')
-rw-r--r--doc/walkthrough/using_Amazon_S3.mdwn12
1 files changed, 7 insertions, 5 deletions
diff --git a/doc/walkthrough/using_Amazon_S3.mdwn b/doc/walkthrough/using_Amazon_S3.mdwn
index b8eb7da53..7f84f2ac2 100644
--- a/doc/walkthrough/using_Amazon_S3.mdwn
+++ b/doc/walkthrough/using_Amazon_S3.mdwn
@@ -2,17 +2,19 @@ git-annex extends git's usual remotes with some [[special_remotes]], that
are not git repositories. This way you can set up a remote using say,
Amazon S3, and use git-annex to transfer files into the cloud.
-**Note that encrypted buckets are not (yet) supported. Data sent to S3
-is without encryption susceptible to snooping.**
-
First, export your S3 credentials:
# export ANNEX_S3_ACCESS_KEY_ID="08TJMT99S3511WOZEP91"
# export ANNEX_S3_SECRET_ACCESS_KEY="s3kr1t"
-Next, create the S3 remote, and describe it.
+Now, create a gpg key, if you don't already have one. This will be used
+to encrypt everything stored in S3, for your privacy. Once you have
+a gpg key, run `gpg --list-secret-keys` to look up its key id, something
+like "2512E3C7"
+
+Next, create the S3 remote, and describe it.
- # git annex initremote mys3 type=S3 encryption=none
+ # git annex initremote mys3 type=S3 encryption=2512E3C7
initremote mys3 (checking bucket) (creating bucket in US) ok
# git annex describe mys3 "at Amazon's US datacenter"
describe mys3 ok