Be nice if they could patch a kernel bug in macOS with less than a 1.5GB download.
It might seem strange, but they are using a change/build/deploy mechanism designed to deliver updates to any and all parts of an OS across a range of hardware devices. I'm pretty sure the mechanism, from end-to-end, is complex, and providing an optimized path for small changes would require resources, introduce more risk, and come at the expense of something else. Sucks, though, for everyone who doesn't have a reason…
Apple patches CVE-2020-9859 (unc0ver)
41–50 of 79 posts
Re: Apple patches CVE-2020-9859 (unc0ver)
#42Earlier quoted context omitted.
It might seem strange, but they are using a change/build/deploy mechanism designed to deliver updates to any and all parts of an OS across a range of hardware devices. I'm pretty sure the mechanism, from end-to-end, is complex, and providing an optimized path for small changes would require resources, introduce more risk, and come at the expense of something else. Sucks, though, for everyone who doesn't have a reason…
I apologize if this is a stupid question, but, is there a reason they can't do a diff patch on the binary? Would it end up not introducing savings?
A private company can deliver two human beings alive to a point in space with millimeter precision. Meanwhile another can't deliver Operating Systems without gross bugs or smaller updates with binary diff patching.
Re: Apple patches CVE-2020-9859 (unc0ver)
#43Earlier quoted context omitted.
It might seem strange, but they are using a change/build/deploy mechanism designed to deliver updates to any and all parts of an OS across a range of hardware devices. I'm pretty sure the mechanism, from end-to-end, is complex, and providing an optimized path for small changes would require resources, introduce more risk, and come at the expense of something else. Sucks, though, for everyone who doesn't have a reason…
It's funny how rarely you see a reasonable response to a question about "why doesn't my software do X" on a site full of software developers.
Re: Apple patches CVE-2020-9859 (unc0ver)
#44Earlier quoted context omitted.
It might seem strange, but they are using a change/build/deploy mechanism designed to deliver updates to any and all parts of an OS across a range of hardware devices. I'm pretty sure the mechanism, from end-to-end, is complex, and providing an optimized path for small changes would require resources, introduce more risk, and come at the expense of something else. Sucks, though, for everyone who doesn't have a reason…
I work on a ship part of the year. Satellite internet shared between 50 people. These Apple updates would saturate the network and grind it to a halt before we started blocking them on the firewall. iMessage got caught in the crossfire and now sometimes works and sometimes doesn't.
https://support.apple.com/guide/mac-help/what-is-content-cac...
It works for iCloud content, too.
Re: Apple patches CVE-2020-9859 (unc0ver)
#45Earlier quoted context omitted.
It's funny how rarely you see a reasonable response to a question about "why doesn't my software do X" on a site full of software developers.
I would venture to guess that often it is because the answer is 'business reasons', which is often not reasonable.
beyond that, if decisions others make often seem not reasonable, it's probable that you disagree with the values on which those decisions are based, rather than those business decisions being without reason. you may be entirely justified in your disagreement, but that's a different animal from unreasonableness.
also, most business decisions are made under uncertainty and with imperfect information (under-informed), and many can seem less reasonable in hindsight as a result.
in any case, it's really unlikely that decision makers are chaos monkeys even if it seems that way from your vantage point.
Re: Apple patches CVE-2020-9859 (unc0ver)
#46Be nice if they could patch a kernel bug in macOS with less than a 1.5GB download.
It might seem strange, but they are using a change/build/deploy mechanism designed to deliver updates to any and all parts of an OS across a range of hardware devices. I'm pretty sure the mechanism, from end-to-end, is complex, and providing an optimized path for small changes would require resources, introduce more risk, and come at the expense of something else. Sucks, though, for everyone who doesn't have a reason…
Re: Apple patches CVE-2020-9859 (unc0ver)
#47Earlier quoted context omitted.
That's a bit before I was using iOS, so I'll take your word on that one ;) AFAIK some system call filtering went into WebKit at some point to make this specific exploit unreachable from the web process, so I guess you could call it "less severe" than JailbreakMe was. That being said, I guess "zero day affecting all current devices" is probably good enough to get priority. (FWIW, heavily publicized non-security bugs o…
That syscall filtering still exists and broke a build for three or four days recently.
Re: Apple patches CVE-2020-9859 (unc0ver)
#48Earlier quoted context omitted.
You didn't communicate that. There is no "download" to delete on iOS (and derivatives) and it's managed by the system on macOS. It's not a small delta when it should be tiny (100 MiB), that eats up data plan and storage.
You can delete a downloaded (but not installed) update on iOS.
Re: Apple patches CVE-2020-9859 (unc0ver)
#49I think this might be the fastest patch of a security issue affecting Apple's operating systems, ever. Aside from *.0.1 releases that fixed critical bugs with core features in new OSes, has anything been patched this fast? (I'm also obligated to post that the bug that this fixes is not new; it was discovered back in iOS 11, fixed, and Apple reopened it in an iOS 13 update: https://www.synacktiv.com/posts/exploit/retu…