Earlier quoted context omitted.
WebKit code execution against Chrome is also likely to work (in modified form, but same basic exploit) against desktop or mobile Safari. Desktop Safari sandbox escape is likely to be completely different from MobileSafari sandbox escape. And in all three cases, the sandbox escape is the harder part. So that logic does not explain to me why people are going after Chrome but not Safari. I honestly don't know why it is.…
Yeah, the WebKit exploit will work effectively unmodified on Safari. And the sandbox escape used against Chrome on Windows was a kernel bug in surface that can't be turned of from user-space (or really at all on Win7). Also, they softened the target quite a bit by using 32-bit Win7 for the contest, rather than 64-bit Win8 (or even 64-bit Win7). As for why no one's targeting Safari, I think it's simple market forces a…
My theory is that not much research has been done yet on breaking the WebProcess sandbox. Which makes me sad.