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

S3 HTTP profile is sending encrypted data after update to 7.4.0 #11061

Closed
cyberduck opened this issue May 28, 2020 · 3 comments
Closed

S3 HTTP profile is sending encrypted data after update to 7.4.0 #11061

cyberduck opened this issue May 28, 2020 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 28, 2020

758cbbf created the issue

I just updated to Cyberduck 7.4.0, and I tried to connect to an on-premise S3 storage system (Scality-based) that I used to use for testing. I got an error about a failed directory listing.
"Failed to parse XML document with handler class org.jets3t.service.impl.rest.XmlResponsesSaxParser$ListBucketHandler. Please contact your web hosting service provider for assistance."

I looked at the logs on my Scality system and my endpoint was sending a "400 Bad request response back".I was using a non-SSL endpoint for this test, and the S3 HTTP cyberduckprofile downloadable on the Amazon S3 protocol page.

When I sniffed the network, I saw a request come in from my client machine where cyberduck is running, but it was all garbage. That's when i started suspecting that the request was coming in SSL-encrypted, on an endpoint configured to not use SSL.

I tried the same cyberduck, and profile/access credentials on an SSL endpoint, and it worked.

Can you please look into this?

Thanks

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 5, 2020

@dkocher commented

Can be reproduced.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 5, 2020

@dkocher commented

Regression from 9ea64ca.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 8, 2020

@ylangisc commented

In 104af11.

Loading

@cyberduck cyberduck closed this Jun 8, 2020
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants