summaryrefslogtreecommitdiff
path: root/doc/special_remotes/S3
diff options
context:
space:
mode:
authorGravatar basak <basak@web>2013-05-24 09:38:40 +0000
committerGravatar admin <admin@branchable.com>2013-05-24 09:38:40 +0000
commit303b4b4801a97975d02d4a193041e1a9b6af1248 (patch)
treef4009d5541213ddeab3d51db9aadfd0c419ee373 /doc/special_remotes/S3
parentc7d3d206460679a3e11477af0d0015fa4275a06c (diff)
Added a comment
Diffstat (limited to 'doc/special_remotes/S3')
-rw-r--r--doc/special_remotes/S3/comment_11_c1da387e082d91feec13dde91ccb111a._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/special_remotes/S3/comment_11_c1da387e082d91feec13dde91ccb111a._comment b/doc/special_remotes/S3/comment_11_c1da387e082d91feec13dde91ccb111a._comment
new file mode 100644
index 000000000..5cd9b7311
--- /dev/null
+++ b/doc/special_remotes/S3/comment_11_c1da387e082d91feec13dde91ccb111a._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="basak"
+ ip="2001:8b0:1c8::2"
+ subject="comment 11"
+ date="2013-05-24T09:38:40Z"
+ content="""
+Thanks Joey - initremote on my slightly older version appears to work. I'll use `enableremote` when I can.
+
+> (Just in case, I have verified that embedcreds does cause the cipher= to be stored in the remote.log. It does.)
+
+This doesn't do what I expect. The documentation suggests that my S3 _login_ credentials would be stored. I understand that the cipher would be stored; but isn't this a separate concept? Instead, I'm being asked to set `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`; my understanding was that git-annex will keep them in the repository for me, so that I don't have to set them after running `initremote` before cloning. This works, apart from surviving the cloning. I'm using `encryption=shared`; does this affect anything? Or am I using a version of git-annex (3.20121112ubuntu3) that's too old?
+"""]]