note about encryption=shared
This commit is contained in:
parent
c7cee80651
commit
80ce678e95
1 changed files with 6 additions and 2 deletions
|
@ -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]]
|
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.
|
One rather neat way to use this is to configure the remote with
|
||||||
It may work for other S3 services, that can be configured to publish
|
`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
|
their files over unauthenticated http. There's a `publicurl` configuration
|
||||||
setting to allow specifying the url when using a service that git-annex
|
setting to allow specifying the url when using a service that git-annex
|
||||||
doesn't know the url for.
|
doesn't know the url for.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue