I thought the whole reason httpd 1.1 was produced was specifically for
this reason. Why do they need multiple methods of producing the same
result, especially when one breaks existing standards?
On Sat, 28 Jul 2018, Mouse wrote:
SNI basically transmits the actual vhost you wish to visit, in URL
terms the part between https:// and the first slash after that, [...]
[...]
Then, the people [...] thought it would be good to create TLSv1.3
[...] and decided to add SNI to that standard; not only that, but
they *require* it to be used now.
So, TLS 1.3 is not usable for securing anything except the Web? (That
is, if you aren't "visit"ing a "vhost"?)
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mo...@rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev
_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev
