Earlier quoted context omitted.
Correct me if I'm wrong, but the signed server-identifying cert is swapped in TLS before the connection is encrypted, no? So it's not technically infeasible to have networking gear drop any connection which doesn't chain back to a government-approved root?
> Correct me if I'm wrong, but the signed server-identifying cert is swapped in TLS before the connection is encrypted, no? Only on old TLS versions. TLS 1.3 changed it so the server certificate is also encrypted.
Tell HN: Sci-Hub's TLS certificate has started failing
151–154 of 154 posts
Re: Tell HN: Sci-Hub's TLS certificate has started failing
#152Only one of the domain/wildcard pairs listed in Sci-Hub's certificate actually works for me right now. It's probable the certificate was revoked not because some publisher threatened legal action against Comodo, but because Sci-Hub no longer controls some of the domains listed in their certificate. If this is the case then they would be able to get a new certificate for free with those names removed. I wouldn't go ru…
Re: Tell HN: Sci-Hub's TLS certificate has started failing
#153Earlier quoted context omitted.
Microsoft runs a root store. That gives them more leverage over the CAs than McDonalds has.
I'd be curious what would happen if the "too big to fail" issuers pushed back against this. Microsoft's only option is to completely drop the root cert, right? So there's no real non-nuclear option... In the broader sense, this is one downside of the shift towards Lets Encrypt and CAs being more interchangable: increased power of the root stores relative to them. Sometimes that's good, sometimes it's evil.
In small-scale disputes MS (and other browser vendors) would not have to nuke an entire large CA to get their way. In principle they could just blacklist the individual certs/names, leaving the CA's other certs alone.
That ability/implied threat probably does mean that the CAs tend to comply with MS piracy/copyright-related revocation requests, because refusing to comply would piss off MS (and possibly law enforcement) without actually stopping them from getting their way by other means.
Re: Tell HN: Sci-Hub's TLS certificate has started failing
#154Earlier quoted context omitted.
It's a simple fact. It doesn't need to be planned or conspirated. The fact that root CAs are at the top, modulo self signed certs exchanged person to person IRL, is certainly no secret. The conspiracy would be that they might use the fact to censor or listen, whoever they are. The conspiracy would be not to tell anyone beforehand, because otherwise it wouldn't be a conspiracy anymore. What kind of exhaustive evidence…
Who are "they"? Google? Mozilla? Microsoft? Apple? The 100s of CAs? And, are they all working together? And there hasn't been a single whistleblower to expose this? What do you mean "listen"? CAs can invalidate certs at will, but, they have no mechanism to listen on communications (unless you give them your private key, but, then anyone you give your private key to can eavesdrop). The CA system has lots of issues. It…
A court seizing a domain thereby invalidating a cert.
> What do you mean "listen"?
If I accept a custom cert, but don't validate the key, I might as well use none, basically. That's the extent of my knowledge, I don't know what Certificate Transparency is doing, for example.
> The CA system has lots of issues. It would be a pretty big conspiracy if there were thousands of people that knew of something better and said nothing. But, there is absolutely no proof that anyone has any idea how to do better than the CA system. Do you know of such a system or have any evidence that someone else does?
> It would be a pretty big conspiracy
Exactly, so why do you expect that twitter sized post could it explain it convincingly?
> if there were thousands of people that knew of something better and said nothing
Ironically, it might be the ability to censor communication to suppress such voices, however hypothetical that is, that triggered the GP.
> But, there is absolutely no proof that anyone has any idea how to do better than the CA system.
PGP is used with key exchange in real live. I'm not using it, just arguing for the sake of the argument. It has problems, too, but "better" is not a binary value , except in the limited scope of the specific problem. PGP doesn't need root CAs.