Re: How to answer "Perl is not secure" objections?

You have to distinguish between perl (the compiler/interpreter) and Perl (the language).

As for the program, I'd like to point you to the Common Vulnerabilities and Exposures List, search for Products -> Perl (don't enter 'perl' in the search box, it will find 'properly' as well).

Now compare these results to other interpreters and virtual maschines.

As for the language: you don't have to mess with your memory on your own (like C), you have tainting, no insecure register_globals (or whatever that stuff is called in PHP).

Perl 6 in German

Comment on Re: How to answer "Perl is not secure" objections?

Replies are listed 'Best First'.
Re^2: How to answer "Perl is not secure" objections? by CountZero (Bishop) on Sep 07, 2007 at 17:05 UTC
13 vulnerabilties for product "Perl" since 1999 and the last one dates back from 2005! Compare this to PHP, which has 185 vulnerabiities since 2000, with the last one in April 2007. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]

Replies are listed 'Best First'.

Re^2: How to answer "Perl is not secure" objections?
by CountZero (Bishop) on Sep 07, 2007 at 17:05 UTC

Compare this to PHP, which has 185 vulnerabiities since 2000, with the last one in April 2007.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]