Re: RE : Problem getting SNI to work on client side.

"Ludo Brands" <[email protected]> writes:

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

Sure, I realise what you're trying to do, but there's no mechanism in cryptlib
for doing this because explicitly specifying the server name (for cryptlib to
connect to) is mutually exclusive with providing an already-connected socket.
What you could do is modify the code so that CRYPT_SESSINFO_SERVER_NAME
records the name without trying to use it to establish a network connection,
and then use it to obtain the SNI value.

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.