Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS4 not working with 3rd Party (dcs.dunkel.de) #9679

Closed
cyberduck opened this issue Sep 2, 2016 · 3 comments
Closed

AWS4 not working with 3rd Party (dcs.dunkel.de) #9679

cyberduck opened this issue Sep 2, 2016 · 3 comments
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Sep 2, 2016

2d787b9 created the issue

Hi,

after upgrade from 5.0.11 to 5.1 our dcs.dunkel.de 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,

Ingo

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 6, 2016

@dkocher commented

Duplicate for #9667.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Sep 6, 2016

@dkocher commented

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

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 5, 2016

@dkocher commented

Milestone renamed

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate s3 AWS S3 Protocol Implementation
Projects
None yet
Development

No branches or pull requests

1 participant