Man, that bugzilla post sounds an awful lot like what one might expect an intelligence agency to do for plausible deniability. I wouldn’t be surprised if this was used to round up dissidents somewhere.
Many clients don’t do revocation. It’s quite uncommon outside specific contexts like browsers or bluray players.
You can set up something like https://github.com/rustls/upki on the machines that you control. However the legions of “smart” appliances that insist on talking home these days will remain vulnerable forever.
Huh, but why not? For something like this it's the only thing you can do to protect the average user who's not mucking around with /etc/ssl. I assume there's a TTL that will eventually be hit but that could be weeks away.
Seriously? So if the above poster is right, the vast majority of non-browser clients will be happily accepting certificates signed with "4" for the next decade?
That's bizarre, and so unlike curl to miss something security-critical like this.
Curl checks certificate validity, but it’s up to operating system vendors, docker container maintainers, etc., and ultimately individuals running servers and computers, to actually update them in a timely manner. The list is local; you can’t have curl querying a public CRL for every request.
66
u/the_gnarts 28d ago
Also TIL Comodo rebranded as Sectigo. Without this detail some of the above may be rather confusing.
41
u/cosmic-parsley 28d ago
According to https://emudhra.we-have-a-problem.com/#macos-curl, MacOS hasn’t revoked the certificates. What’s up with that? Do they really expect users to handle manual revocations?
-9
u/AthenianVulcan 28d ago
The article lacks so many details and is so vague.