Discussion Locked

Opt for Apache 2.0 over IIS?

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Tell us what you think about choosing Apache 2.0 over IIS, as featured in the latest issue of the Internet Security Focus e-newsletter. How much do the recent security issues with IIS affect your decision? What security concerns do you have about both products?

14 replies

by victor.vatamanescu

Hello,

With all the respect for this article's author, I would like to answer him a few very simple questions.

Will I be able to develop .NET Services working with Apache? I sure could develop these stuff using Java but I would charge my customers a lot more, and tell me who's losing.
And, by the way, I'm sick and tired of this marketing crap around Linux and stuff like this. Customers should understand that opting for a so called "open-source, free" OS actually means that the overall cost of applications development greatly increases, because Linux is a great OS only when it does nothing.
About Apache - do you think that in the 2002 year will I use a text editor and write like in the first days of computing php or perl code just because I dont want to use a Visual Interdev or a Visual Studio .NET. My idiocy would cost my customer time and money and I would be fast out of the market.
The FrontPage you are talking about is not taken seriously not even by Microsoft and if this is the only thing you can say about IIS maybe you should quit IT.
You haven't told us nothing about the WSDL, XPath Queries, the tight integration between COM+ and IIS, Windows DNA and a million other things.
I sugest you that if you write other things like this, document some more your writing and please come up with concrete data and not with commercial crap.

by bill gonch

Dear Vatamanescu:

This article does not seem to call for an anti-Microsoft tirade. It certainly does not seem to call for a personal attack of the author. A couple of years ago, I was a Sun, 'open' systems fan, because they seemed to be the best tools for the job I was doing at that point in time. Today, I am also (without having rejected the other side) a Microsoft fan. Different job, different tools. The reality is you can build a good application--in general--with either toolset. Yes, there is a lot of complexity in either domain. And yes, our jobs would be easier if the market place had less hype and a little more substance.

As to the author's question -- which is faster -- I wish I could figure it out. In the context ofa real a substantive application, differences of servers and the quality of the underlying application code line, have caused me to run away from this question that keeps on appearing. The only thing I am pretty sure of is that given enough server investment, you can get a 'good enough' application with either set of tools.

Perhaps, Vatamanescu should take some his own advice, turn down the volume and see whether anyone has a good answer.

by fulsomepraise

I have used IIS since version 2.0 and it just gets better. There have been security issues but these have been more to do with MS's habit of getting it to install wide open and with the way in which IIS has been targetted by anti MS hackers.
I keep my servers patched up and locked down and I've never had a problem. If you get the basics right then IIS offers a much easier and more productive web server solution. It is essential for intranets in a Windows based organisation because of its tight integration with other MS server products. As an internet server it offers a highly productive and fast solution for complex web apps. And of course now it offers .NET.
Of course as Vatamanescu says - I could spend a heap of time messing around with Java, Linux, PHP, mySQL and Apache - I wouldn't be tainted by the MS devil - but my clients want their web apps now and they want them to be easily supportable.

by goboslayer

I believe what it all comes down to is what the author states: fill the needs of the client. Anyone who is proficient in either platform can administer a secure solution for the client. I have worked with IIS 5.0 and ASP for some time now, and I really haven't had any significant problems whatsoever. The department that I am in has also been very proactive at staying on top of possible security breeches, which for the most part MS is very good at notifying admins of. Our IIS is Locked Down (v2.1) and HotFixes applied as well. The portion of the article I didn't quite understand is the statment that Apaches code is "constantly under refinement". Yet the patches to "refine" IIS seem to be question to scrutiny. I guess I am just failing to see how the 2 significantly differ. All in all, good article. These forums are fun.

by lthompson

As a UNIX administrator yourself (I am not) I would assume you feel more comfortable with Apache. I do not. I work in a Microsoft based technology area, our web server (IIS) keeps right on going while the Linux based facility server gets hacked withgreat regularity. Whether they are hacking the Linux kernal or Apache, they don't tell me, but the web site is down anyway. The feature set and the ability to use ASP (now ASPX) have sold me on IIS, I do my patches (part of the job) and don't claim to be unhackable. Since I use and teach .NET, I admit to a bias toware IIS. I just don't find it any less (or more) secure than other web servers. I pay for the ease of use and feature set, and yes I like FrontPage.

Larry Thompson

by caspian

As someone who has worked with both IIS and Apache and is more comfortable in a Windows environment than Linux (although I'm not a newbie to either), I appreciated the fairness that went into the article.

There is much to be said about the new .NET IDE and how quickly a webapp can be put in place, but no amount of functionality should take precendence over the security requirements (which the author acknowledges may vary).

A computing professional who applies ethics to his/her work will take care to provide a secure and robust solution or at least counsel the customer on the consequences of a less secure system. The old adage of "Good, Fast, Cheap... pick two." still applies. If the customer insists on a Fast/Cheap solution after being counseled on the consequences, so be it. But a computing professional who provides such solutions on a regular basis soon gains a reputation for shoddy solutions. Case in point: look at the damage control Bill Gates is applying to curb public perception of Windows' security.

by b_fearron

excellent article by the way...

you are correct about apache...if microsoft is to remain competative it needs some competition and i believe apache fills the void...it's secure and that's what information technologist need..

by richard.j.tisinai

One other concern is the use of "Microsoft
only" web building tools (IIS with FrontPage)
which probably will (if not already) limit the
functionality of web browsing to "Internet
Explorer only." Also, consider being limited to
MS java applets (only) versus others Java
environments. Microsoft touts its "ease of use"
but at a price of its insistence on MS
"onliness."

by hfigueroa

One thing you did not consider in your article is the amount of time it takes to develop or maintain aplications. Together with UML and UDP, VB.NET is paradise in this field. Today's CEO's, CMO's, COO's and CIO's expect you to be very quick and eficient when it comes to small o great changes in your projects or running SW. That's where MS has done its homework better than anyone else.

I agree that keeping track of patches (together with Backups and Versions) is a pain, but that is also supposed to get better with .NET and Windows XP (I really hope it happens).

You know, in Spanish, the phonetics for "Java" equal to the frase "Wait. It's comming." I think Development Speed and Control are important factors when choosing an applicationserver.

Hector R. Figueroa
Datawarehousing & Transactional Web Applications
Project Manager

by mross

I would like to submit a different point-of-view. Even though Apache is a more mature product than IIS it still has its security holes. If other web servers were as much as a target as IIS, I believe you would find that they are not much more secure.

Since Microsoft is a target for very so called cracker/hacker out there, the vulnerabilities are more likely to be exposed.

It is impossible to state that IIS is less secure than Apache or any other web server, when one product is tested(targeted) more than another. Only the fact remains that IIS is cracked more often, by the shear fact that many more people try to hack into it.

Get as may hackers to try to expose security problems in Apache I think you will find it is not as secure as you think it is. IIS is targeted not because of its ease to break into but because of people finding fault in Microsoft and trying to do what they can do to get their misconceived point across.

Patches and Service Packs only prove that Microsoft is moving on exposed holes quickly and effectively.

One issue that Microsoft has addressed that I believe to be their biggest down fall, is that the default install of IIS is wide open and the default install of other web servers is pretty much locked down. I had more to say here but ran out of space.

For those of you, who think you are doing a great favor to us by targeting IIS and Microsoft, think again. Think where we would be without Microsoft. Microsoft took an approach ofhaving millions of people pay for a very expensive product, which reduced the overall cost (basic supply and demand), instead of having just few pay huge amounts for the same product.

Congrats, to Bill Gates for being the Henry Ford of our era.

by spikeymike

Mross,

Apaches is OPEN SOURCE. That means that hackers can pour over the source code to try and find an unchecked buffer or other means of entry. With IIS, it is hit and miss. Believe me, if there are holes so big you can drive a truck throughin Apache, there would be an exploit for it. With IIS, the hacker community is still looking (and finding) those holes.

No offense, but you sound like a pointy-haired manager!

-Mike

by bill harrison

The Toyata Camry has been the most stolen vehicle in the US for the past 5 years! Why isn't Toyota trying to improve security? More importantly why would anybody in their right mind buy a vehicle that is such a security risk? I found the "Netcraft" data very interesting, again it is all a matter of timing and interpretation. The opening line of the article could have read "According to Netcraft's March 2002 Web Server Survey, Apache shows highest rate of decline among webservers" Take a moment to look at the Market share chart and notice that in Aug1995 the server market was dominated by others that have since dropped into obscurity. You'll also notice that MS increases are steadily greater than Apache's decreases. The point is that there is much more involved than "who has the best deadbolt". People continue to buy the Camry because they like the handling, mileage and features. I find it interesting that Yarden paints IIS's "numerous patches" as a bad thing then in the next paragraphindicates that Apache's code "constantly under refinement" is a good thing. They sound very much like the same thing to me. IIS security will improve but Microsoft, like the Camry, will always be a popular target.

by dailyfeed

To label IIS as more insecure than other Web servers, when other products are susceptible to the same problems, is truly a disservice.
IIS stands in the spotlight because people have chosen to write viruses that specifically target IIS. Microsoft is worthy of criticism in many instances, but this (I think) is not one of them. Please do not cloud the issue by claiming that all of our virus and security woes would be solved by replacing one Web server with another.

by donkoque

Pienso que aqui hay mucho en juego, sin embargo la seguridad es algo primordial.
Apache sigue siendo en muchos aspectos, mejor que IIS.

This discussion is closed to new replies.