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

Can't use SNI from the server, or it is not obvious how to do that.... #103

Closed
alcidesv opened this issue Feb 11, 2015 · 5 comments
Closed

Comments

@alcidesv
Copy link

There is a field clientUseServerNameIndication in ClientParams, but nothing similar in ServerParams... without this, it is not possible to implement "virtual hosts" in a TLS server.

@vincenthz
Copy link
Collaborator

SNI should just be recorded on the server side (just like many other extensions). Then after a succesfull handshake, a server could query the context and act accordingly.

for example, something like:

  case getClientSNI context where
        Nothing -> proceed_to_normal_host
        Just "my.virtual.host1.com" -> proceed_to_my_virtual_host1
         ......          

@kazu-yamamoto
Copy link
Collaborator

I cannot find getClientSNI in the source code. Am I missing something?

@vincenthz
Copy link
Collaborator

no, it doesn't exist yet, it was a wishful code example

@kazu-yamamoto
Copy link
Collaborator

OK.

I think that what users want is setting parameters with which we can specify multiple secret keys and their certificates based on SNI values.

@kazu-yamamoto
Copy link
Collaborator

getClientSNI is a part of API now. Let's close this.

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

3 participants