comment and close; bug reporter is using old version and is also mistaken about how S3 security works
This commit is contained in:
parent
c30414a5aa
commit
092eef5894
2 changed files with 18 additions and 0 deletions
|
@ -27,3 +27,5 @@ I tried to persuade `git annex` to use a SSL connection but without encouraging
|
||||||
Debian wheezy, git-annex version: 5.20141024~bpo70+1
|
Debian wheezy, git-annex version: 5.20141024~bpo70+1
|
||||||
|
|
||||||
### Please provide any additional information below.
|
### Please provide any additional information below.
|
||||||
|
|
||||||
|
> [[done]]; port=443 supported since 5.20141203. --[[Joey]]
|
||||||
|
|
|
@ -0,0 +1,16 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 2"""
|
||||||
|
date="2015-02-04T18:55:50Z"
|
||||||
|
content="""
|
||||||
|
You need to upgrade to git-annex 5.20141203. With that version,
|
||||||
|
you can pass port=443 to git-annex initremote and it will then use
|
||||||
|
https.
|
||||||
|
|
||||||
|
The old version you're using does not support this.
|
||||||
|
|
||||||
|
Also, AFAIK, S3 does not send passwords over the wire; it uses a
|
||||||
|
challange-response, which proves to the S3 server that you possess the
|
||||||
|
access keys. This would not be susceptable to attackers in the way you
|
||||||
|
think it is.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue