(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/return-of-the-ios-sa...)
This may also illustrate their priority to reintroduce the same bug and re-fix it at faster speeds to wow their fanbase. Or you know the priority may also be keeping the walled garden - walled? Also it might just be security response 101 - like every other major OS vendor out there depending on the bug. But yeah privacy and security for users that's a much nicer marketing pitch.
That's actually what I interpreted prvc's comment to be saying. But I guess I might have misinterpreted it.
My reading is that this bug could potentially allow apps to install rootkits. The speed of the fix tells me maybe it's being exploited that way right now in the wild.
BTW MacOS got the fix in record time too in spite of it being far less strictly walled than iOS. That supports my suspicion that this bug is being used in nasty ways.
> Available for: macOS High Sierra 10.13.6, macOS Catalina 10.15.5
That's interesting—did the bug exist on both 10.13 and 10.15, but not 10.14?
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 reasonably fast or reliable internet connection.
But generally the software industry has moved to a model where diffs are shunned and “recreate from scratch” is embraced for reasons that range from reproducibility to speed of development to architectural purity and everything in between.
Yes, and smaller updates is arguable better security for users because they'll actually update. A 3gig download and a 15 to 45 minute down time is a huge incentive to NOT update.
It works for iCloud content, too.
secondly, you can run this command on the machine you want to upgrade, to verify that it can see your Content Caching Server (it should report the local IP address of the machine you set up Content Caching on) "AssetCacheLocatorUtil"
Looks like if the machine is asleep it won't use it for a content cache, even if "wake for network access" is turned on. So a pretty useless feature if you have a machine that's allowed to sleep.
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.
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.
Software is more chaotic though. A small change in inputs can change behavior drastically, like stepping a tiny bit to the right on a branch of the Mandelbrot set. It's sometimes easier work, but often relatively counterintuitive.
I repeat: it's incompetence.
Like, shouldn't most high-end consumer devices include a dedicated update storage partition or flash area so that user storage is never impacted?
But back on topic: there are some devices that do include a specific partition for updates, but I don't think it's usually for user storage, but for "seamless updates": you install the OS to the other partition, reboot, and the partitions swap and you have a new OS up and running immediately. I actually doubt that any manufacturer would forgo not counting that as part of their user storage, unfortunately…
and for macOs https://support.apple.com/en-us/HT211215