, 2001-12-31
Everyone from the FBI to the L.A. Times has something scary to say about the new XP vulnerability. Here's why they all have it wrong.
Expand all |
Post comment
Fear, Uncertainty and Doubt, Inc.
2001-12-31
Anonymous (1 replies)
Anonymous (1 replies)
RE: Fear, Uncertainty and Doubt, Inc.
2001-12-31
J Horner <jjhorner@bellsouth.net> (2 replies)
J Horner <jjhorner@bellsouth.net> (2 replies)
RE: Fear, Uncertainty and Doubt, Inc.
2001-12-31
Anonymous (1 replies)
Anonymous (1 replies)
Fear, Uncertainty and Doubt, Inc.
2001-12-31
Anonymous (2 replies)
Anonymous (2 replies)
No worm? Tim, lay off the meds
2001-12-31
Anonymous (9 replies)
Anonymous (9 replies)
A lesson in comprehension...
2002-01-02
Anonymous (1 replies)
Anonymous (1 replies)
A lesson in... Comprehend this: MS has 36+Billion in Liquidity (4x next on list)
2002-01-06
gained by monopoly + inferior product = superior pricing (does this compute?) (1 replies)
gained by monopoly + inferior product = superior pricing (does this compute?) (1 replies)
A lesson in... Comprehend this: MS has 36+Billion in Liquidity (4x next on list)
2002-01-16
Anonymous
Anonymous
Here you go Tim, the exploit is out !
2002-01-04
Chad Cyrisse (1 replies)
Chad Cyrisse (1 replies)

The IFRAME cross scripting vunerability in and of
itself is a nightmare. There are essenttially two
options with repsect to information security when
programmatic interfaces are steam components.
1) NONE
2) NO INFORMATION
The reason for such a strong statement is that we
can either talk about security or actually act on
the real problem. Examine a Unix shell environment
(termcap and terminfo in particular), mc (midnight
commander) and UNICODE interact with each other...
Without giving any details away, it is interesting
to see a Microsoft vunerability used to exploit
another, "less vunerable", system. This seems to be
the reversal of fortunes...kind of like a virii
response in a competitive host environment. Now the
viruii will have to fight each other. May the best
virus win.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/50/9679#9679