mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
michalrus 2017-02-25 18:47:36 +00:00 committed by admin
parent d512098cbb
commit 5fb21f1260
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/bugs/S3_remote___8212___un-embedding_creds__63__/comment_2_282aaaed5e95e8062460f94ac3a68dea._comment Normal file
View file

@ -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. =)
"""]]