Replies

This does get a little vague with open source, but when you're talking about a desktop, Perl and Ruby almost never come into the picture. To hype them as desktop exploit vectors is pure FUD (aside from the fact that it took a lot of deliberate effort just to get the vector to work on a target machine).

So we are ONLY talking about desktops now? What about the Army and their webservers? Think they may be running Ruby or Perl? So which is it...do you withdraw your desktops only comment or the Army uses Mac for a server?

the typical discussion I seem to have with you...you keep changing the target to fit your twisted logic, but if you step back you'll see that it's full of holes.

So we are ONLY talking about desktops now? What about the Army and their webservers? Think they may be running Ruby or Perl?

Not necessarily. But FYI the Army is running, as you'd have seen if you'd seen graphic on post 96, WebStar. With a little more searching you'll find they run PHP (also a Windows language).

If you tell me there's an exploit in PHP, then that's not OS X. If an exploit in PHP allows you to take advantage of an OS X exploit, then that's two different exploits. Even then, it would help if the exploit actually worked.

the typical discussion I seem to have with you...you keep changing the target to fit your twisted logic

It works for either. A desktop is likely to be running Perl only if the user is a developer. A web server is only going to be running Perl if that's their third-party language of choice. Either way, it's only on there by specific choice (not default), and it's Larry Wall's responsibility.