Hacker News (curated)new | past | comments | ask | show | jobs| show hidden

Here's what apple (themselves) recommends to patch: https://support.apple.com/en-us/149555

Pretty much every developer on mac should probably run their patch.



You have to re-run that every time you do a software update btw

Per https://emudhra.we-have-a-problem.com/apple.html

> macOS 27.2, released on 26th October, did not fix the issue and undid the workaround that users had applied by hand, leaving them vulnerable again.


Apple’s handling of this has been a disgrace. It took 4 days before my iPhone and MacBook Pro got the CRL, and now I hear they have done this. Dreadful.

Apple, for the company that prizes itself on believing privacy is a human right, why are you failing your customers so badly on PKI management?


That’s not a ‘patch’, it’s several command lines you need to copy and execute, some optionally.

It’s completely insane to me that Apple didn’t script this with interactive prompts as needed, and non-interactive options for automatic installs.


This is such a Linux way to resolve the issue lol

* Unix way

First time I've seen AI-authored instructions from Apple. I guess it is hard for them to just post a new .pem because it could be MITM'd.

Safari (and other browsers) is safe. The issue is terminal tools such as curl and git

Why would it be more secure to post 4 manual commandline instructions than a single file?

I reposted this as it wasn't clear from previous comments with this URL that there's a patch that's worth running in there from Apple themselves

Why arent they just pushing this patch out on their security update channel?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact | github