From fe97b6773baafe1fb9271d9e38fad4a96444f24b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Jan 2015 17:11:08 -0400 Subject: comment --- .../comment_3_3eb57b98e4136b8550ea5d19393fe967._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/s3_server_side_encryption/comment_3_3eb57b98e4136b8550ea5d19393fe967._comment (limited to 'doc') diff --git a/doc/forum/s3_server_side_encryption/comment_3_3eb57b98e4136b8550ea5d19393fe967._comment b/doc/forum/s3_server_side_encryption/comment_3_3eb57b98e4136b8550ea5d19393fe967._comment new file mode 100644 index 000000000..cee29d877 --- /dev/null +++ b/doc/forum/s3_server_side_encryption/comment_3_3eb57b98e4136b8550ea5d19393fe967._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-01-05T21:09:47Z" + content=""" +Using git-annex's encryption=shared will have the same +key management ease as letting Amazon encrypt. + +In both cases you're putting the shared encryption key into the +configuration of a git-annex S3 remote. Anyone who can access the git +repository can access the encryption key. +"""]] -- cgit v1.2.3