News for hackers. Stuff that matters.

A comment on How Google set a trap for Pwn2Own exploit team. Parent comment

Re:How Google set a trap for Pwn2Own exploit team by sek on Saturday March 10, 2012 @09:09AM (#3687792)
It is not their program, they can't do much about it and everyone else has also Flash installed. In reality this vulnerability is present on 99% of all devices and not just chrome. Compare Flash having a sandbox, to all the other browsers who don't have one. In the end, Chrome is by far the most secure browser.
[ Parent | on HN ]
Re:How Google set a trap for Pwn2Own exploit team by tvon on Saturday March 10, 2012 @10:46AM (#3687938)
They can very easily stop including the Flash player with every version of Chrome. It seems like that would solve some obvious security problems.

This is hardly an impossible feat.

[ Parent | on HN ]
Re:How Google set a trap for Pwn2Own exploit team by justinschuh on Saturday March 10, 2012 @11:23AM (#3688027)
The problem is that an outdated, unsandboxed version of Flash is installed on almost every desktop system. So, if we stopped including Flash, the vast majority of our users would be more vulnerable than they already are. That's why we're shipping a current version with a sandbox that's at least as good as IE low integrity mode, and we're also wrapping up work on a version of Flash that uses the full Chrome sandbox.
[ Parent | on HN ]
Re:How Google set a trap for Pwn2Own exploit team by tvon on Saturday March 10, 2012 @11:54AM (#3688090)
> The problem is that an outdated, unsandboxed version of Flash is installed on almost every desktop system.

Don't use it.

> So, if we stopped including Flash, the vast majority of our users would be more vulnerable than they already are.

Prompt to use a specific Flash when the user requests it.

[ Parent | on HN ]
Re:How Google set a trap for Pwn2Own exploit team by harshreality on Saturday March 10, 2012 @11:51PM (#3689584)
If Chrome didn't bundle a better version of flash, and didn't use the system version of flash, users would find out that Chrome is "broken" the first time they got to a page with flash. Then they would switch to Firefox, Opera, or even IE if they're on windows. Those browsers do use the system flash plugins. Who wins? Not security.

If Chrome didn't bundle a modified version, and prompted the user to select a Flash version, the only one they could offer would be the system one.

Unless you're saying that the Chrome team should go to all the effort to build a custom version of flash, but only deliver it to Chrome browsers when the user specifically requests it? That strategy seems DOA from a cost/benefit analysis perspective.

[ Parent | on HN ]