File: comment_1_68345d01b016abf96c226d2bfa17c641._comment

package info (click to toggle)
git-annex 7.20190129-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 56,292 kB
  • sloc: haskell: 59,105; sh: 1,255; makefile: 225; perl: 136; ansic: 44
file content (16 lines) | stat: -rw-r--r-- 624 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
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
"""]]