Re: SSL Server Name Indication (SNI) client support

Julien Barbot <[email protected]>
Newsgroups gmane.comp.lang.erlang.patches
Message-ID <CAKr4mvJ_FzKW+r_isO6_rDMNBvsQoOmTGCGfBrnY=eL9JEye2A@mail.gmail.com>
Hi,

Here is a new attempt to implement SNI (RFC 6066, section 3). This is
*only* the client side implementation.

The server implementation will come later.

There is no API modification, SNI is used if the connection endpoint
is a hostname.

Comments are welcome.

git fetch git://github.com/klyr/otp.git r17_ssl_sni_client

https://github.com/klyr/otp/compare/master...r17_ssl_sni_client
https://github.com/klyr/otp/compare/master...r17_ssl_sni_client.patch

Pending questions are:
- how to do an ssl upgrade with sni ?
- is an aditional option to ssl:connect needed to explicitly choose an
ssl virtual host (like {virtual_host, string()}) ?
- is an aditional option to ssl:connect needed to explicitly disable sni ?

Regards,

-- 
Julien Barbot
_______________________________________________
erlang-patches mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-patches
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.