Friday, February 13, 2004 - Posts

Why Windows patching sucks (part 1)

1) no easy way to detect missing patches
2) no API to detect missing patches
3) no webservice with patching config info (well, hfnetchk has the xml file)
4) tools(like MBSA or URLSCAN) not bundled into popular downloads like IE, WMP, IM
5) no download manager to allow easy downloading

Other posts I about windows configuration/patching

http://dotnetjunkies.com/WebLog/stefandemetz/archive/2004/05/07/13102.aspx
http://dotnetjunkies.com/WebLog/stefandemetz/archive/2004/02/10/6974.aspx
http://dotnetjunkies.com/WebLog/stefandemetz/archive/2004/02/09/6877.aspx

windows code post-leak opinion

The website www.microsoft-watch.com posted some suggestions of what MS shall do.
It suggests that MS realease ALL the NT4/W2K code as open source so that windows compatible programs would run on any *ix based OS, creating even more demand.
What a hogwash.
What would make sense for a market follower does not make sense for a market leader with 90+ % of a market. For the extra 10 % they would give away 90%? OK, if anyone gives me 90 bucks, I' ll return 10. Any takers?

One Thing although would be nice: if MS could give all the "good" guys out there the (semi)automatic legal permission to hold copies of the leaked code. That way any academic,public institutions, partners and security firms could help with fixing things very fast without getting embroiled in the legal wrangle.