Netcraft: www.sco.com is a weapon of mass destruction

This is so funny! 🙂 Go read it and wait and see if SCO slashdots Slashdot!

Much of the commentary on the SCO distributed denial of service scenario, including our own, has been based on the premise that SCO badly wants to keep their web site running. This may not be the case: unlike Microsoft, which has a real business to run and a real need to keep its web site operational, SCO Executives may not strongly care about the availability of www.sco.com. After all, Michael Doyle’s half a billion dollar patent win against Microsoft scarcely hinged on the response times of the Eolas web site.

In fact, the author of the MyDoom virus has delegated control of the most enormous volume of http traffic that the Internet has yet seen to hostmaster@sco.com. On a whim, SCO can direct that Tsunami at an object of their choosing, simply by changing an A record in named.conf in time for the change to propagate by Sunday.

$2 trillion fine for Microsoft security snafu?

Doubtful it’ll happen..

Microsoft’s latest security lapse with its Passport information service could trigger a $2.2 trillion fine on the company courtesy of the US government.

Microsoft on Thursday admitted that a flaw in the password reset tool of its Passport service could compromise the information stored on all 200 million users. It scampered to post a fix and is looking into potential exploits, but the damage to Microsoft may already have been done.

Slashdot | Larry Rosen on the …

Slashdot | Larry Rosen on the Microsoft Penalty Ruling – good reading.

How do consumers benefit? No, really! by Enry

Both Bill Gates and John Ashcroft talked about how the decision benefits consumers. But there’s nothing really in the decision that changes the way MSFT does business. I can’t call IBM and get a discount on a system without Windows installed, if I load XP onto a machine, MSFT can take it over and install software without my permission, and the APIs can be buried in MSDN, forcing OSS software developers to not only subscribe to MSDN, but also follow whatever licensing MSDN forces on users.

For the most part, this is MSFT business as usual.