Hacker News Reader

> or corrupting my stack pointer...

in that case, it will crash with a SIGSEGV sooner or later anyway

...or is being remotely exploited and it silently succeeds. Who wants that?

That is very unlikely. Crashing would happen 100% of the time though. Most people want that trade-off (meaning: If their browser would crash, they would switch to another one, even it was less secure).

Corrupting SP is part of almost every exploit and I can guarantee you that it is very likely (going to cause harm on your system). Try to pull Metasploit GIT repo to get some idea about thousands of payloads that do corrupt SP without crashing the host...

Yes, but how many of all cases of corrupted stack pointers are exploits?

Why would that matter? We're not trying to be secure against random cosmic rays. We're trying to be secure against attackers.

http://wondermark.com/406/

It matters because we're talking about letting the browser crash on all cases.

> We're trying to be secure against attackers.

We also want a browser that doesn't crash.

Stack pointer manipulation is the entry point for an extremely large subset of security issues.

Reply on news.ycombinator.com