Cyberduck Mountain Duck CLI

#9679 closed defect (duplicate)

AWS4 not working with 3rd Party (

Reported by: Owned by:
Priority: normal Milestone: 5.1.3
Component: s3 Version: 5.1
Severity: blocker Keywords: AWS4
Cc: Architecture:



after upgrade from 5.0.11 to 5.1 our is not working any more. I tracked down the issue towards the default AWS4 authentication.

While we are trying hard fixing that - is there any possibility to edit the profile, NOT to use AWS4?

kind regards,


Change History (3)

comment:1 Changed on Sep 6, 2016 at 8:30:21 AM by dkocher

  • Milestone set to 5.2
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate for #9667.

comment:2 Changed on Sep 6, 2016 at 8:30:55 AM by dkocher

Please update to the latest snapshot build available. As of r21343 you can use a new connection profile that will use AWS2 signature version for authentication.

comment:3 Changed on Oct 5, 2016 at 1:39:23 PM by dkocher

  • Milestone changed from 5.2 to 5.1.3

Milestone renamed

Note: See TracTickets for help on using tickets.