diff options
| author |  michalrus <michalrus@web> | 2017-02-25 18:47:36 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-02-25 18:47:36 +0000 |
| commit | e0626c5073602c48517a282c9f3e14039d7d8816 (patch) | |
| tree | e3a4f38365171aeaa3d263f03a8ad4c727b837f0 | |
| parent | ccc48ffc68eaa8c052a382899c1ceb536b447db7 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/S3_remote___8212___un-embedding_creds__63__/comment_2_282aaaed5e95e8062460f94ac3a68dea._comment | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/S3_remote___8212___un-embedding_creds__63__/comment_2_282aaaed5e95e8062460f94ac3a68dea._comment b/doc/bugs/S3_remote___8212___un-embedding_creds__63__/comment_2_282aaaed5e95e8062460f94ac3a68dea._comment new file mode 100644 index 000000000..9c2e141f3 --- /dev/null +++ b/doc/bugs/S3_remote___8212___un-embedding_creds__63__/comment_2_282aaaed5e95e8062460f94ac3a68dea._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="michalrus" + avatar="http://cdn.libravatar.org/avatar/83c0b6e7f9d20f09a892263c4903bbae" + subject="comment 2" + date="2017-02-25T18:47:35Z" + content=""" +Sure, that’s what I did at the very beginning (revoking the creds on AWS). + +But still, when I clone this repo, `git annex info S3` in this fresh clone, says that credentials are embedded. This is a bit misleading. + +Maybe updating S3 configuration with `embedcreds=no` could change that behavior? + +It wouldn’t matter from the security standpoint (which is solved by changing permissions directly on AWS), but would simply be beneficial for usability. =) +"""]] |