Linked by Thom Holwerda on Thu 19th Mar 2009 06:44 UTC, submitted by Moulinneuf
Privacy, Security, Encryption As he had already predicted, cracker Charlie Miller has won the PWN2OWN contest by cracking Safari and Mac OS X within seconds of the start of the competition. "It took a couple of seconds. They clicked on the link and I took control of the machine," Miller said after his accomplishment. He took home the USD 10000 prize, as well as the MacBook he performed the exploit on. Internet Explorer 8 fell a while later by cracker Nils, who also cracked Safari and Firefox after being done with IE8.
Permalink for comment 353854
To read all comments associated with this story, please click here.
RE: Comment by Hakime
by Thom_Holwerda on Thu 19th Mar 2009 08:24 UTC in reply to "Comment by Hakime"
Member since:

BS, his job is to find security holes, he surely spend plenty of time to find this one, saying that he did this in x or y second for sensationalism does not make any sense as he had tested before if the exploit works. The only thing that he needed was someone to click where he wanted it.

I said that he had cracked Safari within seconds of the competition. This is 100% fact, and there's nothing sensationalistic about it. It would be sensationalism if I had written something like "Safari Cracked within Seconds, Apple Most Insecure Company EVARR!!!"

But I didn't. This article is simply a lineup of facts. Like it or not. As usual, you are trying to shoot the messenger.

You make is it sound that Safari fell first and therefore it is less secure but the fact is that IE or Firefox fell exactly in the same manner, regardless who performed the exploit first.

Why is it always the messenger shooting with you Apple folk? I didn't say ANYTHING about who is less secure than the other! You are just making stuff up now.

This is a simple listing of facts of how the contest went. That's all. I can't help it that your pet company's browser was the first to fall again. Only with Apple fans can journalists/bloggers be blamed for a possible Cupertino screw up.

Humm, the flaw in Safari is probably in webkit, Chrome is probably also affected.

Doesn't have to be WebKit, but could be.

Edited 2009-03-19 08:32 UTC

Reply Parent Score: 6