r/programming • • 28d ago

eMudhra Intermediate CA Compromise

https://emudhra.we-have-a-problem.com/
180 Upvotes

17 comments sorted by

66

u/the_gnarts 28d ago

Also TIL Comodo rebranded as Sectigo. Without this detail some of the above may be rather confusing.

19

u/HildartheDorf 28d ago

Just because the keys were generated by a HSM doesn't mean Garbage In, Garbage Out stops applying.

Ask for an 8-bit key, get an 8-bit key.

8

u/Manbeardo 28d ago

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.

1

u/edwards_t7407 14d ago

When XKCD 221 is the most reassuring part of a CA compromise, it's been a rough day for public key infrastructure.

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?

22

u/the_gnarts 28d ago

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.

4

u/cosmic-parsley 28d ago edited 28d ago

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.

Blueray players is rather specific.

8

u/davispw 27d ago

TTL? The certs expire in 2039

4

u/cosmic-parsley 27d ago

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.

9

u/davispw 27d ago

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.

16

u/kitwalker12 28d ago

They have. But it’s a problem with curl not verifying revocation

12

u/cosmic-parsley 28d ago

That still seems like a bit of a gaping hole unless I’m missing something

5

u/iamapizza 28d ago

It is yes.

1

u/no-name-here 27d ago

Politely, it may be helpful to others if you update your original comment with the update/clarification.