RE: https://toot.cafe/@slightlyoff/116281285290733971
It's funny how Apple is doing both at the same time here:
a) proactively fighting browser engine monoculture, while at the same time
b) requiring browser engine monoculture.
🙂
RE: https://toot.cafe/@slightlyoff/116281285290733971
It's funny how Apple is doing both at the same time here:
a) proactively fighting browser engine monoculture, while at the same time
b) requiring browser engine monoculture.
🙂
@helge the reporting on DarkSword is incredibly sloppy.
Google has a more in depth analysis, with a lot more information on the specific versions of iOS that are affected.
TL;DR It doesn’t seem to affect 18.7.3 at least (might also not work on 18.7.2 given that CVE-2025-43520, which DarkSword uses, has been patched in .2).
https://cloud.google.com/blog/topics/threat-intelligence/darksword-ios-exploit-chain
@helge It's only funny if you accept the first one as true; it isn't:
https://infrequently.org/2022/06/apple-is-not-defending-browser-engine-choice/

Some folks claim that Apple's mandated inadequacy for browsers and their engines is somehow beneficial to the cause of ensuring a diverse pool of web engines. Nothing could be farther from the truth, but to understand why, we need to understand how browsers are funded. With that understanding, we can see that not only has Apple has starved its own browser team of resources, but has done grevious damage to Mozilla along the way.