On Aug 21, 2009, at 12:18 PM, Brad Andrews wrote:
This brings up a great point. How can we grade a program's security
level? Is it just a checkoff list? Which elements should be in
that checkoff list?
You may be interested in reading:
Teaching Secure Programming
IEEE Security and
Folks, I've been forwarding select messages from this listserv to my
nephews, who are undergrads in CS at some fairly reknown
universities, which shall remain nameless cause it would embarrass
the heck out of them to have the following sentiment aired..
Begin forwarded message:
>
> ya,
So, if software is dependably bad and can dependably be counted on to
fail, it's secure?
Especially if it resists attempts to compromise such dependability?
On Jul 15, 2006, at 3:27 PM, Goertzel Karen wrote:
> I've been struggling for a while to synthesise a definition of
> secure software
