[Cyberduck-trac] [Cyberduck] #10203: S3 AWS2 algoritm not allowed any more

[Cyberduck]

#10203: S3 AWS2 algoritm not allowed any more
----------------------------+----------------------
 Reporter:  eithel.sanchez  |         Owner:
     Type:  defect          |        Status:  new
 Priority:  high            |     Milestone:
Component:  s3              |       Version:  6.3.4
 Severity:  major           |    Resolution:
 Keywords:                  |  Architecture:
 Platform:                  |
----------------------------+----------------------
Description changed by dkocher:

Old description:

> cyberduck version: 6.3.5
>
> In previous versions of cyberduck was posible to generate an link to a
> file in S3 using AWS2 algoritm; but now is not possible, the links are
> generated with AWS4 algoritm.  Then the links are not valid when they are
> generated for more than 7 days.
> So this is the error from S3:
> <Error>
> <Code>AuthorizationQueryParametersError</Code>
> <Message>
> X-Amz-Expires must be less than a week (in seconds); that is, the given X
> -Amz-Expires must be less than 604800 seconds
> </Message>
> <RequestId>98B36638CCB7B4C6</RequestId>
> <HostId>FEE9lxU08MTVYLb4gD6RWC0N4knK2HfkQBvmPfz6cW0QuHcl4RPuJidWOA9a7GxadHNq6WX4bz4=</HostId>
> </Error>
>
> In previous version was posible to force the AWS2 algoritm in a file
> user.config whith this:
> <setting name="s3.signature.version" value="AWS2" />
>
> but is not working any more.

New description:

 cyberduck version: 6.3.5

 In previous versions of cyberduck was posible to generate an link to a
 file in S3 using AWS2 algoritm; but now is not possible, the links are
 generated with AWS4 algoritm.  Then the links are not valid when they are
 generated for more than 7 days.
 So this is the error from S3:

 {{{
 <Error>
 <Code>AuthorizationQueryParametersError</Code>
 <Message>
 X-Amz-Expires must be less than a week (in seconds); that is, the given X
 -Amz-Expires must be less than 604800 seconds
 </Message>
 <RequestId>98B36638CCB7B4C6</RequestId>
 <HostId>FEE9lxU08MTVYLb4gD6RWC0N4knK2HfkQBvmPfz6cW0QuHcl4RPuJidWOA9a7GxadHNq6WX4bz4=</HostId>
 </Error>

 }}}

 In previous version was posible to force the AWS2 algoritm in a file
 user.config whith this:
 <setting name="s3.signature.version" value="AWS2" />

 but is not working any more.

--

--
Ticket URL: <https://trac.cyberduck.io/ticket/10203#comment:1>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows