[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] TLS-"transport layer security" & LYNX

From: Travis Siegel
Subject: Re: [Lynx-dev] TLS-"transport layer security" & LYNX
Date: Sat, 28 Jul 2018 18:39:36 -0400 (EDT)
User-agent: Alpine 2.21 (DEB 202 2017-01-01)

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         address@hidden
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Lynx-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]