diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-01-05 16:37:08 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-01-05 16:37:08 -0400 |
| commit | 764dd3fdf7b1e7b951407f56bd7ddc9b1d4315a2 (patch) | |
| tree | 00d715e1845de43bb52c406861ec2e27982ec6b9 | |
| parent | 1e933d6a4ffa299d50d221fb1d1fcabfb18f3ab4 (diff) | |
comment
| -rw-r--r-- | doc/forum/s3_server_side_encryption/comment_1_68345d01b016abf96c226d2bfa17c641._comment | 16 |
1 files changed, 16 insertions, 0 deletions
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 000000000..1dbf60047 --- /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 +"""]] |