Journalists to Other Journalists: Call Out Windows
techrights.org
techrights.org
Also, the article's site is an amazingly shrill opponent of anything relating to MS or Bill Gates. "Author Calls for Action to Stop Bill Gates' Abduction of US Education", "Microsoft Exploits the Poor", "Gates Foundation (and Microsoft) Take the Libraries Takeover Global", etc. It reads like the author(s) puppies got squished by MS early in life, or something. Definitely personal, not rational.
You see a journalist "calling out" Microsoft for insecurity, and you've got a coin-flip's chance that that reporter has absolutely no idea what he's talking about when it comes to security.
Would I trust Win7 code more than... other code? Very yes.
This is basically like asking me, "which would you trust more: code that you're reasonably sure Mike Eddington fuzzed, or code that you're pretty confident he hasn't."
A good OpenBSD install, even one with lots of functionality, just has much less trusted code (i.e. code which absolutely has to be correct). And while I do like OpenBSD, it's not unique: the other BSDs are also solid, and Solaris - despite a somewhat bad reputation in some circles - is also pretty good.
I'm sure that there are some very smart people working on Windows security; it's just that engineering everything for security beats "features first".
[EDIT: thank you for your reply! I'm happy to learn, even if we're unlikely to convince each other...]
Anyway: I think they used to suck; I think that a lot of their decisions in things like ActiveX and IE 6 implied that they didn't yet have the kind of focus on security that they have now.
But, despite this article, Microsoft has taken a ton of heat from the computer industry for their various security issues, and I do think they've tightened it up a lot. I also think that the quote in the article conjecturing that we wouldn't see Linux botnets is absurd, given the number of Linux rootkits in the wild. The only reason we aren't seeing Linux botnets is because there aren't enough Linux systems to form one. (A joke, but only a little!)
And, I don't think you can sit a novice computer user in front of a Linux or BSD system and expect them to get security right. chroot Apache still breaks a lot of stuff, and the first inclination from the user is to change httpd to -u.
Microsoft does relatively OK these days.
Then they sure did a shitty job.
One thing that comes to my mind ... those obnoxious UAC screens. I've never had problems on Linux or Mac to type my password for escalated privileges ... but UAC I had to turn off because it was too annoying.
Also, until Win XP SP2 no firewall wasn't included in the Windows distribution. Not to mention all kinds of services that are active by default without the user needing any of them.
I'd sure like to know where those money went.
How about, by delaying the release of major revisions of their code, on multiple occasions by multiple months, to re-audit for vulnerabilities when a single instance of them is found during last-minute testing?
How about, by forcing every single developer in the company to be trained in writing secure C code? (Book jacket of very popular secure coding book: "Required reading at Microsoft - Bill Gates". Hacker News comment from former MSFT developer a couple days ago: "That book actually was required reading at Microsoft.") Or by deprecating the worst of the old C string interfaces, then banning them across their code, and then auditing against that?
I can see where the disconnect is between you and me on this issue. I've actually worked with them on some of this stuff. Far less than many other people in my field. But the UAC and firewall stuff isn't even on my radar.
The hubris here is astonishing. After this many decades, hasn't the entire industry adequately demonstrated that that almost all programs have mistakes and that most mistakes in C become security flaws? I've contracted there, I've sprinkled some proprietary buffer annotations around their legacy code, and I'm still not convinced that's enough to make unchecked pointers a reasonable way to write apps.
Should "you" write C code? No. You don't have to. You will screw it up in amusing and horrible ways. But don't suggest Microsoft should rewrite Office in Haskell. All that would happen if they did is that we'd learn how to exploit insecure Haskell idioms real fast.
I call BS on this quote. I have no reason to believe that, e.g. firefox on linux is any more secure than firefox on windows. There is no reason a botnet needs root access on a linux hosts. The only reason we don't have huge swarms of linux botnets is that hackers get more bang for the buck by targeting windows.
Instead of developing a new least-privilege extension API like Chrome did, Mozilla put in an App Store style review process on A.M.O. for real extensions and developed a new API just for lame themes. They have code signing baked in but don't even use it for their own code, so an annoying 'unsigned' warning is the expected default.
Even with all that, the extensions themselves have highly-exploitable vulnerabilities: http://lwn.net/Articles/348769/
It's probably the best means to get remote code execution on Linux, especially since extensions can bundle native NPAPI plugins.
Microsoft gets big credit for releasing a patch for many "PC Worms" or "PC vulnerabilities", but the vulnerability in never ever a "Windows" problem.
I tested my impression with data:
Google news searches:
frequency term
--- ---
0 pc worm
5 windows worm
12 computer worm
0 computer vulnerability
2 pc vulnerability
7 windows vulnerability
6 pc virus
35 windows virus
161 computer virus
Flawed premises are par for the course there. (For those who don't recognize the site, it's the old boycottnovell site, with a new name to try to dodge their old reputation).