🇨🇦Samuel Proulx🇨🇦

Blind geek, fanfiction lover (Harry Potter and MLP). keyoxide: aspe:keyoxide.org:PFAQDLXSBNO7MZRNPUMWWKQ7TQ

  • 1 Post
  • 23 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle








  • From the article:

    The TLS-SNI header is used by CDN servers to route requests based on the Server Name in the header. However, a typical front end server, or even a load balancer (LB), belongs to a single app or organization, and does not typically need to handle the SNI header. The easy and reasonable way to configure TLS certificates on such a server, is to either:
 Serve all requests with a single TLS certificate that has SANs (Subject Alternative Names) for all the domains that are used Have multiple certificates, chosen according to SNI, with one of them as the default. In both of these common cases, sending a HTTPS request directly to the IP of a front end server, without any SNI, will present us with a default server certificate. This certificate will reveal what domains are being served by this server.

    So apparently the real issue is that people aren’t using SNI correctly.













  • So who are they sending our product browsing data to in order to provide this service? At least I know what Microsoft and Google are doing with my data (nothing good). But Pocket and cloudflare and there VPN provider and whatever other random companies Firefox partners with? Who knows! How do I opt out? Who knows! How secure are these companies? Who knows! At least using Edge or Chrome I only have to hand over my data to one evil corporation, instead of several. Plus I actually get things I want in return (for me: automatic image descriptions, reader mode, read aloud, and AI based page summaries). Nothing I get from the companies Firefox works with are things I even want.