Re:What should every programmer know about security?
by ArbitraryLimits on Tuesday May 08, 2012 @12:42PM
(#3944504)
> People who write insecure code, when the language makes it just as easy to write secure code, are to blame for insecure code
We're not discussing who's to blame, we're discussing whether there's anything to assign blame for.
Re:What should every programmer know about security?
by chromatic on Tuesday May 08, 2012 @02:03PM
(#3945018)
Can you name a practical language in which it's not possible, by default, to perform an unsafe operation with untrusted user input?
I can easily use Haskell's type system to disallow the use of UnsafeUserInput in my database abstraction layer, but that requires me to use my types pervasively and correctly.
Re:What should every programmer know about security?
by SamReidHughes on Thursday May 10, 2012 @01:51AM
(#3952058)
The question is not whether it is POSSIBLE.
... only if you use the insecure open form. The secure open form has been available and recommended since the release of Perl 5.6.0 in March 2000--twelve years ago.
People who write insecure code, when the language makes it just as easy to write secure code, are to blame for insecure code.