Secure Coding: by author
81 messages
starting Nov 14 04 and
ending Nov 12 04
Date index |
Thread index |
Author index
Aleksander P. Czarnowski
RE: How do we improve s/w developer awareness? Aleksander P. Czarnowski (Nov 14)
Brian Utterback
Re: How do we improve s/w developer awareness? Brian Utterback (Dec 02)
Crispin Cowan
Choices Crispin Cowan (Nov 16)
Re: Re: DJB's students release 44 poorly-worded, overblown advisories Crispin Cowan (Dec 20)
Re: Re: DJB's students release 44 poorly-worded, overblown advisories Crispin Cowan (Dec 22)
Re: Re: DJB's students release 44 poorly-worded, overblown advisories Crispin Cowan (Dec 22)
Re: [Fwd: DJB's students release 44 *nix software vulnerability advisories] Crispin Cowan (Dec 21)
Dana Epp
Re: Secured Coding Dana Epp (Nov 13)
Re: Exploiting Software: How to Break Code Dana Epp (Nov 11)
Re: How do we improve s/w developer awareness? Dana Epp (Nov 12)
David A. Wheeler
New article: "Secure programmer: Call Components Safely" David A. Wheeler (Dec 28)
Re: How do we improve s/w developer awareness? David A. Wheeler (Dec 03)
David Crocker
RE: Secured Coding David Crocker (Nov 14)
der Mouse
Re: How do we improve s/w developer awareness? der Mouse (Dec 02)
Re: [Fwd: DJB's students release 44 *nix software vulnerability advisories] der Mouse (Dec 22)
dtalk-ml
Re: DJB's students release 44 poorly-worded, overblown advisories dtalk-ml (Dec 20)
Florian Weimer
Re: Secured Coding-Intellectual Property Florian Weimer (Nov 19)
Gadi Evron
[Fwd: DJB's students release 44 *nix software vulnerability advisories] Gadi Evron (Dec 18)
Re: Secured Coding Gadi Evron (Nov 17)
Gary McGraw
BSI: penetration testing article Gary McGraw (Dec 09)
RE: How do we improve s/w developer awareness? Gary McGraw (Nov 12)
Re: Exploiting Software: How to Break Code Gary McGraw (Nov 11)
RE: How do we improve s/w developer awareness? Gary McGraw (Nov 12)
RE: Exploiting Software: How to Break Code Gary McGraw (Nov 11)
Static analysis: Building Security In #5 Gary McGraw (Oct 26)
George Capehart
Re: How do we improve s/w developer awareness? George Capehart (Dec 01)
Re: How do we improve s/w developer awareness? George Capehart (Nov 29)
graham . coles
Re: How do we improve s/w developer awareness? [Virus Checked] graham . coles (Dec 02)
Greenarrow 1
Secured Coding Greenarrow 1 (Nov 13)
Fw: Secured Coding Greenarrow 1 (Nov 14)
Exploiting Software: How to Break Code Greenarrow 1 (Nov 10)
Secured Coding-Intellectual Property Greenarrow 1 (Nov 19)
Eweek Article on Secured Coding Greenarrow 1 (Dec 14)
Re: How do we improve s/w developer awareness? Greenarrow 1 (Nov 29)
Gunnar Peterson
Re: Secured Coding Gunnar Peterson (Nov 13)
Re: How do we improve s/w developer awareness? Gunnar Peterson (Nov 11)
Design for failure Gunnar Peterson (Dec 15)
Re: How do we improve s/w developer awareness? Gunnar Peterson (Nov 12)
Re: How do we improve s/w developer awareness? Gunnar Peterson (Nov 12)
Jeff Williams
Re: How do we improve s/w developer awareness? Jeff Williams (Nov 12)
Jose Nazario
Former cybersecurity czar: Code-checking tools needed Jose Nazario (Dec 03)
interesting articles on secure coding Jose Nazario (Nov 30)
Julie Ryan
CFP: The 9th Colloquium for Information Systems Security Education Julie Ryan (Dec 13)
OT: Research in CIIP Julie Ryan (Nov 09)
karger
Re: DJB's students release 44 poorly-worded, overblown advisories karger (Dec 22)
Re: Re: DJB's students release 44 poorly-worded, overblownadvisories karger (Dec 22)
Kenneth R. van Wyk
eSecurityPlanet article on Fortify source code scanner Kenneth R. van Wyk (Nov 22)
On SC-L's first anniversary Kenneth R. van Wyk (Nov 23)
eWeek articles on Software Security Kenneth R. van Wyk (Dec 20)
How do we improve s/w developer awareness? Kenneth R. van Wyk (Nov 11)
Bug 259708: A human perspective Kenneth R. van Wyk (Oct 06)
Re: Open Source failure analysis tool released for Linux Kenneth R. van Wyk (Oct 15)
Programming Legends Debate .Net, J2EE Kenneth R. van Wyk (Oct 30)
Administrivia: Thanks for the input and happy holidays Kenneth R. van Wyk (Dec 15)
Open Source failure analysis tool released for Linux Kenneth R. van Wyk (Oct 15)
ljknews
Re: How do we improve s/w developer awareness? ljknews (Nov 12)
Re: DJB's students release 44 poorly-worded, overblown advisories ljknews (Dec 20)
Re: How do we improve s/w developer awareness? ljknews (Nov 12)
Re: Open Source failure analysis tool released for Linux ljknews (Oct 15)
Re: [Fwd: DJB's students release 44 *nix software vulnerability advisories] ljknews (Dec 22)
Re: Re: DJB's students release 44 poorly-worded, overblown advisories ljknews (Dec 22)
Re: How do we improve s/w developer awareness? ljknews (Nov 11)
RE: [Fwd: DJB's students release 44 *nix software vulnerability advisories] ljknews (Dec 20)
Michael S Hines
RE: How do we improve s/w developer awareness? Michael S Hines (Dec 02)
M Taylor
Re: How do we improve s/w developer awareness? M Taylor (Nov 12)
Nick Murison
Re: Choices Nick Murison (Nov 16)
Re: Choices Nick Murison (Nov 16)
Re: How do we improve s/w developer awareness? Nick Murison (Nov 16)
Paco Hope
Re: DJB's students release 44 poorly-worded, overblown advisories Paco Hope (Dec 20)
Re: How do we improve s/w developer awareness? Paco Hope (Nov 11)
Re: Re: DJB's students release 44 poorly-worded, overblownadvisories Paco Hope (Dec 20)
Peter Amey
RE: How do we improve s/w developer awareness? Peter Amey (Dec 05)
Peter G. Neumann
Re: Secured Coding Peter G. Neumann (Nov 15)
robert
Web Application Security Consortium 'Guest Articles' Call for Papers robert (Dec 06)
Shea, Brian A
RE: [Fwd: DJB's students release 44 *nix software vulnerability advisories] Shea, Brian A (Dec 20)
RE: How do we improve s/w developer awareness? Shea, Brian A (Dec 02)
Wall, Kevin
RE: Exploiting Software: How to Break Code Wall, Kevin (Nov 11)
RE: How do we improve s/w developer awareness? Wall, Kevin (Nov 12)
RE: Design flaw in Lexar JumpDrive Wall, Kevin (Sep 30)
Yousef Syed
RE: Secured Coding Yousef Syed (Nov 15)
Re: How do we improve s/w developer awareness? Yousef Syed (Nov 12)