Secure Coding: by date

81 messages starting Sep 30 04 and ending Dec 28 04
Date index | Thread index | Author index


Thursday, 30 September

RE: Design flaw in Lexar JumpDrive Wall, Kevin

Wednesday, 06 October

Bug 259708: A human perspective Kenneth R. van Wyk

Friday, 15 October

Open Source failure analysis tool released for Linux Kenneth R. van Wyk
Re: Open Source failure analysis tool released for Linux ljknews
Re: Open Source failure analysis tool released for Linux Kenneth R. van Wyk

Tuesday, 26 October

Static analysis: Building Security In #5 Gary McGraw

Saturday, 30 October

Programming Legends Debate .Net, J2EE Kenneth R. van Wyk

Tuesday, 09 November

OT: Research in CIIP Julie Ryan

Wednesday, 10 November

Exploiting Software: How to Break Code Greenarrow 1

Thursday, 11 November

Re: Exploiting Software: How to Break Code Dana Epp
RE: Exploiting Software: How to Break Code Wall, Kevin
Re: Exploiting Software: How to Break Code Gary McGraw
RE: Exploiting Software: How to Break Code Gary McGraw
How do we improve s/w developer awareness? Kenneth R. van Wyk
Re: How do we improve s/w developer awareness? ljknews
Re: How do we improve s/w developer awareness? Gunnar Peterson
Re: How do we improve s/w developer awareness? Paco Hope

Friday, 12 November

Re: How do we improve s/w developer awareness? Yousef Syed
Re: How do we improve s/w developer awareness? ljknews
Re: How do we improve s/w developer awareness? Gunnar Peterson
RE: How do we improve s/w developer awareness? Gary McGraw
Re: How do we improve s/w developer awareness? Jeff Williams
RE: How do we improve s/w developer awareness? Gary McGraw
Re: How do we improve s/w developer awareness? M Taylor
Re: How do we improve s/w developer awareness? Gunnar Peterson
RE: How do we improve s/w developer awareness? Wall, Kevin
Re: How do we improve s/w developer awareness? Dana Epp
Re: How do we improve s/w developer awareness? ljknews

Saturday, 13 November

Secured Coding Greenarrow 1
Re: Secured Coding Gunnar Peterson
Re: Secured Coding Dana Epp

Sunday, 14 November

RE: How do we improve s/w developer awareness? Aleksander P. Czarnowski
RE: Secured Coding David Crocker
Fw: Secured Coding Greenarrow 1

Monday, 15 November

Re: Secured Coding Peter G. Neumann
RE: Secured Coding Yousef Syed

Tuesday, 16 November

Choices Crispin Cowan
Re: Choices Nick Murison
Re: How do we improve s/w developer awareness? Nick Murison
Re: Choices Nick Murison

Wednesday, 17 November

Re: Secured Coding Gadi Evron

Friday, 19 November

Secured Coding-Intellectual Property Greenarrow 1
Re: Secured Coding-Intellectual Property Florian Weimer

Monday, 22 November

eSecurityPlanet article on Fortify source code scanner Kenneth R. van Wyk

Tuesday, 23 November

On SC-L's first anniversary Kenneth R. van Wyk

Monday, 29 November

Re: How do we improve s/w developer awareness? George Capehart
Re: How do we improve s/w developer awareness? Greenarrow 1

Tuesday, 30 November

interesting articles on secure coding Jose Nazario

Wednesday, 01 December

Re: How do we improve s/w developer awareness? George Capehart

Thursday, 02 December

Re: How do we improve s/w developer awareness? Brian Utterback
RE: How do we improve s/w developer awareness? Michael S Hines
RE: How do we improve s/w developer awareness? Shea, Brian A
Re: How do we improve s/w developer awareness? [Virus Checked] graham . coles
Re: How do we improve s/w developer awareness? der Mouse

Friday, 03 December

Former cybersecurity czar: Code-checking tools needed Jose Nazario
Re: How do we improve s/w developer awareness? David A. Wheeler

Sunday, 05 December

RE: How do we improve s/w developer awareness? Peter Amey

Monday, 06 December

Web Application Security Consortium 'Guest Articles' Call for Papers robert

Thursday, 09 December

BSI: penetration testing article Gary McGraw

Monday, 13 December

CFP: The 9th Colloquium for Information Systems Security Education Julie Ryan

Tuesday, 14 December

Eweek Article on Secured Coding Greenarrow 1

Wednesday, 15 December

Administrivia: Thanks for the input and happy holidays Kenneth R. van Wyk
Design for failure Gunnar Peterson

Saturday, 18 December

[Fwd: DJB's students release 44 *nix software vulnerability advisories] Gadi Evron

Monday, 20 December

eWeek articles on Software Security Kenneth R. van Wyk
RE: [Fwd: DJB's students release 44 *nix software vulnerability advisories] Shea, Brian A
Re: DJB's students release 44 poorly-worded, overblown advisories Paco Hope
Re: Re: DJB's students release 44 poorly-worded, overblownadvisories Paco Hope
Re: DJB's students release 44 poorly-worded, overblown advisories ljknews
Re: Re: DJB's students release 44 poorly-worded, overblown advisories Crispin Cowan
Re: DJB's students release 44 poorly-worded, overblown advisories dtalk-ml
RE: [Fwd: DJB's students release 44 *nix software vulnerability advisories] ljknews

Tuesday, 21 December

Re: [Fwd: DJB's students release 44 *nix software vulnerability advisories] Crispin Cowan

Wednesday, 22 December

Re: [Fwd: DJB's students release 44 *nix software vulnerability advisories] der Mouse
Re: Re: DJB's students release 44 poorly-worded, overblown advisories Crispin Cowan
Re: Re: DJB's students release 44 poorly-worded, overblown advisories Crispin Cowan
Re: [Fwd: DJB's students release 44 *nix software vulnerability advisories] ljknews
Re: Re: DJB's students release 44 poorly-worded, overblown advisories ljknews
Re: Re: DJB's students release 44 poorly-worded, overblownadvisories karger
Re: DJB's students release 44 poorly-worded, overblown advisories karger

Tuesday, 28 December

New article: "Secure programmer: Call Components Safely" David A. Wheeler