Hi Dmitry,
As you mention in your email, Adobe is interested in the Shadow DOM effort
and we will coordinate with you to understand better how/if/where we can
contribute.
Good luck with both the implementation and the standards work!
Kind regards,
Vincent.
Dmitry wrote:
Hi WebKit!
I wanted
: [webkit-dev] Timing attacks on CSS Shaders (was Re:Security
problems with CSS shaders)
On Fri, Dec 9, 2011 at 2:40 PM, Vincent Hardy
vha...@adobe.commailto:vha...@adobe.com wrote:
On Dec 7, 2011, at 7:29 PM, Adam Barth wrote:
On Wed, Dec 7, 2011 at 7:23 PM, Vincent Hardy
vha
On Dec 7, 2011, at 7:29 PM, Adam Barth wrote:
On Wed, Dec 7, 2011 at 7:23 PM, Vincent Hardy vha...@adobe.com wrote:
@chris
So I take back my statement that CSS Shaders are less dangerous than
WebGL. They are more!!!
It seems to me that the differences are:
a. It is easier to do
, 2011 at 2:40 PM, Vincent Hardy
vha...@adobe.commailto:vha...@adobe.com wrote:
On Dec 7, 2011, at 7:29 PM, Adam Barth wrote:
On Wed, Dec 7, 2011 at 7:23 PM, Vincent Hardy
vha...@adobe.commailto:vha...@adobe.com wrote:
@chris
So I take back my statement that CSS Shaders are less dangerous than
Hello,
@chris
So I take back my statement that CSS Shaders are less dangerous than WebGL.
They are more!!!
It seems to me that the differences are:
a. It is easier to do the timing portion of a timing attack in WebGL because it
all happens in a script and the timing is precise. With CSS
5 matches
Mail list logo
