summaryrefslogtreecommitdiff
path: root/doc/devblog
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-06-05 16:41:49 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-06-05 16:41:49 -0400
commitacdef5be17d1695dac258f795b8a89930a5ad412 (patch)
tree0401ffd4db9389779ce72fc33d66fa59c9d94710 /doc/devblog
parent751d27ea1012332b7ff25bca32ed5950135713d4 (diff)
note about encryption=shared
Diffstat (limited to 'doc/devblog')
-rw-r--r--doc/devblog/day_291__public_S3.mdwn8
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/devblog/day_291__public_S3.mdwn b/doc/devblog/day_291__public_S3.mdwn
index 7d00643a9..35e124042 100644
--- a/doc/devblog/day_291__public_S3.mdwn
+++ b/doc/devblog/day_291__public_S3.mdwn
@@ -4,8 +4,12 @@ without needing any S3 credentials. Read-only of course.
This tip shows how to do it: [[tips/public_Amazon_S3_remote]]
-That will work for at least AWS S3, and for the Internet Archive's S3.
-It may work for other S3 services, that can be configured to publish
+One rather neat way to use this is to configure the remote with
+`encryption=shared`. Then, the files stored in S3 will be encrypted, and
+anyone with access to the git repository can get and decrypt the files.
+
+This feature will work for at least AWS S3, and for the Internet Archive's
+S3. It may work for other S3 services, that can be configured to publish
their files over unauthenticated http. There's a `publicurl` configuration
setting to allow specifying the url when using a service that git-annex
doesn't know the url for.