Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the problem of signature version of s3cmd connecting rgw

2025-01-22 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to solve the problem of signature version of s3cmd connecting rgw". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

# signature v4 rollback to v2 using s3cmd version 1.6.1 to connect to rgw (ceph 0.94.5) found the following problems

DEBUG: CreateRequest: resource [uri] = / DEBUG: Using signature v4DEBUG: get_hostname (s3soft): s3soft.s3.xxx.comDEBUG: canonical_headers = host:s3soft.s3.xxx.comx-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855x-amz-date:20160429T123546ZDEBUG: Canonical Request:GET/delimiter=%2Fhost:s3soft.s3.xxx.comx-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855x-amz-date:20160429T123546Zhost;x-amz-content-sha256 X-amz-datee3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855DEBUG: signature-v4 headers: {'xmuramzlycontentlysha256colors: 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855,' Authorization': 'AWS4-HMAC-SHA256 Credential=KFIH2I8PDAU38KABCDEFG/20160429/US/s3/aws4_request,SignedHeaders=host;x-amz-content-sha256 XmuramzMaidatedSignatureForme94cbf3893183ccf53b6f4b38a2136252c83c6fd022f9cab1f4cbc29f78cd30cable, 'xmuramzagenda:' 20160429T123546Z'} DEBUG: Processing request, please wait...DEBUG: get_hostname (s3soft): s3soft.s3.xxx.comDEBUG: ConnMan.get (): creating new connection: http://s3soft.s3.xxx.comDEBUG: non-proxied HTTPConnection (s3soft.s3.xxx.com) DEBUG: format_uri (): /? delimiter=/DEBUG: Sending request method_string='GET', uri='/?delimiter=/' Headers= {'xMuamzMurcontentsha256 colors: 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Authorization':' AWS4-HMAC-SHA256 Credential=KFIH2I8PDAU38KABCDEFG/20160429/US/s3/aws4_request,SignedHeaders=host X-amz-content-sha256 XmuramzF3893183ccf53b6f4b38a2136252c83c6fd022f9cab1f4cbc29f78cd30cables, 'xmuramzflidatedates:' 20160429T123546Z'}, body= (0 bytes) DEBUG: Response: {'status': 400,' headers': {'content-length':' 81cards, 'accept-ranges':' bytes', 'server':' openresty', 'connection':' keep-alive','x Methodist amzReceivers: 'tx00000000000000017a1e9-0057235523color d753color xxs1cards,' date': 'Fri 29 Apr 2016 12:35:47 GMT', 'content-type':' application/xml'}, 'reason':' Bad Request', 'data':' InvalidArgument'} DEBUG: ConnMan.put (): connection put back to pool (http://s3soft.s3.xxx.com#1)DEBUG: Falling back to signature v2DEBUG: Using signature v2DEBUG: SignHeaders: 'GET\ n\ nx-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855\ nx-amz-date:Fri 29 Apr 2016 12:35:47 + 0000\ n/s3soft/'DEBUG: Processing request, please wait...DEBUG: get_hostname (s3soft): s3soft.s3.xxx.comDEBUG: ConnMan.get (): re-using connection: http://s3soft.s3.xxx.com#1DEBUG: format_uri (): /? delimiter=/DEBUG: Sending request method_string='GET', uri='/?delimiter=/', headers= {'xMuamz contentlysha256 colors: 'e3b0c44298fc149afbf4c8996fb92427ae41e4649b934ca495b785b855,' Authorization': 'AWS KFIH2I8PDAU38KABCDEFG:jhRC5YXvJL5suBcVb4dE2rsGDfg=' Fri, 29 Apr 2016 12:35:47 + 0000'}, body= (0 bytes) DEBUG: Response: {'status': 200,' headers': {'transfer-encoding':' chunked', 'server':' openresty', 'connection':' keep-alive','x Muhammad requestAfter: 'tx00000000000000017a858-0057235523, d750Muhxs1century,' date': 'Fri, 29 Apr 2016 12:35:47 GMT' 'content-type':' application/xml'}, 'reason':' OK', 'data':

# reason Analysis currently only version 10.2.0 supports v4 version of signature, so the authentication of signature v4 needs to be disabled. Signature v2 is used by default. Reducing the number of illegal requests from the client is also one of the optimization means.

# solution vi ~ / .s3cfg can be set as follows

Signature_v2 = True, "how to solve the problem of s3cmd connecting to the signature version of rgw" is introduced here. Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report