Jump to content

CSS Shaders Security: Revision history

View logs for this page

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

curprev 15:0115:01, 19 April 2012‎ Vhardy talk contribs‎ 22,288 bytes −5‎ →‎No access to rendered content texture in fragment shader
curprev 15:0015:00, 19 April 2012‎ Vhardy talk contribs‎ 22,293 bytes +115‎ →‎Method H: Tainting shader code branches
curprev 14:5814:58, 19 April 2012‎ Vhardy talk contribs‎ 22,178 bytes 0‎ →‎Method H: Tainting shader code branches
curprev 14:5714:57, 19 April 2012‎ Vhardy talk contribs‎ 22,178 bytes −25‎ →‎No access to rendered content texture in fragment shader

curprev 13:3413:34, 15 March 2012‎ Vhardy talk contribs‎ 12,675 bytes +191‎ →‎Method H: Tainting shader code branches
curprev 02:1102:11, 15 March 2012‎ Vhardy talk contribs‎ 12,484 bytes +245‎ →‎Method H: Tainting shader code branches
curprev 02:0802:08, 15 March 2012‎ Vhardy talk contribs‎ 12,239 bytes +613‎ No edit summary

curprev 13:5813:58, 1 February 2012‎ Vhardy talk contribs‎ 9,357 bytes +1,627‎ →‎Method A: Implementations should make shaders run in a fixed amount of time

curprev 00:5300:53, 17 December 2011‎ Vhardy talk contribs‎ 7,730 bytes −2‎ No edit summary

curprev 21:2621:26, 16 December 2011‎ Vhardy talk contribs‎ 7,732 bytes −2‎ No edit summary
curprev 21:1921:19, 16 December 2011‎ Vhardy talk contribs‎ 7,734 bytes −52‎ →‎Introduction: Why do CSS shaders introduce new security concerns?
curprev 21:1821:18, 16 December 2011‎ Vhardy talk contribs‎ 7,786 bytes −1‎ →‎Method B: Cross Origin Domains Restrictions
curprev 21:1821:18, 16 December 2011‎ Vhardy talk contribs‎ 7,787 bytes +33‎ →‎Introduction: Why do CSS shaders introduce new security concerns?

Retrieved from "https://www.w3.org/Graphics/fx/wiki/CSS_Shaders_Security"