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

Server Name Indication (SNI) not supported #6008

Closed
cyberduck opened this issue Jun 15, 2011 · 5 comments
Closed

Server Name Indication (SNI) not supported #6008

cyberduck opened this issue Jun 15, 2011 · 5 comments
Assignees
Labels
bug thirdparty Issue caused by third party webdav WebDAV Protocol Implementation

Comments

@cyberduck
Copy link
Collaborator

afc11a5 created the issue

Apparently Cyberduck doesn't support SNI with WebDAV. I get this lines in Apache log files when trying to connect to SSL enabled vhosts:

==> /var/log/apache2/www.windfluechter.net-error.log <==

[Wed Jun 15 19:57:42 2011] [error] No hostname was provided via SNI for a name based virtual host

==> /var/log/apache2/www.windfluechter.net-access.log <==

[15/Jun/2011:19:57:42 +0200] rostock.ip6.windfluechter.net 2001:6f8:90e:900::2 - "PROPFIND /webdav/ HTTP/1.1" 403 209 "-" "Cyberduck/4.0.2 (Mac OS X/10.6.7) (i386)" www.windfluechter.net

This results in choosing the wrong SSL cert (first/default SSL cert in Apache). Please seet the hopefully attached screenshot.

Regards,
Ingo


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Haven't heard of SNI before. Do you run multiple SSL virtual hosts with the same IP address?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Before I dig into this further, can you update to the latest snapshot build and replicate the issue. The WebDAV protocol implementation has changed for 4.1.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is in Server Name Indication in RFC 4366.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We rely on the TLS implementation in Java where SNI is supported as of SE 7. We currently ship the App Store version of Cyberduck bundled with JRE 7 where this issue should be resolved. For the version of Cyberduck with no JRE bundled, this will be resolved when JRE 7 is available for OS X.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:5 dkocher]:

We rely on the TLS implementation in Java where SNI is supported as of SE 7. We currently ship the App Store version of Cyberduck bundled with JRE 7 where this issue should be resolved. For the version of Cyberduck with no JRE bundled, this will be resolved when JRE 7 is available for OS X.

This is now resolved as of 4.4.

@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 thirdparty Issue caused by third party webdav WebDAV Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants