4 ms·
> This is a client bug, IMO. And sensible servers like Caddy (and yes, before people complain about disclosure, I made it) staple OCSP automatically. As a clie
by marginalia_nu 5y ago
> This is a client bug, IMO. And sensible servers like Caddy (and yes, before people complain about disclosure, I made it) staple OCSP automatically.
As a client I don't get to choose how the servers interact with are configured.
> But optional (and often discouraged), not required. Separate issue!
Not at all a separate issue. The issue is the absolute fantasy that HTTPS makes your connection secure.
> Don't use clients you don't trust, period. And some big-name clients like Chrome let you dump keys to inspect data transfers locally.
Are you really telling me I have to implement every piece of software I want to run myself from scratch, write custom firmware for my processor, for my router, then sit down and create a custom ROM with a custom operating system for my phone?
- mholt 5y ago> As a client I don't get to choose how the servers interact with are configured. Clients are the ones that cause the privacy leak, not servers. > The issue is the absolute fantasy that HTTPS makes your connection secure. Oh, OK. > Are you really telling me I have to implement every piece of software I want to run myself from scratch, write custom firmware for my processor, for my router, then sit down and create a custom ROM with a custom operating system for my phone? If you don't trust them, then yes. Nothing new here though.
- marginalia_nu 5y ago> Clients are the ones that cause the privacy leak, not servers. Regardless of where the leak is, this is not a problem that exists in HTTP. You could not just go to a central server and gather a log of some NN% of the HTTP connections being made. No, DNS is not analogous. You can choose your DNS server, you can even run your own. > If you don't trust them, then yes. Nothing new here though. What's new is that it's become a lot harder to examine the information my software is sending to servers on the Internet. If they all talked HTTP, it would be trivial for me to intercept and examine. You can do that with HTTPS, sometimes, but it's a lot harder and relies on the software obeying OS proxy settings.
- waste_monk 5y agoYou probably want a layer 7 firewall that only allows HTTPS traffic to/from the internet to your terminating proxy. Stuff that doesn't obey the system proxy (or a few of the other pitfalls e.g. HPKP) will break, but at least you'd be aware of what's not allowing itself to be intercepted.
- SahAssar 5y ago> Not at all a separate issue. The issue is the absolute fantasy that HTTPS makes your connection secure. HTTPS is reasonably secure if the person in control of the domain is making sure it is reasonably secure. Setting up your whole domain to be MITM is not that. Your connection to whatever place the person in control of the domain has delegated your connection to is reasonably secure.
- hulitu 5y ago> HTTPS is reasonably secure if the person in control of the domain is making sure it is reasonably secure. Setting up your whole domain to be MITM is not that. And how do you know how secure is a certificate issued by Google or Cloudfare or Microsoft ? Those certificates are just trusted. Good luck with security.
- hdjjhhvvhga 5y ago> The issue is the absolute fantasy that HTTPS makes your connection secure. Well, this is a kind of compromise. It is similar with COVID-19 vaccines: even though they don't prevent transmission, hospitalization and death, they do reduce them (at least the last two). Even though HTTPS can not offer a very high protection level, together with accompanying technologies they do make certain attacks more problematic - especially sniffing. So for most intents and purposes, HTTPS may make a connection more secure.
- tedunangst 5y agoAs a client you get to choose whether to check ocsp or not. If you don't like it, don't do it.