I've seen the details, and I'm angry with the reporting. The problem is not Perl. The problem is undereducated Perl Programmers.{sigh}
We experts can repeat over and over "use taint mode" and "don't let data become code", but if people don't follow the rules, Perl gets smeared as a result. "perldoc perlsec" covers quite a bit of this, and I've also written about Perl security frequently in my columns, such as "Computing Securely", and "Avoiding SQL Injection Attacks".
If anything, the problem is that Perl is too easy to code, and too easy to do something dangerous, so casual programmers can write sophisticated code without also learning about basic rules of dealing with untrusted data.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
In reply to Re: Attack on Perl or Perl's need better PR (again)
by merlyn
in thread Attack on Perl or Perl's need better PR (again)
by wazoox
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |