logoalt Hacker News

chrisweekly • yesterday at 12:37 PM • 12 replies • view on HN

Right, so it's not just git, it's a bunch of system-provided utilities; macOS trusts bad certs, and these utils that trust the OS are affected. I use homebrew for my git and curl but haven't yet checked to confirm whether that matters here. Kind of outrageous that Apple's guidance is to edit the cert chain manually, and to expect that subsequent OS updates may revert your mitigation, reintroducing the vulnerability (as happened at least once so far).


Replies

stingraycharles • yesterday at 2:07 PM

To be honest, git deferring to the OS is the right thing to do. It's macOS that's the problem, not git.

"Ten days later, macOS and all applications that rely on it still trust the compromised eMudhra certificates" would have been a better title.

➕ show 9 replies
woodruffw • yesterday at 2:43 PM

Homebrew ships its own CA bundle so its own curl, etc. are not affected. But the system versions of those tools will continue to be affected until Apple patches their own bundle.

Edit: Git is still affected, we're fixing that now.

(Source: I am one of Homebrew’s maintainers.)

➕ show 4 replies
Fatnino • yesterday at 3:19 PM

Why are we ok with Apple or Microsoft or Mozilla deciding on a wide selection is CAs for us to trust?

I understand why they originally let each CA in, but it's definitely not one size fits all users.

A user in the US does not need to trust a Turkish CA the same way a user in Turkey does.

There needs to be an easy way for end users to personally drop trust of CAs they don't need and have that decision respected and remembered.

➕ show 7 replies
undersuit • yesterday at 7:13 PM

I noticed a machine of my was using a Chinese mirror for Debian apt. Switching to the US apt source brought in updates to cacerts and libbrotli. Not trying to insinuate anything, my mirror was just outdated, and yours (plural) could be too.

kridsdale1 • yesterday at 4:16 PM

I asked codex “find out if this Mac is still trusting that bad cert and remediate if so”. I got a few commands out of it to run myself with sudo, and now I’m good.

Thanks for being on the ball, Apple.

➕ show 1 reply
probe_user • yesterday at 4:16 PM

Second probe: confirming the fixed comment path resolves a parent comment correctly.

probe_user • yesterday at 4:15 PM

[flagged]

andrewmutz • yesterday at 2:42 PM

Apple gets a free pass on this website. If Google or Microsoft did the same thing, the torches and pitchforks would be out.

But instead the Apple fanboys will be out in force to tell us why actually its a good thing for Apple to leave parts of the OS insecure.

➕ show 6 replies