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

in reply to How to answer "Perl is not secure" objections?

'Perl has bindings into OS calls that bypass OS security'

That sentence makes no sense at all. The 'bindings' Perl has to 'OS call's (read: system calls) are subject to all the normal security restrictions the OS imposes. Regardless of whether you program in Shell, Perl, Java, C or whatever (well, perhaps not Logo), you will be able to access these system calls, subject to the OS's restrictions. So it all comes down to the question of "is your OS secure" and has nothing at all to do with the programming language chosen.

All dogma is stupid.

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

Replies are listed 'Best First'.
Re^2: How to answer "Perl is not secure" objections? by radiantmatrix (Parson) on Sep 07, 2007 at 16:09 UTC
Yes, I know it's silly. The question is how to tell manager^3, since he won't just take my word for it. Saying "nuh uh" isn't really sufficient. <–radiant.matrix–> Ramblings and references The Code that can be seen is not the true Code I haven't found a problem yet that can't be solved by a well-placed trebuchet	[reply]

In Section Seekers of Perl Wisdom