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

followup

Browse source
This commit is contained in:
Joey Hess 2022-07-13 14:53:46 -04:00
parent 68e9b7f987
commit 7c7b7ac9b9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 31 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__.mdwn
View file

@ -26,3 +26,6 @@ what exactly does it want from me for AWS4-HMAC-SHA256 ? here is how those secr
$ echo AWS_ACCESS_KEY_ID=$(awk '/^access_key/{print $3}' ~/.s3cfg-dandi-backup) AWS_SECRET_ACCESS_KEY=$(awk '/^secret_key/{print $3}' ~/.s3cfg-dandi-backup) | tr 'a-z0-9' '?-?'
AWS_ACCESS_KEY_ID=AKIA?GIMZPVVE??Y?NKH AWS_SECRET_ACCESS_KEY=/??U??TV?LH?L???KZJ??RF?G???Y+?S??????LM
```
[[!meta author=yoh]]
[[!tag projects/dandi]]

11
doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__/comment_1_a7fcd34cf9376e900db832a8010df7d7._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2022-07-13T17:46:54Z"
content="""
That seems to be Signature Version 4. Try adding this to the initremote: signature=v4
Some AWS regions need V4, others still work with V2, which is what it used
by default. I have not seen the default US region require V4 before.
Could be something about your AWS access key that needs v4?
"""]]

17
doc/todo/allow_for_annonymous_AWS_S3_access/comment_1_0723643146ba36131218be090e6d5c73._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2022-07-13T18:16:57Z"
content="""
I've checked and the haskell aws library does not currently support this.
Since the library currently needs a maintainer, I have not filed an issue
to implement this.
It might be possible to work around it, by using s3SignQuery with a dummy
credentials, and then modifying the SignedQuery that it returns to remove
the authentication headers. Or by bypassing s3SignQuery and constructing
a SignedQuery that is not actually signed.
Do you have a sample bucket that does allow anonymous access, not only
to individual files, but to listing the content of the bucket?
"""]]