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

Using SNI switching does not work if client verification is used in one of the "virtual" servers #234

Open
johanhedin opened this issue Dec 14, 2024 · 0 comments

Comments

@johanhedin
Copy link

This issue is most easily described from uWebSockets point of view. When using addServerName like:

auto app = uWS::SSLApp({
    .key_file_name = "srv1.key",
    .cert_file_name = "srv1.crt"
}).addServerName("server2.example.com", {
    .key_file_name = "srv2.key",
    .cert_file_name = "srv2.crt",
    .ca_file_name = "client-ca.crt"
})
//snip
.domain("server2.example.com") 
//snip

client verification for server2 is not set up correctly. PR #224 adds the necessary SSL_set_verify() for this to work. This is also how it is done (-ish) in httpds equivalent function in mod_ssl: https://github.com/apache/httpd/blob/4a9cd1fccf8e79eda2132d65166af6e87e4f5fe9/modules/ssl/ssl_engine_kernel.c#L2591.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant