From d9ed94f15b5eec1ae36b2d45732a06951c06f25a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 6 Jan 2020 13:59:03 -0400 Subject: [PATCH] comment --- ..._12fd9dfb47e157e1d38c5e88a543498b._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/todo/S3_special_remote_support_for_DigitalOcean_Spaces/comment_1_12fd9dfb47e157e1d38c5e88a543498b._comment diff --git a/doc/todo/S3_special_remote_support_for_DigitalOcean_Spaces/comment_1_12fd9dfb47e157e1d38c5e88a543498b._comment b/doc/todo/S3_special_remote_support_for_DigitalOcean_Spaces/comment_1_12fd9dfb47e157e1d38c5e88a543498b._comment new file mode 100644 index 0000000000..56718b48e5 --- /dev/null +++ b/doc/todo/S3_special_remote_support_for_DigitalOcean_Spaces/comment_1_12fd9dfb47e157e1d38c5e88a543498b._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2020-01-06T17:41:21Z" + content=""" +This is either a bug in or +Digital Ocean's implementation of the S3 protocol. I don't know which, +but I do know it has to be fixed in one of those two place, and not +in git-annex. + +The fact that the aws library can't even parse an error message out of +their response kind of says something. + +But the real problem seems to +While they claim to support V2 signatures, +my guess is there's a problem with their support for V2, since they're +mostly dealing with V4. The aws library's support for V4 is experimental +and [apparently buggy](https://github.com/aristidb/aws/issues/262), but +as git-annex uses it, it will only use V2. +"""]] -- 2.30.2