RE : Problem getting SNI to work on client side.

I'm trying to make SNI working with cryptlib in the open source Synapse
project (synchronuous network library for Delphi/FPC). When making the https
connection I do have already the hostname as it appears in the HTTP header.
This is the same name that servers expect for SNI. So it is not a matter of
getting the hostname but one of passing it to the cryptlib SNI mechanism
without using the CRYPT_SESSINFO_SERVER_NAME which does more than just
storing the name. 

Thanks, Ludo   

-----Message d'origine-----
De : Peter Gutmann [mailto:[email protected]] 
Envoyé : vendredi 4 mars 2011 05:17
À : [email protected]; [email protected]
Objet : Re: [Cryptlib] Problem getting SNI to work on client side.


"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.