How Google set a trap for Pwn2Own exploit team

Re:How Google set a trap for Pwn2Own exploit team by growt on Saturday March 10, 2012 @10:02AM (#3687869)

one more reason to use flash-block. maybe chrome should play flash only after confirmation by default.

[ Parent | on HN ]

Re:How Google set a trap for Pwn2Own exploit team by tjoff on Saturday March 10, 2012 @07:25PM (#3689171)

I haven't seen a flash-block implementation in chrome that hinders execution of flash. Often the flash is able to load before it is blocked which kind of defeats the purpose (from a security standpoint). Or have I missed something?

[ Parent | on HN ]

Re:How Google set a trap for Pwn2Own exploit team by daeken on Saturday March 10, 2012 @08:28PM (#3689278)

If you enable click-to-play for plugins, it'll prevent it from loading whatsoever before you click it.

[ Parent | on HN ]

Re:How Google set a trap for Pwn2Own exploit team by tjoff on Sunday March 11, 2012 @02:17PM (#3690862)

Can't believe I didn't know about that. But I can't find it? (all I can find is that is supposed to be in about:flags) Is it available in stable chrome releases?

Edit: Never find what I'm looking for in chrome settings... It's in Options -> Under the hood -> Content settings... (or just chrome://settings/content ) and then you can enable click-to-play under plugins.

Thanks!

[ Parent | on HN ]