Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
macOS 14 Sonoma firewall bug fixed (mullvad.net)
117 points by bluish29 on Sept 26, 2023 | hide | past | favorite | 12 comments


Once again submitting the bug report to HN gets you much better results than sending it to Apple


PR and legal teams and forums frequented by employees are the only way to short-circuit the corporate feedback layers.


Also direct email addresses harvested from GitHub (sometimes) and apparently also investor relations.

In some countries, if you're part of a retirement fund that owns stock in a company, you might get away with calling yourself an investor in a letter / email / phone call to investor relations. Nobody wants investors to be disgruntled, so if one asks for something and it's not a terrible imposition (think actually looking at a flagged customer instead of bouncing them from bot to script-following employee) many companies actually go for it and fulfill the request without much checking.


I don't doubt it. They definitely don't respond to radars or ack concerns even from partner groups in MA_NG.

Apple's concept of feedback is like Whitehouse petitions: ostensible appearance of engagement connected to the circular file. At least Netflix just has no feedback mechanism at all.


The real question is how such a major security related bug made it into the second public beta.

A company with Apple's resources should have extensive in-house automated and manual testing and validation, and basic firewall rule eval / VPN problems shouldn't be an issue that makes it this far.


> The real question is how such a major security related bug made it into the second public beta.

Does it matter? Isn't that the point of betas?


Beta still get 5% of the full release foot traffic...

I installed the beta 1 of Sonoma months ago (to do work on the widgets) and my mac was fully crashing once or twice a day. You could argue "how did this even make it to beta"... /shrug

My iMessage is still broken from the beta, the text gets displayed in a sub-frame 1/2 the size of the window for no reason at all. I can't seem to undo it.


I'm sure they do, but is that specific test case in their suite?


Based on?

You understand how betas work right?


It was in the release candidate.

It was in the betas, too, and they submitted it as a bug early on, and it wasn't fixed in any of the betas or the first release candidate. This is covered in the article.


But regardless, obivously none of us here have the slightest idea whether it was in the pipeline to be fixed anyways, or if it was because of HN.

It might have been HN, but it might not have been. (Surely other things have been fixed between RC and release without HN intervening.)


Release candidate means it could have gone out as a release. RC2 ended up being the release version.




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

Search: