full-disclosure - Guide To Secure System Development

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <21559A0D4CF8D511B51100065B38178BD300E4@mshyd2.hyd.deshaw.com>
From: Sandeep-Giri at deshaw.com (Giri, Sandeep)
Subject: Guide To Secure System Development

Interesting article..
I hope all will njoy reading this.

Abstract:
Increasingly incompetent developers are creeping their way into important
projects. Considering that most good programmers are pretty bad at security,
bad programmers with roles in important projects are guaranteed to doom the
world to oblivion. The author feels that a step toward washing himself clean
of responsibility is by writing this document. Checking your memcpy() and
malloc() calls have been lectured to death. It's not working. The approach
used by this document is to instead shame developers into producing better
systems. Enjoy.

http://m.bacarella.com/papers/secsoft/html/