• 0 Posts
  • 176 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle



  • Not exactly. They are pointing out that HTTPS assumes all is well if it sees a certificate from any “trusted” certificate authority. Browsers typically trust dozens of CAs (nearly 80 for Firefox) from jurisdictions all over the world. Anyone with sufficient access to any of them can forge a certificate.

    Great thing, that you can remove them and only trust those you trust.

    Also, HTTPS doesn’t cover all traffic like a properly configured VPN does.

    Pls explain what https is not covered? The SNI on tbe first visit? A VPN just moves the “exit point” of your traffic. Now the Datacentef and VPN provider sees what you ISP saw.

    it’s not difficult for a well positioned snooper (like an internet provider that has to answer to government) to follow your traffic on the net and deduce what you’re doing.

    No. I never said otherwise. But they cannot spy on the traffic. And since the SNI is not encrypted anyway they do not even nerd to “follow the traffic”. But what sites you are visiting and what you are doing on them are 2 different things.



  • You can read more about this learning about X.509.

    Its the PKI thats broken, namely the root stores. Has been unreliable for many, many years. This is why packages are signed.

    So you are basically saying that root CAs are unreliable or compromised?

    The great thing is, that you can decide on your own which CAs you trust. Also please proof that those are actively malicious.

    And no. That is not the reason that packages are signed, i am guessing you mean packages like on linux, packages contained in the installation repository. The reason is, that you build another chain of trust. Why would i trust a CA which issues certificates for domains with code distribution. That’s not their job.