Actions
Bug #21039
closedS3 AWSv4 wrong signature when PUT-ing files
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
- Affected version
Ceph Luminous 12.1.2
- Problem
I'm testing radosgw with s3cmd, because it's the de facto standard cli client for S3 APIs.
When getting a file, the "canonical request" is generated as expected:
GET /test2.txt host:test-judu0.cct-clevercloud-customers.services.clever-cloud.com x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 x-amz-date:20170818T133513Z host;x-amz-content-sha256;x-amz-date e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
(That's from the radosgw logs)
But when I PUT files:
PUT text/plain x-amz-content-sha256:aec070645fe53ee3b3763059376134f058cc337247c978add178b6ccdfb0019f x-amz-date:Fri, 18 Aug 2017 13:37:18 +0000 x-amz-meta-s3cmd-attrs:atime:1503057800/ctime:1503057800/gid:1001/md5:14758f1afd44c09b7992073ccf00b43d/mode:33188/mtime:1503057800/uid:1001/uname:judu x-amz-storage-class:STANDARD /test2.txt
(That's also from the radosgw logs)
You can see that the canonical request generation is completely different when I PUT than when I GET a file.
- Next
I just saw that 12.1.3 is out, I'm building it right now to test.
Updated by Julien Durillon over 6 years ago
Ok, the issue is in the default systemd service provided and the documentation. Not in the signature process.
Actions