Microsoft's Security Report Card 354
Decaffeinated Jedi writes "In January 2002, Microsoft launched an initiative called 'Trustworthy Computing' aimed at building better security into its products. It's now two years later, and News.com serves up a report card evaluating Microsoft's efforts. Kevin Kean, a group manager at Microsoft's Security Response Center, points out that customers are better off now than they were before the company made the move to refocus on security issues. An analyst quoted in the article, Stephen O'Grady, agrees that he would give Microsoft 'improved marks,' but also notes that the company is not yet where it needs to be in terms of security. He goes on to suggest, however, that 'the numbers indicate that they are at least taking it seriously.' It sounds like Microsoft might have earned itself an Incomplete on this report card."
Let's be honest (Score:5, Insightful)
Security is a job for all of us, not just Microsoft.
As long as hackers out there have the tuits to break into systems, security is everyone's business.
Re:Let's be honest (Score:4, Interesting)
I think that it is great that less critical problems are being found now then with Windows 2000, and I hope the trend continues.
As an aside, I installed OS X on my grandmother's computer, and until now, forgot about her. Thanks for the reminder to write. Unfortunately, even that is not maintenence-free. Apple has had their own security problems of late.
How about an honest embrace of common sense?
Re:Let's be honest (Score:5, Insightful)
The quantity seems to have dropped, but the severity seems to keep increasing.
Just look at the havok caused by the recent RPC worms.
- I'm also in disbelief that Microsoft still haven't released a patch for the %00 bug in IE that allows spammers and malicious web admins to obscure the real URL the user is being directed to, perhaps Microsoft don't see a bug which could be used to trick people out of their hard earned cash as a Critical problem?
Re:Let's be honest (Score:5, Funny)
They wouldn't see it as a bug, heck that's exactly what Microsoft have been doing to their customers for years!
Re:Let's be honest (Score:2, Interesting)
Services should not default to listening state. Nobody has ever been able to write secure services yet people keep saying "I think we've got it this time"
Leave it off, if I need it I will turn it on. If I am too stupid to turn it on than maybe it shouldn't be on, or at least not accepting connections and data from any IP address on the net. This common sense and they are just now adding it to SP2. And before you step in and call me a Linux zealot, most Linux destroys do this wrong also.
B
Re:Let's be honest (Score:2)
That's what I like about a default(?) gentoo install as opposed to the default install of most other distros
Re:Let's be honest (Score:2)
But we get precious few opportunities to use our pitchforks.
Windows is at that point (Score:5, Funny)
Re:Let's be honest (Score:3, Interesting)
Is any software really at the point where we can install it and forget about it?
Qmail [qmail.org] is pretty damn close.
Re:Let's be honest (Score:2, Informative)
Re:Let's be honest (Score:2)
Re:Let's be honest (Score:5, Interesting)
MS is also working on more secure technologies like
MS is working on code signing at every level of the system. This means no more boot viruses, no more trojans.
MS is still lacking on speed to update. The RPC bug was on the streets long enough for exploits to be written BEFORE they got even the smallest patch out. The big worms came after they did get the patch out, but people weren't updating.
Where does Linux stand in all of this?
Updates are usually still handled manually with apt-get update/upgrade. RedHat has live notification, but it's still done manually for the most part, which slows down the process. There are wasy of caching apt packages for internal use by making your own apt-source, but they can be difficult to implement. You can do similar things with RedHat, but there isn't a lot of work being done in this area.
Open Source developers still hug C and hate most anything running in any other safer languages because of performance. Despite it actually costing more man hours to manually go out and install new versions of SSH, bind, sendmail, etc. every 3 months, for some odd reason open source developers value cpu clock cycles on a machine that sits idle 99% of the time more than an actual person that can hardly find 5 minutes, and usually admins so many computers it turns into an all-nighter.
Open Source people see code signing as a way to enact DRM and are fighting it.
Open Source releases updates within minutes of being aware of prossible security problems, sometimes it can take an hour or a day on less critical projects, but for the most part updates are very quick.
I see progress in MS land, but Open Source people are fighting the future, and are living in status quo. There's no reason why 99% of the daemons out there couldn't be written in Python or Java (with Kaffe even). There's no real reason to fight TCP yet.
Re:Let's be honest (Score:5, Insightful)
Sure, the security is improving, the SUS server is a nice tool.
But what bugs me beyond belief is the amazing lack of information it gives.
SUS out of the box does not:
- Client cannot be controlled, you cant use Windows update to update your system NOW, you will have to rely on reghacks, and stopping and starting services, to make sure your system will be updated in approx 15 minutes..
That is crap, Im the sysadmin, I want to make sure that the system is updated NOW.
- The SUS Server has no simple reporting -who-, -when- and if successfull or not, of events like a client connected and pulled updates.
This is even more crap, I cannot scan the server for activity from clients, unless I go digging in cryptic log files, which are not identified in the MS docs about SUS anyway.
Sure, there is a smart guys script that does that, which involves installing stuff for IIS, without properly explaining how and where. Again unacceptable.
It is that Nachio blasted our network away that we HAVE to be protected so I use it.
But Im very dissapointed in the lack of control and information it gives.
THATS my gripes with MS, stop listing to the damn users already!@ And start listing to the sorrow admins, like me.
NOT just for security in press, but for the daily lives of their admins. After all THEY need to understand whats happening, THATS the basis of REAL security.
"/Dread"
Re: (Score:3, Insightful)
Re:Let's be honest (Score:4, Informative)
Automatic Updates checks for critical updates only, and works in three modes: notify me, download and notify me, or download and install. In the first two modes, you have complete control over what gets installed - even in the case that it's downloaded, it won't be installed unless you give the go-ahead. The third mode, of course, is fully automatic - available critical updates are downloaded and installed at a time specified by the user (it defaults to 3am, iirc).
Personally, in the year or so I've been using XP, I've found no reason not to have it set to automatically install updates. Nothing has broken, and if any unpleasant features have been installed for me, I certainly haven't noticed. (And given the way sites like
Re:Let's be honest (Score:5, Insightful)
Sorry, but if I really felt stupid enough, I could have cron job'd my portupgrade, apt-get, urpmi or up2date long, long before Microsoft thought it was a good idea to push updates to clients; we could have been doing this back while microsoft was trying to convince the court that a HTML interface was the only way that they could update their OS.
You seem to have gotten lost somewhere along the way--updates are manual for a reason. The prudent admin takes the time to know what vulnerabilities or potential problems are going to affect their system. The prodent admin knows whether updating is necessary and what potential problems it may cause. Availability of new code doesn't mean that updates are required.
Automating updates isn't "progress." It isn't even hard.
Open Source developers might "hug" C, but they are much less aflicted by language myopia than are Windows developers.
What Windows IDE will do syntax highlighting for Python
How about PERL?
or PHP?
or Ruby?
or any of the other numerous languages that are not only supported, but are afforded real, working tools natively supported by the environment.
I think your point is something to take very seriously; but I don't see the Open Source community sitting, waiting for MS. Ultimately the idea is fallacious because it takes for granted the idea that new == better. There are many, many reasons to stick with something that works.
Words of wisdom that have been around much longer than you or I: "If it ain't broke, don't fix it."
Re:Let's be honest (Score:3, Informative)
This just goes to show how little experience most Linux desktop (not server) admins have in the real world. End users can not be trusted to update their machines. Yes, updates should be done manually to test for potential problems...in a lab environment. After they have been tested and approved in the lab, they should be rolled automatically to the end user. It is simply ludicrous to assume that one admin, or even a
Re:Let's be honest (Score:5, Interesting)
1: Microsoft has been convicted of antitrust violations. Hence why
2: Blaster.
3: Many linux groups are still nitpicky crazy people who instead of agreeing and copromising, they bicker. Even more are lazy, or greedy, or just plain stupid.
4: Open source people see Microsoft's code signing as a way to enact DRM, which is a polite way of saying they want total world domination. Many linux guru's like the idea of code signing, they just don't like Microsoft and they have good reasons.
5: Linux, netware, and other operating systems are still used for servers more often than Microsoft's software. MS's software is only used on desktops because everyone knows it. I'v used KDE on suse 8.1, it works well for anyone accept power users and I see no reason for ma n' pa to spend $300 on a new copy of winxp so they can check their e-mail.
6: Coding tools for linux exist that are open source and that work well. Not everyone is coding in C.
7: Linux is known for it's efficiency. On a server, efficiency > ease of use. Ms's software was designed for idiots, Linux was designed for people who know what they are doing. Linux is for the person who says "my powersupply blew out last storm, I'll replace the fuse and see if it works" whereas microsoft is for people that say "computer doesn't work = replace computer".
I see progress in for both linux and windows. I see more mind-blowing applications coming out for linux next year and I also see the first idiot proof interfaces coming into being. I don't see microsoft living upto their security bullshit, which they've had several years to implement but haven't. You can say "they're getting better" all you want, but is their security really better than it was in 2000? I see more DRM being brought into play, and it being either accepted or rejected on an individual basis. Ultamatly, in 10 years, I see microsoft becoming a linux distibutor, weither announced or unannounced.
Re:Let's be honest (Score:4, Informative)
What's stopping them? The go-mono project is quite active- I get at least 50 emails a day from linux programmers that are using
2: Blaster.
The most popular platform, ran by the most people in the world, etc. is bound to have security holes that get exploited. Unfortunately when 95% of the people out there don't know how to patch, these are blown way out of proportion. One company can only do so much to prevent the problems- anything else and you get complainers (see point #4).
Many linux groups are still nitpicky crazy people who instead of agreeing and copromising, they bicker. Even more are lazy, or greedy, or just plain stupid.
I've presented at LUG's and I would somewhat agree with this point. There are some people that are just interested in getting things work, but many of them are hecklers, complainers, etc. It's just the sub culture. I used to be "on the other side of the fence" and I know the mindset. Once I graduated college and started working with business, my perspective changed quite a bit. People are drawn to anger/hate/etc. and unfortunately leaders in the linux community help foster this so it continues to pervade.
4: Open source people see Microsoft's code signing as a way to enact DRM, which is a polite way of saying they want total world domination. Many linux guru's like the idea of code signing, they just don't like Microsoft and they have good reasons.
Exactly. MS starts implementing security to eliminate things that happen in #2, and now the complaints start rolling in. No matter what MS does there will always be naysayers. They will never be satisfied.
5: Linux, netware, and other operating systems are still used for servers more often than Microsoft's software. MS's software is only used on desktops because everyone knows it. I'v used KDE on suse 8.1, it works well for anyone accept power users and I see no reason for ma n' pa to spend $300 on a new copy of winxp so they can check their e-mail.
In most companies that I have worked in or with, Linux tends to be used primarily for non-critical systems. Solaris is used on any other *nix based system for critical things (eg. production oracle databases), and the hardware cost is astronomical in comparison. We are converting to Win2K servers. The license cost for a business is not what a consumer would pay, in fact it is significantly less (ex-$100 instead of $300 for XP). Most new PC's that companies order (ie, dell) come with WinXP anyway.
6: Coding tools for linux exist that are open source and that work well. Not everyone is coding in C.
Ok, as a
7: Linux is known for it's efficiency. On a server, efficiency > ease of use. Ms's software was designed for idiots,
I don't think it was designed for "idiots" but I agree that there is definitely a level of abstraction that MS unnecessarily gives the sys admin that ca
Re:Let's be honest (Score:4, Insightful)
. Hence why
Blaster Non
Microsoft's code signing as a way to enact DRM What about signing Java applets for security?
MS's software is only used on desktops because everyone knows it. Um, a majority of enterprise environments that I work in all use Win2k servers to a good degree of success. (Some of the logic to use Win2k is pretty lame...most could easily be replaced with Linux based systems. )
Ms's software was designed for idiots, Why is this bad? Going back to your previous argument, are your "ma n' pa" linux gurus? Are the majority of enterprise/home users, gurus? This is the very elitist attitude that ticks me off. I see it routinely on newbie bulletin boards and chats...it really chaps my you know what. I almost completely switched over all of my systems to FreeBSD for this very reason (support base).
I believe most of your comments were rants against the evil Empire, rather than anything of content.
Linux needs to START catering to "idiots" if this is going to be the "Year of the Linux Desktop". Not all users and even developers are masters of their operating system (I'm going to get flamed for this, but they really don't have to). A user/developer needs to be able to adopt a Linux system and then say: "Hey you know what would be cool" and then proceeds to build a couple of apps
I think that is when Linux will really take off. A few of my developer friends (Perl mongers) refuse to run linux because of the amount of time it takes them to do simple stuff (Plug-in cameras and other peripherals and have them instantly recognized). I can see their point sometimes, when I'm trying to get a pacakge to be installed, only to be told I need four other updates in order to install the first.
The post was right thought:Linux was designed for people who know what they are doing...
That needs to change very quickly.
There are a lot of flavors of Linux out there that I believe are on the right path (I, for one, like Mandrake...and previously Red Hat).
Re:Let's be honest (Score:3, Informative)
Yes, that's a nice spin -- it's your own fault when your computer has been successfully attacked, even if the vendor has known about the vulnerability for months.
The most important part about patching is that you have to do it. If something goes wrong, the vendor can blame you. You don't pay your virus scanner tax? Your fault. You don't pay for personal firewalling software? Again your fault. You don't apply that multi-megabyte security upgrade?
Improved marks? (Score:2, Funny)
Going from an F- to an F+ isn't something to get excited about.
new differnce (Score:4, Funny)
i'm calling myself a trojan horse
Re:new differnce (Score:4, Funny)
Re:new differnce (Score:3, Funny)
*ducks*
MCP Club (Score:3, Funny)
Now go set up franchises all over the country.
Re:new differnce (Score:3, Funny)
Do you have some guy named Tron throwing a glowing frisbee at you now?
Sorry, couldn't resist.
steveha
Let's Compare (Score:2, Interesting)
Heck Red Hat doesn't even support it anymore! 9.0 is coming up too!
Re:Let's Compare (Score:2)
I'll see your three mouse clicks and raise you a two-line shell script.
Re:Let's Compare (Score:2)
I seriously doubt in Microsoft's ability to gain back some degree of trust after years of total neglect. They'll have to do much better for much longer.
No news isn't good news (Score:4, Funny)
Re:No news isn't good news (Score:2)
Nor really (Score:5, Funny)
I think the appropriate grade for this would be an IP (in progress).
Re:Nor really (Score:2, Funny)
Re:Nor really (Score:2)
Which is also, oddly appropriate.
Re:Nor really (Score:2)
Still very appropriate.
Re:Nor really (Score:2)
What they meant was 'Incompetent'
Wait a minute... (Score:3, Insightful)
Re:Wait a minute... (Score:5, Insightful)
If the end user was to grant full control over his computer to Microsoft, then it wouldn't be his responsibility to keep it up to date.
'Secure' technlologies like the DRM used in iTunes' M4P and WMP's WMA files are exactly that - granting some of your control over your computer to those companies in exchange for being able to get music files.
In this case, by granting some of your control over your PC to Microsoft (allowing them to automatically update your PC with new fixes) you can gain more security.
But do you really want to leave your security and privacy in the hands of a corporation? Or would you rather spend the time to do it yourself? You can't have it both ways. Either you keep your PC secure (either by updating Windows often and using a firewall and not visiting random sites and opening random attachments, etc., or by switching to a more secure operating system), or you let someone else do it for you.
Re:Wait a minute... (Score:3, Interesting)
MS improving (Score:4, Insightful)
It's about time, and they still have a long way to go, but increasing security gives less room for E-mail viruses, worms and other network-hogging exploits.
Hmm... Any chance of a class-action suit from people who do NOT use Microsoft, addressing the way their lack of security has wrecked important services for non-MS users?
After all, those of us who don't use MS have never accepted their EULAs, but they've still wreaked havoc for our systems.
Could at least lead to an even further increased MS focus on security, which would help everyone...
Re:MS improving (Score:2)
Less security problems in MS products now is ultimately worse for us. Here's why:
If MS products become good, more people will want to use them, and there will be less interest in linux as an alternative. MS's behavior is constantly reminiscent of an emire, trying to usurp the rights of others for their own good.
So how exactly is the profitability of someone/thing that wants to take my money, my propery, and most importantly, my rights, a good thing for anyone, let alone everyone?
It's not
Can't get into Yale with this... (Score:5, Interesting)
I'm sorry, Microsoft, but you have to be held to higher standards, not lower. Open source is able to do better with infinitely less.
If a bunch of hobbiests were able to colonize the moon, would we hold back any criticism of NASA?
Or maybe we've just figured out a better way of doing things. In which case, maybe the soft spot for the dinosaurs is somewhat warranted.
Re:Can't get into Yale with this... (Score:2, Insightful)
Look, I have on my desk a rock. It has never been broken into by hackers. It rejects all spam sent to it. It was free.
And yet, somehow, I don't think the world will soon use rocks instead of computers to connect to the Internet. If we go with the premise that OSS is 100% secure, this doesn't mean that it's any better a computer system than this rock per se. The tiny end-user market pentetration of OSS despite it
Re:Can't get into Yale with this... (Score:2, Funny)
Re:Can't get into Yale with this... (Score:2)
Re:Can't get into Yale with this... (Score:2)
Re:Can't get into Yale with this... (Score:3, Insightful)
Almost all of whom contribute their work for free, as in unpaid.
I don't know about your math, but last time I checked, "free" was considerably less than "~$38 Billion".
Re:Can't get into Yale with this... (Score:2)
Re:Can't get into Yale with this... (Score:5, Interesting)
I've had a hypothesis for some time that the security flaw rate in Linux would decline over time and eventually approach zero, where Microsoft's would stay essentially constant. I believed this would happen because the Linux source was open and all the security holes would gradually be found and squashed, where the Microsoft source, being closed, wouldn't be as closely examined and would remain a fertile field for new exploits forever.
Well, in 2003, my pretty little hypothesis sure wasn't looking too good. I haven't actually compared numbers, but I felt like there were just as many bad critical bugs on Linux as there were on Microsoft. From my perception, the Linux rate rose, while the Microsoft rate dropped, which is exactly opposite what I was expecting.
I still believe that closed source is "fake" security, and that the only way to get REAL security is for everything to be open, but in terms of actual number of published exploits, both systems appear to be about equal at the moment.
And the standards to which Microsoft needs to be held are pretty much immaterial; only Microsoft can fix that code, where anyone can, in theory, fix bugs in OSS. Personally, I think we can use them as a yardstick, but we shouldn't be flinging mud.... very many more years like 2003, and they'll be flinging lots more of it back at us.
In 2003, OSS security sucked. I hope 2004 is better.
Re:Can't get into Yale with this... (Score:2)
Show me the security... (Score:2, Interesting)
Until then, I'll stick with BSD, Solaris and Linux.
They've still got a ways to go. (Score:4, Insightful)
Just trying to figure out what needs to be updated is a pain in itself, unless you figure out that you need the MBSE. Then you need to wade through the security bulletins, which sometimes contain the patch (in varying locations of the document and with no fewer than two pages to go through to get to the patch) and sometimes tell you to go to Windows Update. Not an option when you're trying to cut a disc for a client, or are dealing with an environment that doesn't allow Windows Update for security reasons.
Grabbing MBSE and every available patch from the website and applying said patches to a fresh Windows XP installation took about two and a half hours, and was incomplete (MBSE reported four patches that weren't applied). Windows Update isn't appropriate for a fresh install because of things like Blaster that will automatically infect the system upon connection to the Internet.
Then, there's all the defaults they've got to have their system phone home, such as sa.windows.com for searches, IE automated updates, WMP automated updates (including DRM), ntp.windows.com, Automated Windows Update. Locking down a Windows XP system is an exercise in frustration.
Trustworthy computing? Methinks not. Linux/BSD/OSX may have their myriad security and design flaws (except OpenBSD, which has yet to have a remote root compromise), but Windows XP holds a special place in my heart. Microsoft has admitted they've got an issue with security, which is a good thing, but now they should really address it -- they should be doing everything possible for the user to take control of his/her system, instead of heading the other way.
Re:They've still got a ways to go. (Score:5, Insightful)
Uh-huh. And you use what to update your Linux systems? Do you manually visit every relevant website and download updates, compile and reinstall everything, resolving dependencies by hand?
Or do you use apt, up2date, emerge...? I'm not clear on how this differs from Windows Update, with the obvious exception of altered EULAs and similar nastiness. There's no excusing that.
My point is that updating any OS without some sort of frontend to do the legwork is horrible. Bash MS, sure, but bash fairly. They've got a decent-and-improving frontend to their patching, a variety of tools to check your network for patch levels, and so on. Good enough? Depends on your environment, but it's a LOT better than nothing.
Microsoft and Security (Score:4, Funny)
OK, I'm VERY sorry but... (Score:5, Insightful)
""There is an order of magnitude--more people using Automatic Update and downloading patches," Microsoft's Kean said."
This would be the system that gave the world the "DRM or be unpatched" situation, right? how trustworthy.... changing functionality along with a "security" patch
I know that bashing microsoft is a favorite past-time here
really HOW is this "trustworthy" ??
I am REALLY impressed by the stupidity of these "reviewers" and how easily people forget these sorts of things... cudos to microsoft PR... AGAIN
I REALLY needed to get this of off my chest
Re:OK, I'm VERY sorry but... (Score:2)
Consider this: You own a mp3/ogg player that does not support DRM. Microsoft finially pushes the final patch that makes it impossible for your windows system to play ANYTHING not WMA AND signed. Suddenly, and without warning you couldn't use your MP3/OGG player anymore... considering (from my point
Re:OK, I'm VERY sorry but... (Score:3, Insightful)
And you know as well as I do that there would be an absolute uproar should that ever happen. MS are big, but they've been swayed by public outcry before - just look at the extension of support for Win98 as one example.
Besides which, as soon as the story hit, people would simply stop applying that patch - while some would almost certainly reinstall the OS to rid themselves of it i
80::20 rule applied to Microsft Security (Score:5, Insightful)
What a well worded articulation - almost Greenspan-ish like in a sense that it looks like he is saying something, but you can never hold him upto for "whatever he is saying." And I think this quote summarises the whole article well.
It is 80:20 rule or in Microsoft's case 40:60 rule. In the first year you move 40 % of the distance towards the the Security Goal-Post. So, "Customers are better off today than they were a year ago, . In the next year you move another 40 % towards the goal. So, "Customers are better off two years from today than they will be a year from today. . An so on and on ...
Now if the security Goal Post moves and you find yourself heading in the wrong direction, as it always does in Real life, you can frame your message as follows. You are now 60 % away from the old place. So, "Customers are better off today than they were a year ago, . In the next year you move another 60 % away from the old place. So, "Customers are better off two years from today than they will be a year from today. . An so on and on ...
So,
And how can you be wrong when you say it the way it is said. What a well worded articulation.
Microsoft's Report Card (Score:5, Funny)
SEMESTER 2, 2003
PRODUCTIVITY 101 3 HRS 80% C
ECONOMICS 307 3 HRS 100% A
CREATIVITY 92 3 HRS 67% D
GOV'T STUDIES 203 3 HRS 100% A
COSC 507 ADVANCED 3 HRS 78% C
MONO 302 3 HRS 100% A
BORE 405 3 HRS 100% A
THFT 305 3 HRS 100% A
LIES 205 3 HRS 100% A
SCUR 101 3 HRS 20% F
MONO 400 3 HRS 100% A
CONV 101 3 HRS 10% F
HID 205 3 HRS 70% C
OVERALL AVG. 78% C
This explains why mediocre rules the market.
Re:Microsoft's Report Card (Score:2, Funny)
Is that next-door to the Skool ov Speling?
Re:Microsoft's Report Card (Score:2)
"School of Capitalism"
Thanks for pointing that out. It's late at night in this part of the world. I guess I get a B for speling.
(Yes, that was intentional.)
Improved marks!? (Score:2, Insightful)
Give them an "F" on the report card (Score:5, Insightful)
Re-writing Windows from the ground up seems to me to be the best remedy. Forcibly breaking backwards compatibility should be a design goal.
Is (Score:3, Funny)
Re:Is (Score:4, Funny)
I don't know about the 7799 part, but Microsoft is certainly BS certified.
Re:Is (Score:2)
Confusing figures... (Score:2, Insightful)
It says here, Mr Gates, that you released 32 security advisories and 21 vulnerability fixes for Windoze 2000 Server in the first six months, yet for Windoze 2003 server you 14 flaw fixes and 6 critical issues...
Would this be because W2K3 server is based on Windoze XP code and that the majority of bugs had been ironed out already in the months between the releases?
hmmmm....
I think a fairer summary is... (Score:5, Interesting)
Sure they've progressed in terms of there's more known security holes fixed now than there was 1-2 years back, but there's also far more security holes that have been identified and at (seemingly) a much faster rate than 1-2 years ago.
In other words, 2 years ago, they rated a 4/10 in terms of security. Today, I'd say they probably rate 20/50. Overall, my impression is that they've essentially stayed in place in terms of removing security holes from their products.
If you think that I'm being unfair, consider how long it's taking new security holes to get fixed now versus 2 years ago - it seems to be generally longer.
Also, consider that MS has now taken the step of bundling security updates into big bunches, to ease the pain of applying them - that they've had to resort to this is a reasonable indication (IMHO) that the quantity of security holes being *fixed* has gone up significantly.
Finally, consider the rate at which security holes are being uncovered - it would have to start dropping off dramatically if MS was being successful in fixing their problems. That certainly doesn't seem to have happened.
agree (Score:4, Funny)
Have to agree there. Two years ago, it would have been a solid F (us) or 6 (de). Today it's an E (us) or 5 (de).
Re:agree (Score:3)
"F" (Score:2)
Re:"F" (Score:2)
Does not work well with others.
Disruptive in class.
Fails to finish assignments.
Attendance problems.
Re:"F" (Score:2)
Microsoft Culture (Score:2, Insightful)
Same goes for Apple (Score:4, Interesting)
Apple has some good programmers
Apple management has a GUI focus
Still Apple doesn't make conceptual security flaws like requiring root privilege for any user to perform even the most basic tasks.
--
Every program has two purposes -- one for which it was written and another for which it wasn't.
Yeah, right... (Score:5, Insightful)
For an indication of just how seriously Microsoft is taking security, rather than quickly fixing the bug, Microsoft is advising users to manually type URLs rather than click on hyperlinks [microsoft.com]. Well, of course, only malicious hyperlinks... but because of this bug, a scammer's link appears to be to the genuine website. Of course, they offer other gems, such as a chuck of javascript you can run to tell you the URL of the website you're actually viewing, since their software can't be bothered with giving you a correct indication. Or you can launch notepad and copy a shortcut. Yeah, everyone should have to go to the trouble of doing these steps, because they couldn't manage to get a fix out quickly (within the 1 week between the disclosure and scam artists starting to use it to trick end users to disclose sensitive indo). Microsoft also suggest viewing email at text-only... effectively reading all the html source, and changing to the high security profile )turning off all the dangerous technologies they have "innovated" over the years: ActiveX, scripting, etc...) not because they will help you avoid being tricked, but because it will limit the damage.
All because they couldn't fix this simple problem quickly.
Yeah, that's taking security seriously!
Re:Yeah, right... (Score:2)
Because they're not taking security seriously, they're trying to put their customer's minds at rest and stop them jumping ship.
If they were taking security seriously, they wouldn't prevent pirated copies of XP from downloading critical updates, this is perhaps a poor analogy but it's the first one that springs to mind, let's look at the automotive industry...
Imagine 95% of the cars on the road are Fords, and every time a problem is found with a For
Re:Yeah, right... (Score:3, Interesting)
They blocked the number one pirate CD key from downloading them even before SP1. And, with SP1, they blocked around 150 other "commonly used" pirate CD keys.
That doesn't mean there aren't other corporate keys that are valid...corporate keys bypass activation so there's no validity checks. If it's a corporate key leaked from a large company, it's feasible that it could go unnoticed for a long period of time before being caugh
Re:Yeah, right... (Score:3, Insightful)
Interesting; I take it that you've seen the IE source code, then? I mean, you have to have, to know that it's a simple problem that can be fixed quickly, rather than something buried deep in the bowels of the code in a module that has hundreds of dependencies - or even something buried deep in the bowels of the OS/MFC, with thousands of dependencies.
No, I don't think it's likely - but you're spouting supposition as though it were gospel. Unless, o
this was the original plan (Score:2)
Seems that MS is trying to undertake PR in a very SCO-like fashion lately.
Seeing it in another perspective (Score:5, Insightful)
Consider a pretty standard setup--the OS, plus ftpd and httpd--here's the count of errata advisory between M$ Win2k Server and RedHat 9:
Microsoft: 1, for the botched FrontPage Extension patch released in November.
RedHat: 4, for the following:
1. Dec 2nd: Updated 2.4 kernel fixes privilege escalation security vulnerability RHSA-2003:392-05
2. Dec 16th: Updated lftp packages fix security vulnerability RHSA-2003:403-07
3. Dec 17th: Updated httpd packages fix Apache security vulnerabilities RHSA-2003:320-09
4. Dec 24th: Updated 2.4 kernel fixes various bugs RHBA-2003:394-08
Not to mention I will need to think about what to do when RH9 becomes EOL in April.
Interesting.
I am by no means by pro-MS here. If I have my way it'd be all qmail and publicfile. In fact, I don't have the balls to put my company's Exchange server directly on the 'net; I put it behind a RedHat box running perdition, and have qmail as the MX, behind an IOS IDS/FW.
Trust needs to be earned, and MS is slowly earning mine in the security front. I don't trust MS software enough to stick them directly on the Internet yet, but they did earn my trust to let Windows Update automatically sort things out: Not a glitch in the last 18 months.
The fact of a matter is, with a little clue as a admin, Windows can be made pretty secure. Being clueless, Linux can be made to be a big wad of swiss cheese.
We Linux and
Now that you have the facts... Go ahead, mod me down.
Re:Seeing it in another perspective (Score:3, Insightful)
incomplete after a while becomes... (Score:2, Funny)
Glass Houses? (Score:5, Insightful)
All of that being said, no technology area is devoid of security flaws. Look at the recent attention given to H.323 standard vulnerabilities due to default ASN.1 parsing. That affects many vendors and product lines. Today I read an ISC diary entry [sans.org] detailing a couple of exploits that affect non-Windows environments. Apache, OpenSSH, QMail, Sendmail, etc. have all had their share of recently announced flaws.
Of course Open Source Software *should* be more secure since many eyes can review the code as it is maintained and updated. But the fact that nevertheless there are significant flaws and exploits in this area further proves my point. Microsoft is the largest software company on the planet so of course they have a target on their back. There are no doubt many third party organizations dedicated to doing nothing but trying to break Windows in order to submit security reports. Of course there are anonymous black hats doing the same but for other obvious reasons.
If the same manpower and effort was dedicated to breaking Linux and OSS applications (which currently have much less exposure and market share) I am sure that even more holes would be poked into what most folks on this board defend as being the silver bullet against corporate greed, monopolistic tyranny, and gaping security holes.
It's going to be a long, difficult march (Score:3, Insightful)
Re:Microsoft Security (Score:5, Insightful)
Well that's an easy answer. It's all about educating 'users'.
1. Don't open emails unless you are certain it is from a trusted source.
2. Keep your system patched
3. Ensure you have Anti Virus software installed, and up-to-date.
4. Use the firewall built into XP, or install one of the many free (for personal use) 3rd party firewalls, or even better look for an ISP that firewalls sensitive ports for you.
This is all basic stuff, but many home users don't really give a stuff if their machine is taking part in a DDoS attack, as long as they can still get to their email, view web pages, send instant messages and download pr0n (actually - forget the last one, that's us geeks)
Re:Microsoft Security (Score:5, Insightful)
That's the big problem here. When your email client, by default, displays HTML and executes macros and scripts, you're extra vulnerable. Even if it's from your pal Bob that you've known for 40 years, his computer may have been owned by a worm and just emailed all his friends seeking to propagate. You say 'hey it's from Bob, I trust him' and open it. Boom, you're owned too, and may never know it.
Bad design is bad design, there's no two ways about it.
Re:Microsoft Security (Score:2, Interesting)
Re:Microsoft Security (Score:2)
In the past 3 years I have only used linux at home. Never had to worry about viruses, nor spam (yeah, that's right, I averaged 2-3 peices a year), nor spyware (spam maker), nor adware (spam maker), nor web browsing issues (IE security flaws). Now I spend more time cleaning up all this crap then anything cause I have to have a winblows box at home so i can do
Granted I kept the system patched, and use
Re:Microsoft Security (Score:5, Insightful)
Your choice of OS doesn't make your system secure. What makes a system secure is a user that has a clue.
In the past 3 years I have only used linux at home. Never had to worry about viruses, nor spam (yeah, that's right, I averaged 2-3 peices a year), nor spyware (spam maker), nor adware (spam maker), nor web browsing issues (IE security flaws). Now I spend more time cleaning up all this crap then anything cause I have to have a winblows box at home so i can do
Like you, I've not had a Virus in countless years. I don't get spam, My system has no spyware, or adware or web browsing issues (Firebird rules!), and I run a Windows box (Prerequisite of being a Windows Sysadmin). Had I have been an uneducated user, I'm sure I would have fallen fowl of most (if not all) of the issues you have listed.
But at least I never had to reinstall my entire OS because a windows update failed (which just happened to my brother yesterday, and I have seen it several other times, too!)
There are aproximately 3000 Windows PC's on the university network that I admin, and I don't see Windows Update issues that you see. Occasionaly a patch will fail, but if you know what you doing it is quite simple to fix, without having to resort to a complete re-install. Reinstalls are for failed disks and compromised machines.
So, no, it is not just about educating users, it is about makeing a more secure system!
But who makes the system secure? Why _educated_ users do. - If a user is clueless, the odds are that they will be compromised, regardless of what OS they choose.
Windows is crap,when will the world realize this?
I'm beginning to think you are a troll.
Re:Microsoft Security (Score:3, Insightful)
Look to the past to see the future: when radio first began it was completely unregulated because no one knew exactly how it even worked. Even after radio receivers had become affordable enough to enter "middle
Re:Microsoft Security (Score:2)
That's rather unfair - the vast majority of home users don't know what a DDoS attack is, and wouldn't know how to tell that their machine is involved in one.
Re:Microsoft Security (Score:2)
Or, MicroSoft could just turn off the services by default.
But let's get realistic, Microsoft doesn't really have an interest in security, in fact I'd argue they prefer to keep their OS from being "too secure" on purpose.
Re:Microsoft Security (Score:3, Insightful)
Seriously though, it's good to see that Windows 98 support has been extended. I shudder to think how many compromised Windows 98 systems there are out there now, let alone imagine how many there would be in 6-12 months time once vulnerabilities that hadn't been patched before support was dropped began to be exploited in earnest.
Re:Microsoft Security (Score:3, Informative)
Microsoft Security. What's it all about? Is it good, or it is whack?
I'd have to say whack. As is this report. Crowing about the lack of reported vulnerabilities means nothing when you have paid [theregister.co.uk] security firms [securityfocus.com] not to report vulnerabilities [attrition.org]! Of COURSE the vulnerabilities reported have decreased. But have the real vulnerabilities decreased? Thanks to Microsoft, we will never know.
Without subjecting themselves to the same review other operating systems undergo, they have no cause to crow about a perc
Re:Secure Means (Score:5, Funny)
Re:Secure Means (Score:2)
They'll move the building to an entirely different location, that they will call by a "hi-tech" acronym, and change the design without letting anyone see the blueprints. The new delivery bay will be the wrong size for current trucks. They will set about making all vehicle plants change to the new size trucks and will tell everyone the new trucks are better as they can't interact with old "insecure" buildings.
People will continue to break into the building by using the hug
Re:Secure Means (Score:4, Funny)
Re:Secure Means (Score:2)