4 ms·
Apparently this was already patched in the previous macOS security update, but Apple updated the documentation for it with additional references to this bug onl
by 0x0 8y ago
Apparently this was already patched in the previous macOS security update, but Apple updated the documentation for it with additional references to this bug only just today. I've seen them do these documentation updates a few times now, is that a recent thing? Isn't it kind-of breaking embargoes if a binary security update goes out weeks before the vulnerability is documented in public? Not sure if it's a good or bad thing... happy to be already protected, but concerned about installing updates which aren't fully documented on release and which might let bad guys discover issues early?
- duskwuff 8y ago> Isn't it kind-of breaking embargoes if a binary security update goes out weeks before the vulnerability is documented in public? Sort of. But it's a balancing act -- if you delay the release of a fix until the day of disclosure, users are all vulnerable to a known exploit until they patch. If you release a patch before public disclosure, chances are much better that users will update before the vulnerability is disclosed, either officially or through reverse-engineering of the patch.