Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Vista
Results, Not Resolutions
Bruce Schneier and Adam Shostack , SecurityFocus 2002-01-24

A guide to judging Microsoft's security progress.

Comments Mode:
Results, not Resolutions 2002-01-24
Anonymous
Results, not Resolutions 2002-01-24
Gary McGraw
Results, Not Resolutions 2002-01-24
David Litchfield (2 replies)
Results, Not Resolutions 2002-01-24
davep (at) pitt (dot) edu [email concealed] (1 replies)
Results, Not Resolutions 2002-01-25
Nicholas Harring
Results, Not Resolutions 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-24
Anonymous (1 replies)
Results, Not Resolutions 2002-01-24
Anonymous
Results, Not Resolutions 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
Anonymous
Well, to conclude: Use Java, M$ 2002-01-25
Anonymous (1 replies)
Well, to conclude: Use Java, M$ 2002-01-25
Trithemius (1 replies)
Well, to conclude: Use Java, M$ 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
BMaximus
SOAP Recommendation is Silly 2002-01-25
Anonymous (1 replies)
SOAP Rec is correct 2002-01-26
Anonymous
Almost right on the compensation 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
Anonymous
Results, Not Resolutions 2002-01-25
Chris
Regarding macros in documents... 2002-01-25
Anonymous
Things getting out of hand here? 2002-01-26
Toni Heinonen
Microkernel smog 2002-01-27
Grumpf
I'm quite sure they'll do it. They did it before with Internet technologies when felt behind (to fast to be honest).

But the "where do you want to go today" department must in fact stop and wait a bit. This time no one "wants to go anywhere" blindly.

The microkernel complexity added by the DCOM implementation model led to an extreme (and uncontrolable?) interdependency of processes. This was done inheritably in a bottom-up way over time. The "domino effect" on security is obvious.

Microkernels are still the way to go in my opinion, but this time and with all the new knowledge, things must be done from scratch in a topdown approach for a broader perspective of interaction and "sandboxing".

With a stable w2k and feature rich XP out there for a while, maybe now is the right time to give MS true programmers (yes, they exist) some slack and... REDESIGN!

Bill, this one's on me:

"Think abstract so you can think object".

PS: Nevermind if win2003 only comes out on 2005... A TIP: Call it Win3000.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/315/10177#10177
Inaccuracies and crazy talk 2002-01-28
Anonymous
Results, Not Resolutions 2002-01-28
Anonymous







 

Privacy Statement
Copyright 2007, SecurityFocus