Re: The CERT Oracle Secure Coding Standard for Java
On 5/28/2011 3:42 AM, Nasser M. Abbasi wrote:
On 5/27/2011 10:44 AM, rCs wrote:
The CERT Oracle Secure Coding Standard for Java has been completed and
is now ready for
https://www.securecoding.cert.org/confluence/display/java/The+CERT+Oracle+Secure+Coding+Standard+for+Java.
The CERT Oracle Secure Coding Standard for Java provides rules for
secure coding in the Java programming language. The goal of these
rules is to eliminate insecure coding practices that can lead to
exploitable vulnerabilities.
To review, you can create an account on the wiki and then post
comments to any of the pages, or respond directly to me.
Thanks,
rCs
I thought Java was already secured? i.e. no buffer overflow
problems like with C, and the sandbox thing for applets and
all of that. I did not know that Java can be not secured before.
Follow the link, read at least the introduction, and improve
your understanding.
But, would it be not better, if the language can be defined
so that these remaining security holes that can make it not
secure be closed at the language definition level, instead of
having set of rules, that one need to print out and hang on
the wall to look at while coding? This way the compiler job
to spot them, not the programmer. Much better.
"Security" is not a property of a language in isolation
(nor of any tool in isolation), but only in the context of
desired and undesired behaviors. The desires are not the
tool's, but the user's. The compiler cannot read your mind,
especially concerning matters you haven't thought about yet.
Power saws these days usually have blade guards and other
such security features to help their operators keep all their
fingers close at, er, hand. But no saw, no matter how safe,
will refuse to cut great gouges in the priceless antique table.
--
Eric Sosman
esosman@ieee-dot-org.invalid