I 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 have a pretty clear memory of the JailbreakMe 2/3 bugs (which, for anyone else reading, were bugs that could be used from the web browser, and so were of the form "you click a link or have some evil iframe and are pwned") being fixed in six days (which I mentally cataloged as the minimum turnaround time Apple could muster).
If it is true the bug was present in iOS 11 and fixed in iOS 12 before being reintroduced in iOS 13, that might align with macOS 10.14 (≈ iOS 12) being unaffected.
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 reasonably fast or reliable internet connection.
I jailbroke for the first time in nearly a decade when unc0ver came out. It's actually pretty useful. I really love having the ability to use Flex on any app on my device.
[+] [-] saagarjha|5 years ago|reply
(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...)
[+] [-] saurik|5 years ago|reply
[+] [-] prvc|5 years ago|reply
[+] [-] KenanSulayman|5 years ago|reply
[+] [-] Flockster|5 years ago|reply
[+] [-] Wowfunhappy|5 years ago|reply
> 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?
[+] [-] 0x0|5 years ago|reply
[+] [-] saagarjha|5 years ago|reply
[+] [-] vmchale|5 years ago|reply
[+] [-] xerces8|5 years ago|reply
[+] [-] baggy_trough|5 years ago|reply
[+] [-] jmull|5 years ago|reply
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.
[+] [-] tuxone|5 years ago|reply
[+] [-] xerces8|5 years ago|reply
[+] [-] andarleen|5 years ago|reply
[deleted]
[+] [-] myko|5 years ago|reply
[+] [-] mangix|5 years ago|reply
[+] [-] based2|5 years ago|reply
and for macOs https://support.apple.com/en-us/HT211215
[+] [-] unknown|5 years ago|reply
[deleted]
[+] [-] s010c011ab|5 years ago|reply
[+] [-] paypks|5 years ago|reply
[deleted]