3 ms·
It's could be unfixable without a significant performance penalty, but at minimum they could make safari do proper process isolation like every other browser do
by sebzim4500 2y ago
It's could be unfixable without a significant performance penalty, but at minimum they could make safari do proper process isolation like every other browser does.
- School-Cotton 2y agoI could easily imagine such a refactor of Safari taking more than 90 days even if Apple made it the highest possible priority.
- goldsteinq 2y agoThe bug is open since 2018, so clearly they don’t actually care about that. https://bugs.webkit.org/show_bug.cgi?id=184466 https://bugs.webkit.org/show_bug.cgi?id=184466
- School-Cotton 2y agoRight, but that was before they knew about this exploit. My point was that even if they decided they needed to urgently switch to a multiprocesses architecture because it's the only way to mitigate this exploit, they might not be done yet.
- goldsteinq 2y agoThis class of attacks is not new. Spectre demonstrated this possibility in 2018, and Apple was previously targeted by speculation attacks, e.g. https://gofetch.fail/ https://gofetch.fail/ or https://ileakage.com/ https://ileakage.com/.