The Disparity Bit

Everyone is talking about the way Windows Update silently updates itself when set to 'notify only' (but not when set to 'off', apparently). Bruce Schneier calls it 'a huge deal'.

And it is. But only if you never considered what it really means to run a proprietary OS like Windows.

Microsoft can remotely, silently modify your OS any way they choose. Does that scare you? What can you do about it? Only install their patches manually? But you still won't have a clue what those patches do. Not install them at all? The holes in a completely unpatched Windows XP give the entire world remote control over your PC, not just Microsoft.

Microsoft can make your computer cooperate with some external entities against you. Do you think that's worse than 'mere' remote vulnerabilities? But how do you know your existing, unpatched OS isn't already betraying you? (It was when it downloaded that update.) How are you going to protect yourself against that?

Use a host-based firewall? Your OS can bypass it; it works through Microsoft callbacks and lives on Microsoft sufferance. Use an external firewall? How can it tell the difference between legitimate browser access to tfosorcim.com and software calling home?

Running Windows in a tightly locked-down VM is a hard but tractable engineering problem. Running it on bare hardware with Internet access is like keeping a huge tiger susceptible to radio mind control in your living room. You build a Faraday cage around your house and keep a tranquilizer gun in your pocket, and you pat it on the head after it feeds. Eventually the force of habit puts you off your guard and you let your children play with it and pull the tiger's tail. But the tiger only needs to bite your head off once for this to be a losing proposition.

Windows only needs to let someone bring down or take over a billion computers worldwide once for all of today's troubles with 10-million-PC botnets to look like really small peanuts.

I'll end with an insightful (and obvious) comment from Schneier's blog:

To say that those keys are "high value" is a bit of a gross understatement. Imagine that you had a key that would let you arbitrarily load software onto 90+% of the computers in the world. How much would something like that be worth to the right person? [...] Heck, it's probably more than a lot of people working at Microsoft are going to make in their entire lifetime. (And you just wanted to get the code long enough to cause a problem, it would definitely be worth enough to kill a few people for.) That's a nuclear-weapons-grade secret.

All accounts of the evil of Vista DRM are careful to remind us that no users ever asked for DRM. Microsoft have sold out to the MPAA, they wail. And almost noone stops to consider if this is really true or not.

They're all making the same mistake promulgated by Microsoft and the MPAA's PR. They assume that the primary users of Windows are the people who run it on their private PCs at home to "consume" media. The same people who soon won't even get to choose what version of Windows they run, as big integrators like Dell stop selling XP.

But the real mass-users of Windows, the ones with power to influence Microsoft, are big corporations and governments.

And corporations want DRM very, very much.

I've written here before about some reasons free, openly developed software generally has fewer security issues than proprietary software. However, one would expect Microsoft to beat the odds, since they're capable of funding any development process they want. They can hire world-class programming and QA teams and make sure at least their software contains no bugs or vulnerabilities.

Of course we all know that doesn't happen, but it might one day. I'd like to point out that there's another fundamental reason Windows and Office, or any similarly proprietary OS and applications bundle, can't be as secure as a good Linux distribution. Since I used to be a Gentoo Linux packager, I naturally consider package management to be the indispensable quality Windows lacks.

The new Vista license has been published by Microsoft, and people have been pointing out the differences from older Windows versions.

Reposted from my old blog - the old comments are there.

---

Xen can run unmodified DomUs (guest OSs), including Windows [pdf] or potentially any x86 or x86_64 OS, if your CPU supports Intel VT (aka Vanderpool) or AMD-V (aka Pacifica and SVM). I've always known that in theory, but I guess I haven't been keeping up with the news. It turns out all Athlon64 CPUs for the new Socket AM2 (and apparently some or all Pentium D Preslers) support SVM, and the latest Xen 3.0.2 can use that.