Study Finds Windows More Secure Than Linux 796
cfelde writes "A Windows Web server is more secure than a similarly set-up Linux server, according to a study presented yesterday by two Florida researchers." In addition to the Seattle Times article, there is also coverage on VNUnet. From the article: "The researchers, appearing at the RSA Conference of computer-security professionals, discussed the findings in an event, 'Security Showdown: Windows vs. Linux.' One of them, a Linux fan, runs an open-source server at home; the other is a Microsoft enthusiast. They wanted to cut through the near-religious arguments about which system is better from a security standpoint."
Just what we need... (Score:4, Insightful)
These studies are pointless. Both can be secure (Score:5, Insightful)
A webserver needs port 80 and maybe 443 open. Any webserver can be secured.
Where's the news?
Newsflash... ONE Linux Fan.. (Score:5, Insightful)
A Linux enthusiast at the RSA Conference in San Francisco has reluctantly concluded that Microsoft produces more secure code than its open source rivals.
In an academic study due to be released next month Dr Richard Ford, from the Florida Institute of Technology, and Dr Herbert Thompson, from application security firm Security Innovation, analysed vulnerabilities and patching and were forced to conclude that Windows Server 2003 is more secure than Red Hat Linux.
Now, I'll concede that Dr. Ford and Dr. Thompson do sound reputable, but one is an admitted Windows enthusiast and while the other one is a Linux fan who changed his minds, this hardly sounds like a study
It's an interesting question, and I'm sure there is no clear cut answer, but a more systematic study (with more parties, rather than just two scientists) is going to be needed to answer this sort of question before the 'results' are trumpetted. I'm sure Microsoft will pick this one up and run with it, however.. more of those annoying ads that seem peppered throughout Slashdot.
Not again... (Score:5, Insightful)
So Windows is more secure than Red Hat because Microsoft chooses to report less vulnerabilities and release less patches? Hmmm...
(Move along, nothing new to see here.)
Non Story (Score:5, Insightful)
The security of a server... (Score:5, Insightful)
Now let the flaming begin, so you can all argue about the number of patches/updates required for each system, how long it takes for Linux/Windows to respond to problems, and all that good stuff. We all know that's the only reason this kind of story shows up on Slashdot is to start a good flame/troll war!
Self-Evident (Score:5, Insightful)
I'm no zealot (Score:5, Insightful)
No matter how fast a patch is issued, you still have to install it for it to work.
Delay in announcing MS vulnerabilities? (Score:5, Insightful)
Re:These studies are pointless. Both can be secure (Score:2, Insightful)
Re:Hardly scientific isn't it? (Score:4, Insightful)
Hardly a study (Score:5, Insightful)
Sorry, but this "study" is not a study.
Why was this even posted?
Well at least it's nice... (Score:3, Insightful)
A lot more could certainly be done... (Score:5, Insightful)
OpenBSD runs chroot() Apache. Does IIS have similar capability?
The chroot() patch was never taken up, but it would probably not be that difficult to install on Linux.
I would be disinclined to run any other way at this point.
Not only that, but I find this quote odd.. (Score:5, Insightful)
Umm, so MS showed him their source code? I find that a little hard to believe.
If he can't see the source, how can he make any determination at all?
Reproducebility? (Score:4, Insightful)
Such professional sources (Score:3, Insightful)
I'll take a nice report by computer scientists and security experts about overall system design over crap papers like this any day.
Re:These studies are pointless. Both can be secure (Score:2, Insightful)
"Days of Risk" vs. Full Disclosure (Score:5, Insightful)
Secondly, there's no discussion of how the criticality of a vulnerability was weighed. If every "day of risk" for Windows was "critical," and every "day of risk" for RedHat was "moderate," then I'd differ with their conclusions. Further, there was no mention of whether they considered actual exploits in the wild.
Re:Integrity? (Score:5, Insightful)
Their criteria included the number of reported vulnerabilities and their severity, as well as the number of patches issued and days of risk -- the period from when a vulnerability is first reported to when a patch is issued.
I hoped for a deeper analysis, like the security model used or how it behaves in networks. But it just back to counting vulnerabilities.
--Nothing to see here, move on.
Re:The security of a server... (Score:3, Insightful)
-----------
Both were in the most basic configuration, an approach that some in the audience suggested may tilt the results in favor of Windows, which comes with more features.
Ford said the idea was to represent what an average system administrator may do, as opposed to a "wizard" who could take extra steps to provide plenty of security on a Linux setup, for instance.
---------
Define 'Wizard', and this may be informative. Otherwise, it's bunk.
Re:More FUD (Score:3, Insightful)
A study comes out saying Linux is better than Windows? Praise it to high heavens! We knew it all along!
A study comes out saying Windows is better than Linux? Question the results, Impugn the source and dig as deep as it takes to find some political or financial affiliation between them and Microsoft, no matter how assinine or inconsequential.
Severity of Vulnerabilities? (Score:3, Insightful)
"The pair examined the number of vulnerabilities reported in both systems and the actual and average time it took to issue patches. In all three cases Windows Server 2003 came out ahead, with an average of 30 "days of risk" between a vulnerability being identified and patched compared to 71 from Red Hat."
There is nothing said about the severity of the vulnerabilities. This article would never make it in a peer reviewed publication.
Study did not prove Windows more secure than linux (Score:3, Insightful)
Re:These studies are pointless. Both can be secure (Score:3, Insightful)
>
> A webserver needs port 80 and maybe 443 open. Any webserver can be secured.
A workstation doesn't even need that.
Not counting the (numerous) local exploits caused by IE, WMP, Outleak and other applications getting pwn3d by their handling of hostile content, the big (i.e. "remotely exploitable without user intervention") holes in Windows all stem from M$'s unstated design assumption that "all the world's an office LAN", and the open/listening status of ports 135, 445, 5000 (anyone remember uPnP, the first 2K/XP remote exploit?), UDP-1434 (SQL server) and the like.
If your business is based on selling an office application suite (and you're trying to extract a few more bucks from your office suite sales by requiring that someone buy your operating system to run it), then assuming that all the world's an office LAN is a pretty natural thing to do. It's wrong, it's flawed by design, and it's the canonical example of valuing ease of use over security, but it's pretty natural.
My problem. (Score:3, Insightful)
If a company or individual is actually doing this how on Earth can they possibly attest to the security of their server?
Re:Integrity? (Score:5, Insightful)
I challenge the assumption that Redhat vulnerabilities are equal to Microsoft vulnerabilities.
Given the history of malware, they clearly are not.
This study is nothing more than a more formalized version of a certain form of trolling once popular on COLA.
Does Microsoft pay Security Innovations bills? (Score:0, Insightful)
This should be disclosed in any report that is critical or praises a particular Microsoft product.
Re:Hardly scientific isn't it? (Score:3, Insightful)
A valid comparison? (Score:4, Insightful)
Re:Non Story (Score:4, Insightful)
Red Hat = Linux
Microsoft > Red Hat since it announces less vulnerabilities
Therefore Microsoft > Linux by the transitive assumption...
Seriously though, that's the problem with EVERY SINGLE one of these "security studies" -- they don't "study" anything, but they do "research" -- and they always use the same, weak argument as described above.
Horribly flawed (Score:5, Insightful)
Are they joking? Their metric (reported vulnerabilities) is absurd for a number of reasons.
1) Microsoft reports only a fraction of its vulnerabilities. Remember when Win2000 had over 65000 known (to Microsoft) flaws? No more than a handful were ever reported. Microsoft reports flaws only after bearing enormous public humiliation. Of course Microsoft's flaw count is going to be low. Microsoft hides them all until forced to disclose.
2) Linux vendors report every hair out of place. It doesn't matter if the flaw causes a D to look like an O on the third day of the Summer Solstice, but only if that day matches the 4th digit of PI, and only if the computer has calculated the cure for cancer at exactly 15 milliseconds after the user's orgasm.
3) Seriousness of vulnerabilities. Due to the nature of full disclosure under Linux, it will -always- have higher reported flaw counts than Windows. The vast majority of reported Linux flaws, however, are relatively benign, while the vast majority of reported Windows flaws hand over complete control of your computer to some third party.
4) Widespread Propagation. Windows, by its intended design, makes propagating exploits to these vulnerabilities trivially easy (automatic, actually), while this has yet to be accomplished on Linux (and likely won't be).
Sorry, but this "study" is complete nonsense.
Quality Research (Score:5, Insightful)
Re:Newsflash... ONE Linux Fan.. (Score:5, Insightful)
I'm getting a little disturbed at the way all pro-Linux studies are being accepted and all other studies are being dismissed here. Critical thinking should always be welcome. And, yes, Linux is NOT perfect, it is NOT flawless, and it IS full of security holes like anything else. Nobody should take their operating systems so personally that they feel attacked when Linux is criticized.
Note that this doesn't go for everybody. But there are a lot of zealots in the community who need to learn to see outside their own perspective.
If you lean WAAAY over to the left... (Score:5, Insightful)
The researchers used reported vulnerabilites as their guideline, and 'days of risk;' quote: "the period from when a vulnerability is first reported to when a patch is issued."
Windows Server 2003 had 30 days of risk, Linux (Red Hat Enterprise Server 3) 71 days.
But which reports of vulns are they considering? Microsoft often provides their own reports, which are released WITH THE PATCH. I wouldn't give those reports the same weight, since the vuln could have been there (and unofficially known) for MONTHS.
I fully expect Linux to have MORE vulns in any case, since Linux ultimately is a collection of separate programs working together, each of which has their own potential insecurities. But, a vuln in sendmail is NOT going to affect my webserver, because I'm going to turn that OFF (if I'm a smart admin).
In fact, the researchers only used a "hypothetical" system to show "what an average system administrator may do." I'm sorry, but if an admin is using anything like a default setup he is BELOW average.
In conclusion, this really sounds like a comparison of how vulnerable the respective systems with a 'default' install. Wake me up when they go head-to-head with OpenBSD.
P.S. Hey researchers- RED HAT IS NOT LINUX.
How these statistics could mislead... (Score:4, Insightful)
I don't know which OS has more risks, has a greater delay between discovery and announcement, or has a greater delay between patch availability and patch application. Does MS or Linux get more slack from vulnerability finders? Do MS or Linux admins patch faster? DOes MS or Linux get more vulnerabilities? These data points would help evaluate the true risk.
Re:Integrity? (Score:5, Insightful)
The correct answer is the one with the better administrator. You can have a Linux box locked down tight, and a Windows box wide open. You can also have the inverse. Probe around, and you will find boxes of all those flavors out there. It all depends on the competence of the guys running it. The competence of the administrator at running the system he is running has a much larger effect on overall security than which OS is chosen.
Re:Hardly a study (Score:3, Insightful)
Re:Not again... (Score:3, Insightful)
Your post has to be the fourth one I've seen that has said the exact words "Move along. Nothing to see here."
Why so desperate for people to not see it? Linux is not flawless. In fact, it's not been the best of years for it (Firefox as well). I'm sorry, but as popularity grows, so will the security reports pointing out the inherent flaws in any complex system constructed by human beings.
The need to be better than Microsoft has to go. Just concentrate on fixing what is wrong with Linux when it's pointed out. This isn't a popularity contest, right?
Linux thrives on criticism (Score:5, Insightful)
Linux is awesome, this study doesn't change that but we always need to work to make it better and easier to secure. Critics of Linux are our best friends, because they do the work of finding out where we need to improve for free.
The best thing about linux is that when people have a legitimate complaint, it's well within our power to fix it! If Linux is temporarily less secure, so what? After reading this, everyone will adapt their linux distros to render the complaints moot.
This is part of why we love open source, right?
Two random guys say... (Score:2, Insightful)
is that an average windoze SA or an average Linux SA?
They do mention they are not "wizards" (Score:3, Insightful)
And you're going to need those resources if you're not a "wizard". Open Source software is not as easy to use as most MS products, and in many cases the documentation isn't very good either.
Re:Not only that, but I find this quote odd.. (Score:2, Insightful)
Easily; you don't have to have access to source code to make a determination - you can make many external determinations by treating things as a black-box. It's a myth that only open-source code can be secure.
We don't understand the "source-code" of DNA, and yet we make millions of determinations about other people, every day.
Re:Newsflash... ONE Linux Fan.. (Score:4, Insightful)
When a study is contradictory to most peoples direct experience and observations they tend to be heavily skeptical. If a study was released saying the sky is really mauve, not blue, people are also going to be pretty dismissive. When was the last time you read about a Unix/Linux worm or virus on a nontechnical site like CNN? Or heard about it on the evening news? Ever heard these things about Windows? This isn't to say that the study is invalid, just that they better have a damn good case if they expect to convice anyone.
Re:Hardly scientific isn't it? (Score:4, Insightful)
Sure doesn't sound like it's aimed at IT admins. If your IT department doesn't have anyone who's competent to secure and maintain the system(s) you use, it's the fault of management, not the software (nor the admin).
Hey, my plywood outhouse is more secure than Fort Knox.. as long as the outhouse has a padlock and Fort Knox is unlocked and unoccupied. Putting one competent gaurd in front of the entrance to each highlights the real defendability of both.
A crayon is ready to use right out of the box - a pencil has to be sharpened. Strangely, we use more pencils than crayons in the workplace. Why? Because it's better. Someday, a PHB will touch the obelisk, and stand upright. Until then, we're stuck with cray^H^H^H^H windows.
The Real Truth... (Score:5, Insightful)
An OS is only as secure as it's admin is competent. This will NEVER change no matter what platform you are dealing with.
If you give some RedHat CDs to a complete goof off and have them install it on a system that is going to be directly exposed to the internet, that box is going to get rooted eventually. It might take longer to get rooted than a Windows box, but it will be cracked.
If you give Windows 2003 Server to a knowledgable admin, he will secure the box and make certain that the likelihood of it getting cracked is fairly low. He will know not to put the box on the internet until he's applied all SPs and critical updates. He will know to use an internal SUS or WUS to make sure that the box is updated without exposure to the internet.
If you give a complete moron who *thinks* he knows all about [insert platform] any installation media, you're going to have an insecure box.
It's been my experience that the best people to set up an internet exposed box using any OS are people who are most familiar with all OSes and have a good understanding of how to secure each one. It's not that hard to hit the main security points and still keep on top of all OSes. However, since egos aer so intrinsically tied to how secure a box is, people point the finger at the OS distributor. Sure, they are to blame in many cases, but the implementor is usually far more guilty of being lax. That's the hard truth and it cannot be refuted.
Re:Self-Evident (Score:1, Insightful)
No, what he is saying is that the assumption was that a wizard wasn't available to fix all the problems with the Linux setup.
Re:Horribly flawed (Score:3, Insightful)
Re:More FUD (Score:5, Insightful)
It is useful as an anecdotal example. Especially in the area of security, where real security tends to mean knowing a lot of very specific examples of how things can go wrong. Documenting how these guys could have inadvertently left holes open would be useful. Then we need several hundred more such paired tests, with a more extensive report listing all the ways that admins of both systems can get it wrong.
But concluding that, because two guys didn't get it right in a single test, therefore one of the systems is more or less secure than the other, shows little other than a total lack of understanding what security is all about.
That, or intentional FUD on the part of either or both.
I'd go with the lack of understanding. People are really good at generalizing from a single case with no statistical significance.
Re:Integrity? (Score:5, Insightful)
Another is that just counting vulnerabilities gives you a worst-case scenario. However, my practical experience suggests that if there aren't any script kiddie tools or viruses out there that take advantage of said vulnerability, your chances of getting compromised through it are exceedingly small.
I'd also like to see some weighting for the likelihood of an attack succeeding through a given vulnerability. I'm going to be a lot more scared of the exploit that works every time than I am the buffer-overflow that lets you run arbitrary code, but only works once in a blue moon.
Granted, these studies will never have that info; they aren't meant to mean anything, they are just mindcandy for the PHBs put together by industry pundits looking for a quick paycheck or some attention. If I were really looking for a security analysis or comparison that included an open source server that ran on x86 hardware, I would expect OpenBSD to be one of the operating systems tested.
Re:The Real Truth... (Score:2, Insightful)
Re:Not again... (Score:3, Insightful)
FUD and a Never-Will-Be-True Assertion (Score:5, Insightful)
But, RH isn't Linux. Linux is many distributions, some good, some not so good, but if you take the pool of Linux administrators against the pool of Windows administrators, you'll find Linux administrators are more knowledgeable about their systems and do smarter things in securing them. This isn't as true as it was a few years ago before the reluctant Windows administrative masses took refuge in RedHat, but you won't see _any_, not even one Linux defector to Windows. Perhaps BSD, but definitely _not_ Windows!
I've never seen one of my Slackware servers (running sendmail, _even_ and FrontPage extensions with PHP on the Apache server) compromised. It's never happened in the 10 years I've been using them.
I've been wasting a lot of time lately poring through logs for a new project and it's ludicrous how much additional coding I've had to put into my Perl scripts to make allowances for compromised Windows boxes that have inundated my web server with traffic during their Code Red and Slammer compromises, not to mention all the other little oddities Windows clients do when downloading mp3s from the server, such as client caching and sending 32k+ search strings in the URL. It creates work to have these obnoxiously configured client machines on the Internet.
I'm not going to complain too loudly since without all these Windows users on the Internet surfing my site, there wouldn't be much of interest to process in these logs, but to assert Windows as more secure than Linux?! Really....
Could someone please post the name of which Micro$oft C?O's budget backed this study, so we can move on to a more interesting and valid discussion?
Hmm... true (Score:3, Insightful)
I would have to agree. Windows IIS servers are insecure, if you set up an Apache server similarly (insecure), it will also be insecure.
Re:Newsflash... ONE Linux Fan.. (Score:3, Insightful)
As right people should be dismissive. The sky is neither mauve nor blue, it has no colour. Blue light scatters in the atmosphere causing it to look blue.
Nearly half that article had nothing to do with Linux or Windows security.
Re:The Real Truth... (Score:5, Insightful)
Windows isn't "just another OS"... it has the rather unique position of being on a substantial number of desktops in people's homes. In and of itself this is not a problem and requires no greater security, however, a significant percentage of _THOSE_ systems are also on the Internet. And of course, the problem is that most people are simply not qualified to do a respectable job of administering and securing their home computer. Which brings us to the point you mention. The security problem with Windows are primarily caused by the inescapable fact that most of its users *ARE* ignorant when it comes to security and the fact that MS chooses to continue to market its products at this demographic while at the same time ignoring security issues or sweeping them under the rug is why people may be inclined to blame the operating system or Microsoft for the problems.
Although, interesting enough, if Darwinism really works, Windows users may ultimately adapt to having to always struggle to keep their boxes secure, and perhaps even end up being better than most Unix gurus at home computer security. Time will tell.
While I don't like this article one bit... (Score:2, Insightful)
Keep in mind that most admins are lazy, and that while we can yell and scream that a default setup is not secure nor is it a good indication of being secure, it still should be somewhat secure out of the box. If it's not, then we have a problem and we're supplying the ammunition to the FUD machine that is MS.
Re:Integrity? (Score:1, Insightful)
Also I think the point here was particularly good (Score:5, Insightful)
It's not all that useful to research how tight a competent admin can lock down a box because the answer for almost any OS is "very well". You get a good admin that knows their OS and is on top of things, they can keep anything secure, even Windows. So it's not of much use to say a compentent Linux admin can make a secure system, we already knew that.
It is useful, however, to know that a less competent admin will have trouble. More useful would be to know what specificly need to be done to fix it, but just knowing that it's a problem is a start. If Linux continues to gain in popularity, more people that are not as competent will be running it. While you can never truly protect someone from themselves, there are things you can do to make things more secure for those that don't know what they are doing, and that's a good thing for Linux developers to be looking in to.
Re:Integrity? (Score:5, Insightful)
Actually, this tells us most of what we need to know. If we want our system to be considered secure, the way to do it is: 1) Don't report vulnerabilities; 2) Don't issue security patches.
Linux pretty much has to lose a contest that is judged this way.
Biased? (Score:5, Insightful)
As someone said, "extraordinary claims demand extraordinary evidence". In a lot of peoples' opinion, the claim that Windows is more secure than Linux is just that, an extraordinary claim.
How would the authors of their study reconcile it with something like this one [theregister.co.uk], which showed that a default installation of Windows got infected with a virus within 20 minutes?
Once again, RTFA! (Score:5, Insightful)
From TFA:That sounds good. A real comparision of real services running on real servers.
But wait!They aren't real setups.
And it gets worse.Hmmmm, I wonder if they included the info from www.eeye.com http://www.eeye.com/html/research/advisories/AD20
So, a "study" that doesn't test any real world criteria is somehow valid?
Oh, it's not that the study is not valid, it's that pointing out the flaws in the study shows the groupthink on
And pointing out that perceived groupthink gets you mod'ed up as "insightful".
Re:More FUD (Score:1, Insightful)
A study comes out saying Windows is better than Linux? Question the results, Impugn the source and dig as deep as it takes to find some political or financial affiliation between them and Microsoft, no matter how assinine or inconsequential.
Hear hear. This absolute black and white "conviction" and group rage is ruining more for the credibility of "the community" than most people imagine. We just look like crazy fundamentalists.
Re:The Real Truth... (Score:5, Insightful)
The primary questions include:
1) How *securable* is the OS?
2) How gracefully do services respond to failures?
Secondary questions (addressed in this study) include:
1) How secure is the OS *by default.*
2) What constitutes a typical setup?
Now, personally I don't care much about these secondary questions from a secure server perspective. Linux security is easier than Windows security, and Linux is more securable than Windows. A lot of this is because Windows depends on things like RPC which does not fail gracefully.
On the other hand, you can mitigate a lot of this risk by proper security practices. A skilled admin is going to be trying to balance usability and security and will do it well if given the approrpiate tools.
Again the quesition should be "how securable" rather than "how secure" for exactly the reason you mention.
Re:The Real Truth... (Score:4, Insightful)
Think of the gold in Fort Knox as your personal information, and think of the fort itself as the server or PC.
Fort Knox is not secure because it was easy to do, nor is it secure because they spent ungodly amounts of money securing it. Fort Knox is secure because it was well thought out, well implemented, and has been modeled after the sum of innumerable years of open ideas about how to build a stronghold. The idea of hiding all that gold under a rug and hoping nobody will notice is utterly absurd. All it would take is for someone to accidentally kick the rug or tell just one person where the gold is and its all over. Conversely all it would take is just one person to talk about a hole in Fort Knox to have the entire Army in Kentucky in a matter of hours.
Oh yes it is. (Score:3, Insightful)
If you want to see which car is safer than another, you would do things like controlled crash tests and use crash test dummies.
You would NOT factor in how many crashes they had both been in. One moron who keeps hitting telephone poles would alter the stats too much.
The material in TFA does NOT show them comparing the security models or even the patch severity. One bug in a seldom used perl module that lagged on the fix could result in very bad stats for Red Hat.
Re:More FUD (Score:5, Insightful)
That's a critical difference. So many people pour over the Apache source code that most vulnerabilities are discovered prior to when they actually become "in the wild" exploits. The same cannot be said about MS IIS. Worse, the odds are very good that many the IIS exploits were in the wild prior to when they were first publicly reported, while most of the Apache exploits were, in all likelihood, patched prior to the first exploit.
When viewed from that perspective, the Windows/IIS server was likely vulnerable to exploit for many, many more weeks than the Linux/Apache server. And that assumes that half the vulnerabilities are ever even reported. With a closed source product, there could be tons of security holes being subtly exploited by clever crackers every day and there would be no way to find out about it.
No, this article is pure and unadulterated FUD.
There are three kinds of lies: lies, damned lies, and statistics.
---Benjamin Disraeli
Why is it that ... (Score:3, Insightful)
Microsoft 12137446 20.86 12322111 20.85 -0.01
Sun 1830008 3.14 1835718 3.11 -0.03
Zeus 690193 1.19 618599 1.05 -0.14
Given those statistics (source - netcraft) why is it then, that we dont see malware attacking apache on such a grand scale as we do IIS? If its possible for an operating system with such a small percentage of the (server)market to suffer from such virulent malware attacks - then why do we not see these problems on linux which has a comparatively small share of the desktop market?
I call bullshit!
I've been seeing this coming for a while though as people find new and exciting FUD campaigns. Does anyone know who funded this report ? need I even ask that question?
Nick
Re:More FUD (Score:5, Insightful)
Also, many OSS exploits are theoretical in nature... if a strcpy() passes an unchecked ptr and some coder sees this... whether or not that code could have been exploited... he fixes it and out goes the patch. Its a patch for something that may have never been even able to be taken advantage of. That would never happen in a commercial project. All this study shows is that these researchers define security as the ability to hide security problems as long as possible until a patch is ready and if the patch never gets ready, just never tell anyone about the problem. Following the two above stated rules would easily make any software company "secure" by their standards. As stated previously, their criteria was # of patches and time to release. Time to release is shortened by waiting until the patch is ready (which Microsoft does) and # of patches is shortened by simply not releasing non-major patches and just rolling them out with the next version. The criteria these guys used was meaningless and if anything shows that linux is doing something right if they are updating several times more programs with only twice the delay (which i really doubt is the true delay time). One other thing worth noting, the Ford guy has been paid by Microsoft several times to do studies and release them in favor of MS, I'd hardly call him a true linux fan. Maybe this time they just covered it up better... you wouldn't want to bite the hand that feeds you.
Regards,
Steve
Could be severely flawed ... (Score:3, Insightful)
Re:Once again, RTFA! (Score:1, Insightful)
You mean this one?
"eEye Digital Security has discovered a vulnerability in Windows SMB client's handling of SMB responses."
Perhaps they didn't include it because this is a study of servers. Once again, RTFA. Dumb shit.
Further testament to slashdot's retardedness is that that exact same "insightful" comment is posted largely verbatim in each article where Windows is found to be more secure than Linux. and each time I post it, it gets modded to +5.
Re:A lot more could certainly be done... (Score:3, Insightful)
The article as has a point when it states that "linux wizards" could do a lot more to enhance the Linux machine's security compared to the default RHEL installation they were using. Indeed, why are vendors not using the complete assortment of Linux security best practices? Administrators almost always go for the path of least resistance -- whether Windows or Linux. As a result, Linux distros need to make absolutely sure that this path is also the most secure by default. And tools need to be written to make proper administration easier.
Re:A lot more could certainly be done... (Score:3, Insightful)
The whole "study" is silly. There is no such things as "more secure", unless you take into account WHO managed those machines. What's the point of having super-secure Linux server if admin leave '1234' as password? Security is not only technology (actually, technology is only small part of it) - it is much more. It is sociology (or whatever you call it in English).
I've been doing pentests for the past 13 years, and in many (and I mean it) cases I didn't need latest exploit (or any exploit at all) in order to gain access to resources.
You know, when you do proper information gathering and try to "think like an admin", miracles happen...
Glad the thoughtful analysis is going on here (Score:3, Insightful)
Folks, it's hard to maintain credibility if you heap praise on one study that agrees with you [theregister.co.uk] and then critique another sight unseen.
Wait for the study to be published, examine its assumptions, and try to reproduce it. I know it's not as exciting, but that's the only way anyone is going to get to the truth.
Security is a Process.. (Score:3, Insightful)
Re:Also in the news... (Score:2, Insightful)
As far as the European Imperial era, Christianity was often abused by the governments a front to support the looting and plundering of the rest of the world, rather than a primary cause.
Broad generalizations make us no better than these reports we keep complaining about.