From c6f41490a8dc379008c63716d178bda9eef15c17 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 5 Jun 2015 16:43:03 -0400 Subject: [PATCH] improve --- doc/tips/public_Amazon_S3_remote.mdwn | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/doc/tips/public_Amazon_S3_remote.mdwn b/doc/tips/public_Amazon_S3_remote.mdwn index 0140445c42..a1fb7f6f22 100644 --- a/doc/tips/public_Amazon_S3_remote.mdwn +++ b/doc/tips/public_Amazon_S3_remote.mdwn @@ -17,12 +17,16 @@ Now, create the remote: # git annex initremote pubs3 type=S3 encryption=none public=yes initremote pubs3 (checking bucket) (creating bucket in US) ok -In the above example, no encryption was used, but it will also work -if you enable eg, encryption=shared. It's also ok to enable chunking. - The public=yes is the crtical part; this lets the public read the contents of the bucket. +In the above example, no encryption was used, but it will also work +if you enable encryption=shared. Then files will be encrypted on S3, and +anyone with a clone of the git repository will be able to download and +decrypt them. + +It's also ok to enable chunking when setting up the remote. + Now, copy some files to the remote, in the usual way, and push your git repository to someplace where someone else can access it.