sc-l  

Messages by Thread

• [SC-L] new book Jason Grembi
• [SC-L] DistriNet Research Group Kenneth Van Wyk
• [SC-L] Silver Bullet (transcripts) Gary McGraw
• [SC-L] Coverity to Buy Codefast Kenneth Van Wyk
• [SC-L] informIT: web 3.0 security Gary McGraw
• [SC-L] Silver Bullet 26: Adam Shostack Gary McGraw
• [SC-L] No general-purpose computer, or everything under surveillance? David A. Wheeler
  • Re: [SC-L] No general-purpose computer, or everything under surveillance? Andy Steingruebl
  • Re: [SC-L] No general-purpose computer, or everything under surveillance? Gunnar Peterson
• Re: [SC-L] GCC and pointer overflows karger
• [SC-L] MetriCon 3.0 Gunnar Peterson
• [SC-L] Microsoft's message at RSA Gary McGraw
  • Re: [SC-L] Microsoft's message at RSA Gunnar Peterson
  • Re: [SC-L] Microsoft's message at RSA Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]
  • Re: [SC-L] Microsoft's message at RSA Andy Steingruebl
  • Re: [SC-L] Microsoft's message at RSA Gary McGraw
  • Re: [SC-L] Microsoft's message at RSA Andy Steingruebl
  • Re: [SC-L] Microsoft's message at RSA Gunnar Peterson
• [SC-L] Reminder: W2SP 2008: Web 2.0 Security and Privacy 2008 Larry Koved
• [SC-L] GCC and pointer overflows [LWN.net] Kenneth Van Wyk
  • Re: [SC-L] GCC and pointer overflows [LWN.net] Robert C. Seacord
  • Re: [SC-L] GCC and pointer overflows [LWN.net] der Mouse
  • Re: [SC-L] GCC and pointer overflows [LWN.net] Epstein, Jeremy
  • Re: [SC-L] GCC and pointer overflows [LWN.net] ljknews
  • Re: [SC-L] GCC and pointer overflows [LWN.net] Leichter, Jerry
  • Re: [SC-L] GCC and pointer overflows [LWN.net] ljknews
• [SC-L] Lateral SQL injection paper Kenneth Van Wyk
  • Re: [SC-L] Lateral SQL injection paper Arian J. Evans
  • Re: [SC-L] Lateral SQL injection paper Jim Manico
  • Re: [SC-L] Lateral SQL injection paper Joe Teff
  • Re: [SC-L] Lateral SQL injection paper Steven M. Christey
  • Re: [SC-L] Lateral SQL injection paper Arian J. Evans
  • Re: [SC-L] Lateral SQL injection paper Mary and Glenn Everhart
  • Re: [SC-L] Lateral SQL injection paper Pascal Meunier
• [SC-L] Silver Bullet 25: Jon Swartz Gary McGraw
• [SC-L] InformIT: budgeting for software security Gary McGraw
  • Re: [SC-L] InformIT: budgeting for software security Stephen Craig Evans
  • Re: [SC-L] InformIT: budgeting for software security Jim Manico
  • Re: [SC-L] InformIT: budgeting for software security Wall, Kevin
  • Re: [SC-L] InformIT: budgeting for software security ljknews
  • Re: [SC-L] InformIT: budgeting for software security Jim Manico
  • Re: [SC-L] InformIT: budgeting for software security Dave Aronson
  • Re: [SC-L] InformIT: budgeting for software security Stephen Craig Evans
  • Re: [SC-L] InformIT: budgeting for software security Kenneth Van Wyk
  • Re: [SC-L] InformIT: budgeting for software security Stephen Craig Evans
  • Re: [SC-L] InformIT: budgeting for software security Gary McGraw
• [SC-L] Invitation - OWASP AppSec Europe May 19-22 2008 - Belgium Sebastien Deleersnyder
  • [SC-L] Invitation - OWASP AppSec Europe May 19-22 2008 - Belgium Sebastien Deleersnyder
• [SC-L] Bringing two threads together: PCI & SXSW Epstein, Jeremy
• [SC-L] 0x000000.com SuiGenchi Demonstration Benjamin Tomhave
• [SC-L] Silver Bullet turns 2: Mary Ann Davidson Gary McGraw
  • Re: [SC-L] Silver Bullet turns 2: Mary Ann Davidson Andrew van der Stock
  • Re: [SC-L] Silver Bullet turns 2: Mary Ann Davidson Stephen Craig Evans
  • Re: [SC-L] Silver Bullet turns 2: Mary Ann Davidson Gary McGraw
  • Re: [SC-L] Silver Bullet turns 2: Mary Ann Davidson Arian J. Evans
  • Re: [SC-L] Silver Bullet turns 2: Mary Ann Davidson Arian J. Evans
• [SC-L] Software Security Bibliography Gary McGraw
• [SC-L] Secure Development World ? Gadi Evron
  • Re: [SC-L] Secure Development World ? Steven M. Christey
  • Re: [SC-L] Secure Development World ? Gadi Evron
  • Re: [SC-L] Secure Development World ? Robert A. Martin
• [SC-L] CERT C Secure Coding Standard - last call for reviewers Robert C. Seacord
• [SC-L] Software security definition(s) Arian J. Evans
  • Re: [SC-L] Software security definition(s) Mike Lyman
• [SC-L] implementable process level secure development thoughts Andy Murren
  • Re: [SC-L] implementable process level secure development thoughts Gary McGraw
  • Re: [SC-L] implementable process level secure development thoughts Wall, Kevin
  • Re: [SC-L] implementable process level secure development thoughts Roman H.
  • Re: [SC-L] implementable process level secure development thoughts Andy Murren
• [SC-L] quick question - SXSW Benjamin Tomhave
  • Re: [SC-L] quick question - SXSW William L. Anderson
  • Re: [SC-L] quick question - SXSW Benjamin Tomhave
  • Re: [SC-L] quick question - SXSW Kenneth Van Wyk
  • Re: [SC-L] quick question - SXSW Johan Peeters
  • Re: [SC-L] quick question - SXSW Gunnar Peterson
  • Re: [SC-L] quick question - SXSW John Steven
  • Re: [SC-L] quick question - SXSW Arian J. Evans
  • Re: [SC-L] quick question - SXSW Benjamin Tomhave
  • Re: [SC-L] quick question - SXSW Arian J. Evans
  • Re: [SC-L] quick question - SXSW Mike Lyman
  • Re: [SC-L] quick question - SXSW Gary McGraw
  • Re: [SC-L] quick question - SXSW Arian J. Evans
  • Re: [SC-L] quick question - SXSW Andy Steingruebl
  • Re: [SC-L] quick question - SXSW Arian J. Evans
  • Re: [SC-L] quick question - SXSW Andrew van der Stock
  • Re: [SC-L] quick question - SXSW Stephen Craig Evans
  • Re: [SC-L] quick question - SXSW Gary McGraw
  • Re: [SC-L] quick question - SXSW Andy Steingruebl
  • Re: [SC-L] quick question - SXSW Gary McGraw
• [SC-L] Secure Coding Books Lawson, David L
  • Re: [SC-L] Secure Coding Books Jim Manico
  • Re: [SC-L] Secure Coding Books Sebastien Deleersnyder
  • Re: [SC-L] Secure Coding Books Gary McGraw
  • Re: [SC-L] Secure Coding Books Goertzel, Karen [USA]
  • Re: [SC-L] Secure Coding Books Neil Daswani
  • Re: [SC-L] Secure Coding Books Robert C. Seacord
  • Re: [SC-L] Secure Coding Books Dean H. Saxe
  • Re: [SC-L] Secure Coding Books Bennett, Jason
• Re: [SC-L] CFP: W2SP 2008: Web 2.0 Security and Privacy 2008 Larry Koved
• [SC-L] Secure development after release Andy Murren
  • Re: [SC-L] Secure development after release bugtraq
• [SC-L] PCI: Boon or bust for software security? Kenneth Van Wyk
  • Re: [SC-L] PCI: Boon or bust for software security? Bruce Ediger
  • Re: [SC-L] PCI: Boon or bust for software security? Andy Murren
  • Re: [SC-L] PCI: Boon or bust for software security? Benjamin Tomhave
• [SC-L] Silver Bullet 23 Gary McGraw
• [SC-L] SC-L Administrivia: How does the readership feel about sponsorships? Kenneth Van Wyk
• [SC-L] SDLCs and x.509 at OWASP Belgium, 4 March 2008 Kenneth Van Wyk
• [SC-L] Michael Howard's Web Log : Introducing SAFECode Kenneth Van Wyk
• [SC-L] Darkreading: code scanning Gary McGraw
• [SC-L] CALL FOR TOPICS-PAPERS - OWASP AppSec Conference Europe 2008 - May 22-23, Belgium Sebastien Deleersnyder
• [SC-L] a little coding humor... Benjamin Tomhave
• [SC-L] Tech Insight: The Buzz Around Fuzzing - Application and Perimeter Security News Analysis - Dark Reading Kenneth Van Wyk
• [SC-L] Silver Bullet: spaf transcript Gary McGraw
• [SC-L] Static analysis tool exposition - call for participation Romain Gaucher
• [SC-L] Programming language comparison? Vincent Verhagen
  • Re: [SC-L] Programming language comparison? Robert A. Martin
  • Re: [SC-L] Programming language comparison? Steven M. Christey
  • Re: [SC-L] Programming language comparison? ljknews
  • Re: [SC-L] Programming language comparison? Steven M. Christey
  • Re: [SC-L] Programming language comparison? Robert C. Seacord
  • Re: [SC-L] Programming language comparison? ljknews
  • Re: [SC-L] Programming language comparison? Pete Shanahan
  • Re: [SC-L] Programming language comparison? Shea, Brian A
  • Re: [SC-L] Programming language comparison? Vincent Verhagen
  • Re: [SC-L] Programming language comparison? Craig E. Ward
• [SC-L] Silver Bullet: Ed Amoroso Gary McGraw
  • Re: [SC-L] Silver Bullet: Ed Amoroso Ignacio Evans
• [SC-L] XKCD on sane build environments Benjamin Tomhave
• [SC-L] Open Source Code Contains Security Holes -- Open Source -- InformationWeek Kenneth Van Wyk
  • Re: [SC-L] Open Source Code Contains Security Holes -- Open Source -- InformationWeek Gary McGraw
  • Re: [SC-L] Open Source Code Contains Security Holes -- Open Source -- InformationWeek Steven M. Christey
• [SC-L] Darkreading: Getting Started Gary McGraw
  • Re: [SC-L] Darkreading: Getting Started Gunnar Peterson
  • Re: [SC-L] Darkreading: Getting Started Gary McGraw
  • Re: [SC-L] Darkreading: Getting Started Andy Steingruebl
  • Re: [SC-L] Darkreading: Getting Started Gary McGraw
  • Re: [SC-L] Darkreading: Getting Started Jim Manico
  • Re: [SC-L] Darkreading: Getting Started Gary McGraw
• [SC-L] ENISA issue on Software Security Kenneth Van Wyk
• [SC-L] secappdev 2008 Johan Peeters
• [SC-L] Code Testing Tools Could Be Acquisition Targets in '08 Kenneth Van Wyk
  • [SC-L] Code Testing Tools Could Be Acquisition Targets in '08 Tom Brennan
• [SC-L] Silver Bullet Episode 21: Cigital principals Gary McGraw
• [SC-L] Silver Bullet Happy Holidays Gary McGraw
• [SC-L] darkreading: PCI, web app firewalls, and software security Gary McGraw
  • Re: [SC-L] darkreading: PCI, web app firewalls, and software security Gary McGraw
  • Re: [SC-L] darkreading: PCI, web app firewalls, and software security Pete Werner
  • [SC-L] Interesting Blog Entry on Tools Coverage McGovern, James F (HTSC, IT)
  • Re: [SC-L] Interesting Blog Entry on Tools Coverage Steven M. Christey
  • Re: [SC-L] Interesting Blog Entry on Tools Coverage Chris Wysopal
  • [SC-L] Secure Coding in the Hartford CT Area McGovern, James F (HTSC, IT)
• [SC-L] WASC Announcement: The Script Mapping Project Results and Call for Participation announcements
• [SC-L] Code Coverage and Code Quality tools avi shvartz
  • Re: [SC-L] Code Coverage and Code Quality tools McGovern, James F (HTSC, IT)
• [SC-L] Redmond Developer News | Best Defense? Kenneth Van Wyk
• Re: [SC-L] SC-L Digest, Vol 3, Issue 197 karger
  • Re: [SC-L] SC-L Digest, Vol 3, Issue 197 dcrocker
• [SC-L] Fwd: SCARE metrics and tool release Kenneth Van Wyk
• [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Kenneth Van Wyk
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Leichter, Jerry
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading der Mouse
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Leichter, Jerry
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading der Mouse
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Shea, Brian A
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Steven M. Christey
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andre Gironda
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Kenneth Van Wyk
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andre Gironda
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and robert
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andy Steingruebl
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Blue Boar
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andy Steingruebl
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading silky
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Steven M. Christey
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andre Gironda
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading silky
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Pete Werner
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andre Gironda
  • Re: [SC-L] Insecure Software Costs US $180B per Year - Application and Perimeter Security News Analysis - Dark Reading Andre Gironda
• [SC-L] Silver Bullet 20: Markus Jakobssen Gary McGraw
• [SC-L] podcast (IT Conversations) Gary McGraw
• Re: [SC-L] OWASP Publicity Gary McGraw
• [SC-L] "Radio" webcast on EOG/Software Security streams FRIDAY at noon EST Gary McGraw
• [SC-L] Fwd: People in glass houses shouldn't brick phones Kenneth Van Wyk
• [SC-L] [Fwd: Seeking questions for Panel discussion on website vulnerability disclosure during OWASP-WASC AppSec Conference on Nov 15] Benjamin Tomhave
• [SC-L] Bernstein's new paper on secure coding Benjamin Tomhave
• [SC-L] FINAL REMINDER: OWASP & WASC AppSec 2007 Conference - Nov 12-15 - San Jose, CA Dave Wichers
• [SC-L] Code review pool Paolo Perego
  • Re: [SC-L] Code review pool ljknews
  • Re: [SC-L] Code review pool Paolo Perego
  • [SC-L] OWASP Publicity McGovern, James F (HTSC, IT)
  • Re: [SC-L] OWASP Publicity Gunnar Peterson
  • Re: [SC-L] OWASP Publicity Crispin Cowan
  • Re: [SC-L] OWASP Publicity Bernie Rosen
  • Re: [SC-L] OWASP Publicity der Mouse
  • Re: [SC-L] OWASP Publicity Leichter, Jerry
  • Re: [SC-L] OWASP Publicity Crispin Cowan
  • Re: [SC-L] OWASP Publicity Benjamin Tomhave
  • Re: [SC-L] OWASP Publicity James Stibbards

• Earlier messages
• Later messages