points by truelson 1 day ago | 0 comments
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.
[–] gamer191 1 day ago
[–] Arbortheus 1 day ago
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?
[–] Recurecur 1 day ago
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.
[–] unfitted2545 1 day ago
This is such a Linux way to resolve the issue lol
[–] dewey 1 day ago
* Unix way
[–] idkeickeixkeidj 9 hours ago
No, no. They’re right. It’s a very “Linux” thing to do. Applies to Unix as well? Yes. But it is most definitely what one comes to expect of Linux, not Mac.
[–] dewey 9 hours ago
I get it, I was just being pedantic ;)
[–] LeoPanthera 1 day ago
A script to automate this. https://gist.github.com/DavidCWGA/a5d09105371f734ccc7b0693a7...
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.