5,164 karma · joined July 13, 2008
google chrome. web performance.
the web is the platform.
https://paul.irish
> Layering. That is an important word.
Layering is also the key to the (silly but also sometimes good-looking) effects from my text shadow project from 14yrs ago: https://paulirish.github.io/mothereffingtextshadow/
Settings Sync launched ~a year ago and requires being signed into a Google account, plus consent. https://developer.chrome.com/docs/devtools/customize#sync
eieio: your link to Juice it Or Lose It makes me so happy. For a decade I point people to that presentation. It's just perfect. Our easter egg is could afford some more juice though.. I might yoink some of your code. :) great stuff.
The treemap library was authored by evmar, chrome OG who's also in this thread.
But it does expose itself as a custom HID device! This project uses connects to all the StreamDeck models over WebHID. https://github.com/petele/StreamDeck-Meet
So I think the driver paranoid are actually in a decent spot.
My understanding is that the theory of this attack was introduced with Spectre. iLeakage adds enough research to create a working proof-of-concept, plus acknowledgment that, as of last year, it wasn't addressed in Safari.
More on site isolation (the functionality that mitigates these attacks):
https://w3c.github.io/webappsec-post-spectre-webdev/ https://www.chromium.org/Home/chromium-security/site-isolati... https://blog.chromium.org/2021/03/mitigating-side-channel-at...
> That is, while the speculative JavaScript sandbox escape is still possible, an attacker becomes limited to reading their own address space and therefore their own data. Finally, at the time of writing, Apple’s patch is publicly available [57] and is implemented in Safari Technology Preview versions 173 and newer [58].
[57] is https://github.com/WebKit/WebKit/pull/10169. At the bottom of it, an engineer continues to link ongoing hardening patches for window.open() + process isolation.
Anyone know observability software are they using to visualize the GIT_TRACE details? (Or is the assumption that the UI is Olly as well?)