From d0a4c99daa6c0e0cc6be88cbc4a2b4df7b94db8f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Jan 2015 16:37:08 -0400 Subject: [PATCH] comment --- ...t_1_68345d01b016abf96c226d2bfa17c641._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/s3_server_side_encryption/comment_1_68345d01b016abf96c226d2bfa17c641._comment diff --git a/doc/forum/s3_server_side_encryption/comment_1_68345d01b016abf96c226d2bfa17c641._comment b/doc/forum/s3_server_side_encryption/comment_1_68345d01b016abf96c226d2bfa17c641._comment new file mode 100644 index 0000000000..1dbf60047d --- /dev/null +++ b/doc/forum/s3_server_side_encryption/comment_1_68345d01b016abf96c226d2bfa17c641._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-01-05T20:33:13Z" + content=""" +I have not looked into this particular S3 feature, since I see little point +in using it. git-annex can encrypt files client-side before sending to S3, +which is much better. + +However, you can probably configure git-annex to send the header. +See the `x-amx-meta-*` option documented in [[special_remotes/S3]]. +If the header was named encryptplz and needed to be set to +"canhazsecurityburger", you would enable it with something like: + + git annex enableremote mys3remote x-amz-meta-encryptplz=canhazsecurityburger +"""]]