241–250 of 365 posts
> As pointed out by iLeakage, Safari lacks Site Isolation Well I'm shocked, for such a company that promotes security and privacy, apple not having put site isolation into safari seems amateurish.
Earlier quoted context omitted.
> Individuals could choose a "secure" browser or browser mode that provides increased protection from such attacks or a "compatible" one that is less likely to break old websites. And then we get thousands of posts whining about Safari being broken because it is "not like Chrome" and developers moaning that their unsafe pet API is not supported. Web developers are never going to play ball.
idunno, as a professional web dev since 1998, I don't understand why Google, Apple and Mozilla are trying so hard to make the web browser like a complete OS (I technically understand why, I just think it's ridiculous). The amount of obscure APIs being added just boosts the surface area for vulnerabilities and makes low-resource web browsing nearly impossible. You either get "a web browser that works" or "a web browse…
There's an obscure use case for this called "Watching Video"
For any yung'uns seeing this for the first time, the spectre and meltdown attacks (and accompanying papers) are worth reading. https://spectreattack.com/
Is it bad that I disable spectre mitigations on all my PCs to get a free double-digit-% performance boost?
Earlier quoted context omitted.
Have you noticed how often people complain Chrome uses too much memory?
Because long-inactive tabs should go to sleep. If Chrome itself is not aggressive enough, try the "Auto Tab Discard" extension.
Safari on the other hand doesn't even have Tab Sleep for whatever reason.
Seems like speculative execution is just fundamentally insecure. With SPECTRE/MELTDOWN mitigations, doesn't CPU performance drop below the same CPU performance with no branch prediction at all? Should we move back to CISC? Or maybe VLIW?
Can browser side channel attacks be made less effective by running another compute/branch heavy process?
Earlier quoted context omitted.
The permanent solution to the flaw is either a hardware/OS-side fix (i.e. disabling this particular kind of speculation via a chicken bit, if there is one), or Safari implementing site isolation in the same way Chrome and Firefox are already doing. But as the former might well be impossible (at least without ruining performance or requiring a hardware swap), and the latter might take a while, websites should still ta…
> But as the former might well be impossible (at least without ruining performance or requiring a hardware swap), and the latter might take a while, According to the site they informed Apple in May 2024. Should that not have been enough time?