In any case, I'm glad to see someone in MS has come out of the closet
on this issue.
Writing Secure Code 2nd Ed is chock full of Microsoft-specific
defects!!!
[19 Deadly Sins]
http://books.mcgraw-hill.com/getbook.php?isbn=0072260858
[Writing Secure Code]
http://msdn.microsoft.com/security/
Heh. They want us to do their code review for them?
Did you look at it?
I looked at the referred-to blog. I didn't see any code, though I
didn't do much webcrawling looking for any - perhaps I was too early,
or perhaps I just missed the crucial link, or
Christopher Canova [EMAIL PROTECTED] wrote:
It seems to me that they may be shifting from a
Deploy-first-ask-questions-later tactic to a
Code-it-right-before-its-out-the-door.
They always did code it right before it's out the door. It's just a
question of where you put the comma. ;-
