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

comment and close; bug reporter is using old version and is also mistaken about how S3 security works

Browse source
This commit is contained in:
Joey Hess 2015-02-04 15:00:33 -04:00
parent c30414a5aa
commit 092eef5894
2 changed files with 18 additions and 0 deletions

2
doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn
View file

@ -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
### Please provide any additional information below.
> [[done]]; port=443 supported since 5.20141203. --[[Joey]]

16
doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__/comment_2_c01a47b9df3167c9af8e5e43ec138401._comment Normal file
View file

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