3 ms·
I asked Paul Irish, Chome Developer relations: @paul_irish re http://bit.ly/kOZ7Lp http://bit.ly/kOZ7Lp - MSFT wrong? Security risk in Chrome/FF with WebGL? ht
by msy 15y ago
I asked Paul Irish, Chome Developer relations:
@paul_irish re http://bit.ly/kOZ7Lp http://bit.ly/kOZ7Lp - MSFT wrong? Security risk in Chrome/FF with WebGL?
http://twitter.com/#!/paul_irish/status/81492337108328448 http://twitter.com/#!/paul_irish/status/81492337108328448
@AlexGraul i think chrome's record in pwn2own is a good indicator of our commitment to security while delivering great features. :)
- tzs 15y agoNote he didn't actually answer the question.
- paulirish 15y agoI'm not at all an expert to handle details about the security of WebGL. I have no idea on that front. I do know Chrome and FF just fixed a timing attack vector where you could apparently intuit the content of a crossdomain image by interpreting what hues were based on it via the application of shaders. Which means hypothetically you could read text. Like a crazy-person's OCR.
- benatkin 15y agoOr like virtual Van Eck phreaking. http://en.wikipedia.org/wiki/Van_Eck_phreaking http://en.wikipedia.org/wiki/Van_Eck_phreaking