StopBadware.org coalition calls on Apple to fix Safari ‘carpet bomb’ issue sooner than later
Tuesday, May 20, 2008 - 04:16 PM EDT"The Google-backed StopBadware.org coalition has called on Apple to rethink its stance on whether the Safari 'carpet bomb' issue reported by Nitesh Dhanjani constitutes a serious security risk," Ryan Naraine blogs for ZDNet.
"Dhanjani originally discovered than it is possible for a booby-trapped Web site to litter the user’s Desktop (Windows) or Downloads directory (~/Downloads/ in OSX) with executables masquerading as legitimate icons," Naraine reports.
"Apple has classified Dhanjani’s findings as more of an annoyance than a security risk that requires an immediate patch," Naraine reports.
"A source tells me that Apple will fix the issue in Safari 3.2, which is slated for release in the summer (September) this year," Naraine reports. "However, StopBadware.org, a non-profit managed by Harvard Law School’s Berkman Center for Internet & Society and Oxford University’s Oxford Internet Institute, wants Apple to create and distribute a fix to protect end users."
Full article here.
StopBadware.org's blog post on the subject here.
MacDailyNews Take: If what Naraine reports is true, Apple, why wait until September to fix what can be fixed today?


MDN:
- what is a carpet bomb?
- how is it invoked?
- how is one detected and stopped?
- how are false-positives avoided (whereby a user downloads lots of files, but it's mistaken for a carpet bomb)?
Software engineering is not a trivial thing. There's lots of factors to consider and lots of testing to be done.
Furthermore, why trust the September release as fact? Where's the proof?