rclone: SignatureDoesNotMatch: release 1.60.0 broke the copy using S3 backend with Other (GCS) as provider
The associated forum post URL from https://forum.rclone.org
N/A
What is the problem you are having with rclone?
The copy of a file using S3 backend with Other
provider (Google Cloud Storage) started to fail with the 1.60.0 release.
What is your rclone version (output from rclone version
)
rclone v1.60.0
- os/version: darwin 12.5.1 (64 bit)
- os/kernel: 21.6.0 (x86_64)
- os/type: darwin
- os/arch: amd64
- go/version: go1.19.2
- go/linking: dynamic
- go/tags: cmount
Which OS you are using and how many bits (e.g. Windows 7, 64 bit)
macOS 12.5.1, x86_64
Which cloud storage system are you using? (e.g. Google Drive)
S3 with Other as provider.
The command you were trying to run (e.g. rclone copy /tmp remote:tmp
)
./rclone --config gcs_over_s3.conf copy source:/bucket/file .
With a config like:
[source]
type = s3
access_key_id = XXX
provider = Other
secret_access_key = XXX
endpoint = https://storage.googleapis.com
A log from the command with the -vv
flag (e.g. output from rclone -vv copy /tmp remote:tmp
)
Failed to copy: failed to open source object: SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.
Looking at the result of --dump headers
:
- HEAD request still works
- GET request fails
When I compare the output between 1.60.0 and 1.59.2 for the GET request the only difference I can see (despite dates,…) is the order of request headers…
FAIL
Host: storage.googleapis.com
User-Agent: rclone/v1.60.0
Accept-Encoding: gzip
Authorization: XXXX
X-Amz-Content-Sha256: XXXX
X-Amz-Date: 20230106T081010Z
WORK
Host: storage.googleapis.com
User-Agent: rclone/v1.59.2
Authorization: XXXX
X-Amz-Content-Sha256: XXXXXX
X-Amz-Date: 20230106T080942Z
Accept-Encoding: gzip
The X-Amz-Content-Sha256
is the same value for both request.
The headers of the HEAD request (works) of v1.60.0:
Host: storage.googleapis.com
User-Agent: rclone/v1.60.0
Authorization: XXXX
X-Amz-Content-Sha256: XXXXXX
X-Amz-Date: 20230106T081010Z
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don’t comment if you have no relevant information to add. It’s just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 18 (18 by maintainers)
Thanks for your feedbacks, PR updated