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

Certificate trust error connecting to os.unil.cloud.switch.ch #9668

Closed
cyberduck opened this issue Aug 25, 2016 · 4 comments
Closed

Certificate trust error connecting to os.unil.cloud.switch.ch #9668

cyberduck opened this issue Aug 25, 2016 · 4 comments
Assignees
Labels
bug fixed s3 version:5.0.11
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Aug 25, 2016

791684b created the issue

Hi,

We are running a third party S3 compatible object store using SSL star certificate.
Because of the FQDN name size, Cyberduck always show a certificate trust error about the SSL certificate of the service.
See attached screenshot.

Our service use a valid star certificate for 'os.unil.cloud.switch.ch' and '*.os.unil.cloud.switch.ch'. You can check it here

https://os.unil.cloud.switch.ch 

I think it is related to the issue #3813.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 25, 2016

791684b commented

For testing this bucket is public readable (anonymous): s3://os.zhdk.cloud.switch.ch/valery-public or s3://valery-public.os.zhdk.cloud.switch.ch.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 25, 2016

@dkocher commented

Regression from 18562.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 26, 2016

@dkocher commented

In 8110631.

@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 fixed s3 version:5.0.11
Projects
None yet
Development

No branches or pull requests

2 participants