The following patch adds a USE flag for net-libs/webkit-gtk-1.1.10 to enable or disable JavaScript JIT (enabled by default). I'm not sure if this flag should be arch-dependant: currently JIT is availabe on x86 only, but more archs to come (amd64 at least). --- net-libs/webkit-gtk/webkit-gtk-1.1.10.ebuild 2009-09-29 04:06:21.000000000 +0800 +++ net-libs/webkit-gtk/webkit-gtk-1.1.10.ebuild 2009-09-30 17:25:51.000000000 +0800 @@ -15,7 +15,7 @@ SLOT="0" KEYWORDS="alpha amd64 ~ia64 ~ppc ~sparc x86 ~x86-fbsd" # geoclue -IUSE="coverage debug doc gnome-keyring +gstreamer pango" +IUSE="coverage debug doc gnome-keyring +gstreamer +jit pango" # use sqlite, svg by default RDEPEND=" @@ -91,6 +91,10 @@ myconf="${myconf} --with-font-backend=freetype" fi + if use !jit; then + myconf="${myconf} --enable-jit=no" + fi + econf ${myconf} }
(In reply to comment #1 here: https://bugs.gentoo.org/show_bug.cgi?id=287046 ) > Why? Some more background info would be nice. JIT requires executable stack pages, and any process performing JavaScript on hardened kernels will require to run with PAX_MPROTECT disabled. This may allow easier code execution exploits to work (without the need in pure ret2libc-style stack preparations, that is harder). Apart from that the JIT itself can be vulnerable.
*** This bug has been marked as a duplicate of bug 285792 ***
Sorry for bugzie spam. I decided to open two bugs.
iirc there is no such flag in 1.1.15.2. Closing wontfix.