From: Joey Hess <joeyh@joeyh.name>
Date: Wed, 13 Jul 2022 18:53:46 +0000 (-0400)
Subject: followup
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~72^2~63
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=7c7b7ac9b92fcf9a76516e02402a95858fc29de7;p=git-annex.git

followup
---

diff --git a/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__.mdwn b/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__.mdwn
index cb103f7436..32c025eaa9 100644
--- a/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__.mdwn
+++ b/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__.mdwn
@@ -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]]
diff --git a/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__/comment_1_a7fcd34cf9376e900db832a8010df7d7._comment b/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__/comment_1_a7fcd34cf9376e900db832a8010df7d7._comment
new file mode 100644
index 0000000000..0096874f3d
--- /dev/null
+++ b/doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__/comment_1_a7fcd34cf9376e900db832a8010df7d7._comment
@@ -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?
+"""]]
diff --git a/doc/todo/allow_for_annonymous_AWS_S3_access/comment_1_0723643146ba36131218be090e6d5c73._comment b/doc/todo/allow_for_annonymous_AWS_S3_access/comment_1_0723643146ba36131218be090e6d5c73._comment
new file mode 100644
index 0000000000..b0a0b17907
--- /dev/null
+++ b/doc/todo/allow_for_annonymous_AWS_S3_access/comment_1_0723643146ba36131218be090e6d5c73._comment
@@ -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?
+"""]]