Re: Problem getting SNI to work on client side.
Peter Gutmann <[email protected]>
| Newsgroups | gmane.comp.encryption.cryptlib |
|---|---|
| Message-ID | <[email protected]> |
"Ludo Brands" <[email protected]> writes: >I'm trying to get SNI working on the client side. Problem is that the server >name sent to the server is extracted from the CRYPT_SESSINFO_SERVER_NAME >attribute (ssl_ext.c) and I'm using the CRYPT_SESSINFO_NETWORKSOCKET >attribute to initiate the session. Using both results in a CRYPT_ERROR_INITED >error. Is there a way around to set this attribute without initializing the >session? Or should there be a new/other attribute that can be used as an >alternative source for the server name? If you're supplying a raw socket yourself then unfortunately that kinda destroys any link to the original DNS name, at best you could use getpeername() but that'll only give you an IP address. So for something like this you would, unfortunately, have to come up with your own mechanism for doing it. Peter. _______________________________________________ Cryptlib mailing list [email protected] via Mail: [email protected] Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/ http://news.gmane.org/gmane.comp.encryption.cryptlib Posts from non-subscribed addresses are blocked to prevent spam, please subscribe in order to post messages.