ie8 fix
madison

Is Windows more secure than Linux for web serving?

By | March 23, 2005, 2:49am PST

At the risk of starting another holy war, I had to comment on this story. Robert Lemos reports?on a study?that concludes Windows is more secure than Linux for Web serving. Although the test was funded by Microsoft, the two authors of the study did publish all test methodology so that it can be independently scrutinized and repeated. In general, vendor-funded studies almost always favor the vendors that fund them. This statistic obviously makes sense, since no company would ever fund a study that they either expected to lose or if they couldn’t get the researchers to "fudge" the numbers in their favor. The big question here: Is this a case of fudging the numbers or is there some truth to it?

Since this was primarily a comparison of Web server technology, we’re mainly talking about IIS 6.0 and Apache 2.x. From a real world standpoint, it can be argued that other vulnerabilities pertaining to the underlying operating systems and other non-Web related components for Windows or Linux are less of a security priority.?A locked down Web server will only have TCP ports 80 and 443 open on the local firewall, whether you’re talking about Linux IPChains or Windows Firewall. Therefore, the only thing that is exposed beyond the Ethernet adapter of the server is IIS 6.0 or Apache 2.x, and these are the main things we need to worry about when evaluating Web servers. So let’s compare these two platforms’ security track records.

If we look at the SecurityFocus Web site vulnerability search page and we type in keywords "Apache 2" and "IIS 6.0", we will see that there is basically only one security advisory for IIS 6.0 since its inception, and we can see that there are many advisories for Apache 2. Unfortunately, the results don’t really elaborate on what this actually means in terms of severity of the advisories. A better?security research site is secunia.com which does go into much more detail with nice graphical analysis. When I searched Secunia, I found the following results.

IIS 6.0 track record:
IIS 6.0 has?only three advisories listed for for the last two years and none of the advisories were rated beyond moderate.?Two advisories were moderate and?one was rated low. Only one was not patched.

Apache 2.0.x track record:
Apache 2.0 has 22 security advisories and two were not patched. One was rated high,?seven were rated moderate, and 13 were rated low.

Both comparisons were from the year 2003 to 2005 and represent the most modern versions of their respective platforms, so it’s a pretty fair comparison. Based on this information, it is easy to conclude that IIS 6.0 has a much better track record than Apache 2.0.x and that Apache needed to be patched more frequently. In light of this data, we have to wonder if Windows 2003 server really is better than Linux and Apache for the purpose of Web serving. What do you think? Talkback and let your opinion be heard.

Kick off your day with ZDNet's daily e-mail newsletter. It's the freshest tech news and opinion, served hot. Get it.

Topics

Disclosure

George Ou

http://blogs.zdnet.com/Ou/?page_id=557

Biography

George Ou

George Ou, a former ZDNet blogger, is an IT consultant specializing in Servers, Microsoft, Cisco, Switches, Routers, Firewalls, IDS, VPN, Wireless LAN, Security, and IT infrastructure and architecture.

Related Discussions on TechRepublic

Did you know you can take part in these discussions with your ZDNet membership?
38
Comments

Join the conversation!

Just In

Who reports exploits?
Jick 3rd Nov 2005
It is well known that epidemiological statistics on diseases are skewed by changing attitudes toward various "afflictions" -- many non-life-threatening ailments appear to be on the rise because they are now reported where there were not before. Could the statistics on Web server security be subject to the same effect? Who reports exploits? Not the hackers who have found a way to wreak vengeance on their sworn enemy, that's for sure. Suppose you were a dedicated "Open Sourcerer", a founding member of the Linux Jihad, and you found a security hole in a Micro$oft product; would you tell Micro$oft? Would you tell anyone, except perhaps the hacker community? Doubtful. But if you found an exploit in Apache, the chances are much better that you would immediately let the developers know so they could fix it. I think you have to factor in the skewed reporting that results from widespread hatred for Micro$oft. (If you doubt that it exists, please estimate the ratio of viruses written for Windows vs. Linux.)
0 Votes
+ -
I'm sorry, but your topic is rediculous. It's purely pedantic to propose that windows is secure. Linux has many followers, and well that it should. Now take a look at some servers with muscle. Who are you kidding?
You said that Secunia was tracking issues with Apache 2.0 and IIS 6. Granted that IIS is almost surely running on Windows, but where does Linux come into this? Are you making unwarranted, illogical leaps?
0 Votes
+ -
Newspeak?
seosamh_z 23rd Mar 2005
..I'm sorry, but your topic is rediculous. It's purely pedantic to propose that windows is secure...

Thanks for clearing that up.
Pretty persuasive argument you have there.
Did you read the blog?
And if the topic is so ridiculous, why?


Joe
0 Votes
+ -
Newspeak? Nah, just ignorance
LGLisle 23rd Mar 2005
The original poster appears not to be a native speaker, but likes big words.
0 Votes
+ -
yet another round of pointless banter
barnesanova 23rd Mar 2005
first of all, java_programmer, you've spelled ridiculous incorrectly, which i think is ridiculous when you throw words like pedantic into your sentences.

second, hasn't everyone learned at this point that there are goods and bads to both? come on, let the war go. what a bunch of crap. i work with both, i'm competent in both, and both have some MAJOR annoyances. so stop bickering and do your jobs.

if i've annoyed you, well, that's redecoulous!
0 Votes
+ -
risk
dwest_z 23rd Mar 2005
"At the risk of starting another holy war...."

If you didn't want to risk it then why the title:

"Is Windows more secure than Linux for web serving?"

Why not a title like:

"Another M$ funded study finds Windows web server to be secure"????

Course that wouldn't get you as many readers.

Maybe it's because this is another pro-M$ article from the web IT news site funded by M$....
0 Votes
+ -
Comparisons
Roger Ramjet 23rd Mar 2005
Apache was a VERY stable web server - during its 1.x.x days. The change to version 2 was more revolutionary than evolutionary (IIS 6 was evolutionary from IIS 5). There were major issues with migration and stability as the 1.3.x Apache was replaced with the 2.0.x. To focus on the 2.0.x Apache is like focusing on - say, the reliability of a vehicle in its 3rd model year. The negative statistics of the 1st year, and partially negative statistics of the 2nd year tend to bring the rating down in the 3rd year - even if all of the "kinks" have been worked out. SO what model year is Apache 2.0.x in, and how far back are you taking statistics from?
0 Votes
+ -
Completely agree
Bata Srki 23rd Mar 2005
Not only that, but how many web servers out there do run Windows Server 2003? What is the ratio of said servers to Linux (and Windows) servers running Apache 2.x? If all those IIS 5 and IIS 5.1, not to mention IIS 4, boxes were replaced with the IIS 6 boxes, would you only see just 3 advisories. I think not.
0 Votes
+ -
All stats were from 2003 - 2005
george_ou 23rd Mar 2005
Your argument would be fine if it weren't for the fact that the stable Apache 1.3 had many vunerabilities in the 2003 - 2005 timeframe as well. Many more than IIS 6.0.

http://secunia.com/product/72/

I think you didn't read the section where I said that all numbers were from 2003 to 2005.
It doesn't matter which one has more security vulnerabilities, because all software has security vulnerabilities they just haven't all been discovered yet. Its more important to know which software is being targeted for exploitation. The software can be a full of holes as swiss cheese, but if no one is trying to exploit those holes it really doesn't cause any problems. M$ is the #1 target of hackers right now so that makes their software automatically less secure.
...but it's definitely not a matter of perceived threat, either.

Threats are variable, you have no control over threats. It's smart to avoid threats wherever possible, but you can not predict them with any ongoing accuracy.

And I'd disagree with or refine rather your summary statement as well: Linux has been largely documented as the #1 target for interactive-attack-oriented-incidents, meanwhile Windows is clearly the #1 target for mass-malware incidents. And depending on the study, these statistics usually exceed relative populations; which makes them both rather significant.

Security is not an inverse of threat; it's a matter of impact reduction. You aren't afraid to have a wreck because of the wreck - you fear the wreck because the possibility to cause death, personal injury, or any relevant cost scenarios that could result from it (loss of license, loss of transportation, insurance rate increases, lifelong guilt from killing a family of four, etc). "Security" largely has more to do with the means to reduce those costs, given a wreck, than it does to prevent the wreck itself. The same is true in computing.
0 Votes
+ -
Most cogent argument so far
mmarth 23rd Mar 2005
Wow. This person actually brought the discussion into a moment of reality.

Let's see if George is deep or just a spectator.
0 Votes
+ -
Wow
IT Scion 24th Mar 2005
Who can argue with that?
0 Votes
+ -
MS might have a stranglehold on the desktop, but Apache has an undisputed presence on the server. I though that > 50% of webservers ran Apache, but this link suggests it's currently nearer 70%:

http://news.netcraft.com/archives/web_server_survey.html

Hence there is a *considerable* incentive to *find* a security vulnerability in Apache. So on what basis do you say that people are only trying to exploit Microsoft's software? Why restrict yourself to only 25% of all webservers? You make no sense. Are you saying that crackers *expect* to find more weaknesses in IIS than in Apache?
0 Votes
+ -
The day is going to come...
Qbt 23rd Mar 2005
The day is going to come when MS software is going to be more secure than other vendor's software. Of course most people will laugh at this but given the effort they are putting in, and seeing results like these (even if some people still can't accept it) it's just a matter of time.

Let me give this example: When MS released Windows 95, they said they wanted to make Windows "the ultimate" gaming platform. I was laughing about this statement because at the time the only way you could get high-demanding games to run fast was to go into DOS mode. I could not understand how Windows could ever provide a faster, better environment for games.

Yet, here we are, with Windows by far the most popular platform for games. Look at benchmarks between Linux/Windows and Mac/Windows and see how Windows beats those in performance.

http://www.barefeats.com/mac2pc.html

http://www.linuxhardware.org/article.pl?sid=04/10/12/1725246

My point? Don't underestimate MS. People who do usually end up losing out.

Just accept that it could happen, as we start seeing these results as an indication of what's to come.

Peter
0 Votes
+ -
Are they going to change the underlying OS?

That's the only way I see it..
0 Votes
+ -
Yes, it could happen
alterego_z 23rd Mar 2005
but not unless Microsoft bites the bullet and builds an entirely new operating system from scratch. Or takes the Apple OSX approach and builds their GUI on top of exiting UNIX kernel.

As long as MS continues to patch their ancient desktop operating system and call it a server they and are doomed to spend their life on the bottom rung of secure technology.
0 Votes
+ -
It Could Happen?
Jkirk3279 23rd Mar 2005
"Or takes the Apple OSX approach and builds their GUI on top of
exiting UNIX kernel."

Except that M$ had the chance to do this with NT and blew it.

I actually had high hopes for NT back in the day. I recall
reading about NT, and thinking that it could be a fresh start for
M$.

Nope. Guess not.

There are M$ lovers that think Redmond can do no wrong.

But let's be rational. With the money M$ has, they SHOULD have
the greatest operating system in the world !

Their stuff should be bulletproof.

Even IF they had to start fresh like Apple did, their OS should be
perfect by now. Virus Proof. No hacks possible.

Yet, it's not. And I can't figure out why.

Maybe money can't buy class.
0 Votes
+ -
No such thing
IT Scion 24th Mar 2005
A bullet proof OS is a dream. MAybe many years from now it will change but no one is putting out anything close to bullet proof(Especially for Web servers or desktops). I'm sure in theory it is possible but the OS would be the most limited and inconvenient system on the market and no one would buy it. Not able to figure why there is no perfect OS? Here's just a couple of reasons but there are plenty. A hole in an OS may not be a hole until technology takes a next step. Humans design the OS. For every user friendly feature there is more surface to attack. You say "let's be rational" and think anyone debating your post will automatically be an MS lover but you weren't rational and I'm not an MS lover.
0 Votes
+ -
Erroneous numbers
mmarth 23rd Mar 2005
The measures of this study would be laughable if it weren't for the techno wannabes buying in...

I have a better reason that Windows is more secure: the box is heavier; therefore it would require hackers that were physically stronger to pick it up, open it, install it and then hack it.

Or maybe Windows is more secure because it has more characters in its name than Linux. Passwords with more characters are more secure, right?
0 Votes
+ -
What about compromised numbers?
rpmyers1 23rd Mar 2005
Forget the patches, and reported vulnerabilities, what about the absolute number of compromises of each, and that relative to market share numbers.

These seem to be more relevant numbers.
0 Votes
+ -
Your best bet there is...
droby10 23rd Mar 2005
...going to be mi2g's monthly report. Despite a level of discrediting by certain individuals/groups, it's about the only thing publicly available with numbers on actual live compromises. Save your money - it pretty much says the same thing, just using a different metering stick.

Linux comes out in the worst spot with about 3-4 times the number of Windows incidents, after relative population adjustment.
0 Votes
+ -
mi2g just makes stuff up -nt-
emcee_z 23rd Mar 2005
nt
0 Votes
+ -
Reading 101
droby10 23rd Mar 2005
...was duly noted that credibility has been in question. However a statement such as yours might be interpretted as libel without cause; especially given the increasing number of reports and independent studies which pretty much all corroborate the numbers portion at face value.

I'm not saying anything other than here's the report; of which the numbers are verifyiable. The interpretation and analysis may not be aligned with what you'd want to see, however. If not, then quit complaining about such things and do your own research. Because outside of this particular instance, such levels of reporting are generally held confidential. Due to the very nature of evaluating incidents rather than risks and exposures which are significantly easier to quantify, although have less real-world relevance.
0 Votes
+ -
Not about what I want to see
emcee_z 23rd Mar 2005
I don't care what the report says. What matters is the fact that the company that created the reports has been shown to consistantly create reports with no sources or reasoning to back them up, and have been repeatedly found to be false. These reports have covered everything from certain disaster from Y2K, to cyber-terrorism related to 9/11, to some kind of cyber-war between the US and China. They have even gone so far as to refer to sites that discredit them and hate sites and compare them to neo-nazis. Knowing this why would anyone ever consider their reports anything more than random numbers?
0 Votes
+ -
Then feel fortunate in the fact...
droby10 23rd Mar 2005
...that you weren't the one asking for virtually non-existant statistics; given your described aversion to read or comprehend anything objectively.
0 Votes
+ -
The superficial analysis works for you
Richard Flude 23rd Mar 2005
"Therefore, the only thing that is exposed beyond the
Ethernet adapter of the server is IIS 6.0 or Apache 2.x, and
these are the main things we need to worry about when
evaluating Web servers."

I agree with this approach over the "all packages installed"
approach of the report. However, this is not just IIS and
Apache it must be everything accessible through these
ports (eg scripting engines, ssl implementations, webdav,
etc) and be restricted to configuration (either default or
typical).

You don't do this in your superficial analysis. Indeed many
of the vulnerabilities you attribute to Apache are not going
to affect common deployments (eg check_forensic Script,
Apache Directory Traversal Vulnerability on cygwin,
SSLCipherSuite, etc). The two you claim are unpatched
require ubuntu and mod_disk_cache respectively.

"Based on this information, it is easy to conclude that IIS
6.0 has a much better track record than Apache 2.0.x and
that Apache needed to be patched more frequently."

Of course it would, but you'd be making yourself to look
like a fool.

First, why don't you add those vulnerabilities not listed
under IIS but will impact a deployed windows web server
through exposed ports.

eg SA11064 - 14 vulnerabilities

3) boundary error within the Microsoft Secure Sockets Layer
(SSL) library when processing PCT (Private Communications
Transport) handshake packets can be exploited to cause a
buffer overflow.

We could also add time to fix, criticality of error, attack
vector by why waste our time. The superficial analysis
approach works for you.
0 Votes
+ -
You're misinterpreting the results
george_ou 23rd Mar 2005
Richard, I looked this up at Secunia and it appears that you are misinterpreting the results. The advisory doesn?t say anything about the operation of a web server, and mostly pertains to client applications. Does that go through port 80? Sure it does but it doesn?t pertain to a web server. Of course, I happen to automatically patch all security vulnerabilities, but it?s not what you make it out to be.

http://secunia.com/advisories/11064/

Here is an excerpt:
************************************************
The vulnerability may affect the following applications and services:
* Telephony Application Programming Interface (TAPI)-based applications
* NetMeeting
* Internet Connection Firewall (ICF)
* Internet Connection Sharing
* Microsoft Routing and Remote Access service

NetMeeting is installed as part of Windows 2000, Windows XP, and Windows Server 2003. The vulnerability doesn't affect Windows NT 4.0 unless the standalone version of NetMeeting has been installed.
************************************************
0 Votes
+ -
I think what he's saying...
droby10 23rd Mar 2005
...is that SSL, being a common (and often times critical) component to web services - should be included in the what is evaluated; even if it categorically falls under different vulnerability identification. Item 13 of 14 is/was clearly a service-oriented issue effecting IIS; and I tend to agree that it should be included to provide parallelism. The actual CERT/CAN ids are VU#150236 and CAN-2004-0120, respectfully.
0 Votes
+ -
Show me where it affects a web server
george_ou 24th Mar 2005
Please quote what parts of those alerts say that an IIS 6.0 web server is affected. Show me a scenario where this might happen.
0 Votes
+ -
Here you go
Richard Flude 24th Mar 2005
"Please quote what parts of those alerts say that an IIS 6.0
web server is affected."

Under IIS on Secunia it doesn't, which highlights how
dangerous superficial analysis of the problems are.

The issue I raised is covered here

http://www.kb.cert.org/vuls/id/586540

The issue droby10 raised is covered here

http://www.kb.cert.org/vuls/id/150236

Both alerts show that the MS SSL implementation is
vulnerable to attack. Clearly both should be counted in your
number of vulnerabilities for IIS where SSL is enabled and
accessible and both are much more critical than many of
the obscure Apache vulnerabilities you counted.
0 Votes
+ -
You're partially right
george_ou 24th Mar 2005
I checked your link out and you're partially right.

Here is the quote.

****************************************
Windows Server 2003 is only vulnerable to this issue if an administrator has manually enabled PCT (even if SSL has been enabled).
*****************************************

With all the Win2003 IIS 6.0 servers out there, how many people do you think would manually enable PCT let alone know what it is? I've never done this on any of my servers.

You're partially right because this could affect IIS 6.0. But then again, I didn't include other potentially vulnerable libraries for Linux/Apache. The comparison is still a fair one.
0 Votes
+ -
Why?
Richard Flude 24th Mar 2005
"You're partially right because this could affect IIS 6.0. But
then again, I didn't include other potentially vulnerable
libraries for Linux/Apache. The comparison is still a fair
one."

You didn't?

You think it is fair to compare a count of Apache advisories
that include Apache on cygwin, mod_ssl, scripts included
by one distribution, obscure unused modules, and then
don't count core OS vulnerabilities which could be exposed
on an IIS webserver?

Says a lot about your definition of fair.
0 Votes
+ -
Unless you have your head in the sand, it is obvious that Microsoft is now taking security very seriously and is devoting huge resources and money to making all of its systems secure.

Unless you are fool, you'll realize that when Microsoft devotes a huge amount of money to a technical problem they eventually succeed. There are more and more security tools/features built into Windows every year and Linux is remaining constant with more or less the same security story it had 5 years ago.

Just like Netscape eventually lost the browser war, Linux will eventually lose the security war against Microsoft.

I still don't understand why people use Linux instead of OpenBSD. OpenBSD is vastly superior to Linux (and Microsoft) from a security perspective and gives you essentially all the benefits of Linux. Go OpenBSD!
0 Votes
+ -
Right...
Sabz5150 26th Mar 2005
That's why XP is still vulnerable to an 8 year old exploit.

I have yet to see a new security feature outside this "Windows Firewall" thing that does more harm than good on a network.

My Linux boxen haven't been bothered by crackers once. Didn't lose one bit of usability securing them either.

Microsoft's devotion to security is still more lip service. Linux however... well, look at the source code. I can see with my own eyes what has been changed and why. Gotta have some devotion to let it all hang out like that in front of the general public.

I hear about changes and devotion in the Microsoft camp. The Linux camp proudly shows me their changes and devotion.
0 Votes
+ -
usual apples and oranges ...
mdfischer 25th Mar 2005
Only the headline has much to say about Linux or Windows. The
comparison was with specific products, Apache 2 vs Microsoft's
IIs server, MySQL vs SQL server and php vs ASP.net in default
configurations, not the configurations mentioned in this re-story
which are servers with only ports 80 and 443 enabled. The
additional problems with Windows web servers is that they are
often not locked down as indicated, and they are connected to
machines on the local network that can easily exploit their way
in.

Not knowing much about IIs I am not willing to say which is
better between IIs and Apache. As a long time observer of
Apache logs, having used it over ten years, I note daily several
thousand attempted exploits for IIs and Apache for windows
(based on the paths used in these attempted exploits). I see a
few hundred attempts for Apache under linux and generic unix,
and a few dozens attempts for Apache under Solaris (which is
what is actually running).

So even if we took the figures of vulnerability seriously, which
would in crude terms give linux a 3:1 disadvantage, I get about
15x as many attempts for windows as linux if all windows
servers ran IIs (which is not the case), which would under the
methodology used in the study make windows very crudely 5x
more at risk if all flaws were not patched since they are
disproportional targets.

In the to be fair department:

Apache 2 has had problems, and a lot of sites still use Apache 1
because of this, although there is a sense that Apache 2 is about
there. Many of these past issues were not issues, however, if
only ports 80 and 443 are enabled. Many of the more serious
problems were only serious with respect to windows because of
its light approach to permissions and priviledges.

Not all linux services use Apache.

Many windows hosts do not use IIs

If you do break into a Windows host you can do a lot more
damage and compromise than an Apache break-in.
0 Votes
+ -
Ken Brown: Validated
Junior_z 31st Mar 2005
As a run of the mill observer of the ongoing issue of cyber-security and more specifically open-source code security, it is interesting to notice how an initially bashed commentary and investigation from Alexis deTocqueville Institute President Ken Brown (Opening the Open-Source Debate, 2002, http://adti.net/ip/opensource_debate.html ) has more recently become dittoed all across the computer-world spectrum. Seems to me that Brown was well ahead of his time as more and more inhabitants of ?planet geek? are now talking the same Brown-language; or shall I say, Brown-code.
(As a former employee of AdTI and around the offices when Brown authored the white paper on open-source, I witnessed first hand the initial backlash from many in the open-source community about his report. I have moved on since (Dec. 2002), but have kept in touch with the issues surrounding open-source software, in particular the issues of security and felt the need to give credit where credit is due.)

It is understandable why so many in the computer community, mainly ?open-sorcerers?, frowned upon Brown?s investigative and some would say common sense concerns. The general conclusion from Brown was that open-source code, especially with its use in highly sensitive areas such as defense and intelligence, leaves higher the open possibility of hackers obtaining, writing or deciphering sensitive code. As Symantec?s Asian Pacific Vice President, Vincent Steckler said in a March 17, 2004 speech (a full 2 years after Brown?s analysis), ?? imagine smart hackers with [access to] source code.?

In his 2002 white paper Brown noted the usefulness of open-source code in academia and in software development. Open-source advocates hardly found this flattering enough as some went so far as to place Brown into a full fledged conspiracy theory by saying, ?There is speculation in the open source community that the report is a Microsoft-backed attempt to scare governments away from the increasing interest in open source software.? So, instead of addressing the issues of the paper, many automatically looked at ?why? the paper was written as opposed to ?what? was actually in the paper; a common argument fallacy that does not address Brown?s accurate and important evaluation of open-source security concerns.

Simply put, at least from this everyday observer, Brown?s points addressing the specific security concerns were never fully addressed by ?open-sorcerers? at the initial release of the AdTI study; although some tried. One specific point raised was that with open-source, many users with their ?many eyes? would be able to catch and therefore patch security holes, while Microsoft users with no knowledge of the code itself, are not able to accomplish the same. While this may be a true depiction of the ?many eyes?, it fails to recognize a significant issue Brown raised in his 2002 study in that although there are many eyes checking out the source code in open source, there can be no guarantee all the eyes are helpful eyes. There has been growing speculation hackers have obtained source code, plugged in fallacious and/or malicious code, and have redistributed that malicious code to other open source users.

Probably the most notable quote I can give you in relation to this that I read is from a December 2003 C/Net article where Linux?s own Corey Shields admitted, ?The worry is that if someone wanted to be malicious, they could change core software and users could be using corrupted packages." Now this is what I was waiting for; a Linux guy supporting Brown?s thesis. This is highly encouraging that the community has recognized the issues and is combating them with great eagerness.

In addition, a recent March 17, 2005 article on silicon.com entitled ?Linux, not secure enough for enterprises? (Munir Kotadia) pronounced the IT heavyweight filled Agility Alliance ?does not consider Linux to be a suitable operating system for the largest of enterprise customers because the open source operating system has issues with security, scalability and the possibility of forking.? They specifically point to the unending question of who is providing the source code. As Brown rightly stated, nobody can be sure.

Again, this Brown commentary has been echoed throughout the industry. In one instance, Executive Director for the Center for Education and Research in Information Assurance and Security, Charles J. Murray said emphatically in an article discussing national security concerns with open source technology, ?But [open source] certainly has one problem, and that is that there are many elements of unknown provenance in it.?
Again, is there an echo in here?

There are many examples of recent speeches given and/or articles written where Brown?s assessment of security concerns with open source software is reverberated; when once it was dismissed as a political hack job. I believe that because certain United States agencies have seriously been using open source software for their own applications, the discovery of the security risks have become more apparent. For one, the National Security Administration (NSA) already uses a security-enhanced version of Linux. Additionally, a March 11, 2005 Washington Post article explained how much damage could be done by hackers that are able to reach the control centers of America?s power grid; and that the attempts are hundreds daily. Brown, realizing this trend, wanted to shed some light on some of the issues for the benefit of national security in our post 9/11 world, and I applaud his efforts.

Beyond the security threats foreseen with open source are the questions of intellectual property (IP). AdTI?s President Brown also shed a much needed light on this issue in terms of economics and business. Like it or not, Microsoft? Corp. is an economic engine in not only the American, but the world economy. Attached to this engine and the fuel necessary for its operation lies in the realm of IP and the safeguarding of its sources and ends. One of Brown?s main points was that major companies cannot be sure their employees do not contribute to the free open source network, therefore may lose IP critical to economic growth. This point is resonated by many in the investor-related community and is essential to understand for all of us interested in this critical market. After all, even Linux is looking for market share aren?t they?

With much excitement, I find it beneficial to all of us and I encourage everyone to think critically and openly about what Brown has and is saying about open-source security and proprietary rights concerns. The intense discussion, as I see it, is for the benefit of national, (and for you ?open-sorcerers? out there), intellectual security. It took one micro-second for Brown to be dismissed, ridiculed and ostracized; but as I have recognized through my research today, it has taken three years for his deserved vindication. Kudos.

---Keith Sheets, Jr.
Keith was employed by AdTI during the release of Brown?s white paper. Keith left AdTI in December of 2002.
0 Votes
+ -
Who reports exploits?
Jick 3rd Nov 2005
It is well known that epidemiological statistics on diseases are skewed by changing attitudes toward various "afflictions" -- many non-life-threatening ailments appear to be on the rise because they are now reported where there were not before. Could the statistics on Web server security be subject to the same effect? Who reports exploits? Not the hackers who have found a way to wreak vengeance on their sworn enemy, that's for sure. Suppose you were a dedicated "Open Sourcerer", a founding member of the Linux Jihad, and you found a security hole in a Micro$oft product; would you tell Micro$oft? Would you tell anyone, except perhaps the hacker community? Doubtful. But if you found an exploit in Apache, the chances are much better that you would immediately let the developers know so they could fix it. I think you have to factor in the skewed reporting that results from widespread hatred for Micro$oft. (If you doubt that it exists, please estimate the ratio of viruses written for Windows vs. Linux.)

Join the conversation!

Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]
ie8 fix
Click Here
ie8 fix

The best of ZDNet, delivered

ZDNet Newsletters

Get the best of ZDNet delivered straight to your inbox

Facebook Activity

White Papers, Webcasts, & Resources
ie8 fix
ie8 fix