On Wed, 25 Oct 2006, Christopher Martin wrote: > Yes, Microsoft should write tighter code. Is it grounds for a > lawsuit? Well, I would suggest that any tech savvy judge (not that > one exists) would throw the case out, citing that it is common > knowledge that there are intrinsic security complications in > Windows. They would also say that if you buy Windows in full > knowledge of these pre-existing issues and then fail to take the > appropriate action then it's your own silly fault, in the same way > people burn themselves on a hot apple pie (despite the presence of > hot in title, as opposed to warm or tepid).
Inappropriate analogy. He doesn't want to sue because his own copy of Windows is causing him grief, he wants to sue because everyone else's copy of Windows is being used as an attack vector against him due to inherent security flaws that MS does not find profitable to fix. -- John Hardin KA7OHZ ICQ#15735746 http://www.impsec.org/~jhardin/ [EMAIL PROTECTED] FALaholic #11174 pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- "Bother," said Pooh as he struggled with /etc/sendmail.cf, "it never does quite what I want. I wish Christopher Robin was here." -- Peter da Silva in a.s.r ----------------------------------------------------------------------- 4 days until Daylight Savings Time ends in U.S.
