3 ms·
"Who have shown repeatedly to be user hostile; especially towards privacy conscious users." What examples were you thinking of. They are still the only CDN of
by 1vuio0pswjnm7 5y ago
"Who have shown repeatedly to be user hostile; especially towards privacy conscious users."
What examples were you thinking of.
They are still the only CDN offering TLS1.3 with ESNI. Problem is they do not necessarily encrypt backend connections. TLS version and SNI are relevant IMO because even with DoH, without TLS1.3 plus ESNI, the ISP can still see domain names in the clear on the wire in client hello packets sent and TLS certificates returned from remote IPs. All those AWS-hosted sites you visit all require SNI, the domain name sent in the clear over the wire for your ISP to track. For many, you can use the cloudfront CNAME as the SNI but it would be easy for an ISP to keep lookup table for all AWS CNAMES. HN's hosting provider will not even support TLS1.3, it's TLS1.2 at best.
SNI is hostile toward privacy conscious users and makes censorship easier.
- Semaphor 5y agoBut what’s the alternative to SNI for multiple domains on one IP? And don’t say IPv6, because my ISP doesn’t even offer that yet…
- kelnos 5y agoESNI with TLSv1.3. (The "E" means "encrypted".)
- Semaphor 5y agoThat does sound nice, but apparently it’s already been succeeded by TLS ECH, and neither of them are widely enabled by default, so essentially there is currently no SNI alternative.
- 1vuio0pswjnm7 5y agoESNI (now called ECH): https://defo.ie https://defo.ie I use ESNI-enabled openssl from github.com/sftcd, 30 Aug 2019 release, for all HTTP requests to Cloudflare-hosted sites and it works well. A noticeable downside is one has to keep fetching a new key in a DNS TXT RR every hour. Another use for DoH; the key can re retrieved via DoH (no SNI required).