Apache 2.0.44 Released 198
rbowen writes "The Apache Software Foundation is pleased to announce the release of Apache 2.0.44, which addresses a number of security issues. Download it from your favorite mirror." Rich notes that it fixes some important security problems (under Windows) for the Windows version. Also interesting is that now there truly is a split between a development and regular releases, adopting the Linux kernel model, with 2.1 being the dev Apache tree and 2.0 being the release tree.
First /. Apache article since Dec 2 (Score:2, Insightful)
Re:First /. Apache article since Dec 2 (Score:3, Insightful)
That's because it hasn't had a minute version change!
Re:First /. Apache article since Dec 2 (Score:2, Funny)
But they love the popularity anyways...
Re:First /. Apache article since Dec 2 (Score:1, Insightful)
Re:First /. Apache article since Dec 2 (Score:2)
Security problems under windows (Score:2, Flamebait)
Jason
ProfQuotes [profquotes.com]
Re:Security problems under windows (Score:2, Interesting)
Offtopic: love your sig (Score:2, Funny)
Re:Security problems under windows (Score:5, Funny)
The IP is 207.46.248.109
Re:Security problems under windows (Score:5, Funny)
The IP is 207.46.248.109
I was going to mod this up as +1 Funny, but I was afraid that nobody would "get it." So, here's the reverse dns lookup so everybody understands.
Re:Security problems under windows (Score:2)
Re:Security problems under windows (Score:3, Funny)
Everybody who generalizes sucks.
Re:Security problems under windows (Score:1)
Re:Security problems under windows (Score:2)
Ha!
Now that I think about it, I don't know what I'd think if I ran across that. I can tell you, though, that I was gritting my teeth when I wrote that. I'm sick of people making stupid generalizations like that based on some MSPhobia. (damn I wish I could make that rhyme with HomoPhobia.)
Re:Security problems under windows (Score:4, Funny)
Your statement is so dumb and stupid, I don't know where to begin debunking it.
Almost every statement is a generalization.
"The sky is blue" - but not when it's cloudy or at night.
"This item costs x$" - but not if you add in taxes, transportation to get to the store.
"My table is flat" - but not if you take into account the small inperfections on the wodden surface and the tiny tilt it sure has.
"Windows is a security nightmare" - but not if you spend day and night securing the computer, maintaining virus-scanners and install and test all patches.
The ability to generalize is a basic ability of a thinking being.
P.S.: Seriously, why should anybody want to use Windows as a webserver? The only reason I can think of is when you are locked into MS-only technology like ASP which rules out Apache anyway. So why? Just because the computer came with Windows? Because Bill Gates tells you?
Re:Security problems under windows (Score:2)
You shouldn't have tried debunking it. You missed my point by nearly 100%. Go read the post I was responding to, then read mine again. Maybe it'll become clearer. Somebody else got it, so I know it's not too obscure.
" Seriously, why should anybody want to use Windows as a webserver? The only reason I can think of is when you are locked into MS-only technology like ASP which rules out Apache anyway. So why? Just because the computer came with Windows? Because Bill Gates tells you?"
I'd give you reasons, but that'd just invite argument. Instead I'd suggest that if you're asking a question like that, it's because you've been reading Slashdot too long, as opposed to speaking from experience.
I speak from experience, and I can tell you IIS is not the nightmare people make it out to be. If it were I wouldn't have time to tinker around on Slashdot.
Re:Security problems under windows (Score:2)
Everybody that generalizes sucks. Heh.
"Why whine about Apache/Windows, then when IIS is so great anyway?"
I didn't whine about Apache. Never did. I have no idea why you think I was. I was only commenting on the fruitless generalization that earned karma.
"And why was IIS so great again?"
Again? When did I say it was great the first time?
Heh. Part of me wonders if I'm recieving messages you intended for somebody else.
Apache (Score:3, Interesting)
Is Apache's security really the problem here?
Re:Apache (Score:2)
I suppose running Apache on Win9x or ME is probably thought of as stupid, but I don't think anyone would be dumb enough to run on that platform as a production server. I think most of the people using Apache on 9x or ME are doing so instead of IIS or Personal Web Server... mainly for local testing in web development and programming.
I run Apache on Win98 for a couple of reasons:
1) My hacked version of PWS (IIS 3.something) scared the hell outta me.
2) *Someone* has to test Apache on Win98. Why?...
3) There are a lot of Win98 boxes in third-world countries. Those folks shouldn't have to pay to upgrade (if they only have MS skills) to XP or Win2K.
Win98 is pretty securable if you have a decent hardware firewall, and don't install a lot of crap on it. Stick with Moz for email, Cygwin for functionality and it's a pretty nice little machine.
Here comes the onslaught... (Score:4, Funny)
- Why do you guys post every single minor release?
- Damn, I just loaded 2.0.x! Stop updating the software so fast!
- I'm still using 1.9.x.
- I just downloaded it. Now what?
Ad nauseum.
Re:Here comes the onslaught... (Score:2)
Re:Here comes the onslaught... (Score:1)
"ad nauseam"
Under Windows? (Score:5, Funny)
I fixed that server security problem a long time ago...I just moved my Windows server from underneath the window to the rack beside the window.
Re:Under Windows? (Score:2)
A fully-patched IIS 5.0 box that ran a website I use got broken into last September. The next day the patch for the actual exploit that was used to get in was put out by Microsoft.
The issue is whether this sort of thing happens with any more regularity than on some Linux box running Apache. I don't have figures to hand.
I don't see why you'd want to have a machine with a GUI running as a server though. For me it's a power issue.
Outsider Perspective (Score:3, Insightful)
1. "Apache 2.0.44 is the best available version"
2. "Apache 1.3.27 is also available"
Now, don't get me wrong. I know enough to know that keeping around previous versions can be a Good Thing. However, as an outsider, this is confusing. Also, if you care to know, the entire section on verifying the integrity of the files was confusing.
Yes, I understand, I'm not the target audience. But, it still makes me frustrated to know that the Apache download site is mysterious. Just for giggles, take a look at the Windows NT Server download page [microsoft.com]. It ain't perfect, but at least you don't have to work about file integrity...
Compatibilty issues... (Score:4, Interesting)
This may be an issue of not being able to see the forest from the trees, and everyone that knows apache, knows what version they need for their server, so may not be the best bet for noobs.
But then again they may want all noobs to download the 2.x version, so the use of "best available" might be their marketing.
Re:Compatibilty issues... (Score:1)
Re:Outsider Perspective (Score:5, Informative)
Apache 2.0... has new features built into it, however, it is still relatively new. And some bugs are still lying around here and there. I reverted to 1.3 because of serious bugs in the PHP module (in version 2.0.1x,
Apache 1.3... is "old", but has built a solid userbase because of this age factor. It is also proven reliable and stable code.
Re:Outsider Perspective (Score:4, Informative)
Re:Outsider Perspective (Score:2)
Atleast, this is the case for me not to migrate our production environment since machines im managing are based on ssi based templates and i there is shitload of rewriting unless this wont get fixed.
Re:Outsider Perspective (Score:2)
Re:Outsider Perspective (Score:5, Informative)
I was quite excited with 2.0.43 but ended up back at 1.3.27 because PHP 4.2.3 (haven't tried 4.3.0 yet) made Apache unstable, specifically when calling an 'apachectl restart' which made my pager go off due to the server segfaulting at 4am during logrotate. In my testing, it was PHP that caused this instability.
Also, with 2.0.43 I couldn't get it to build with anything but the OpenSSL package, which on my box was 0.9.6b (hole!) but I couldn't get it for the life of me to look at an alternate install of 0.9.6h.
2.0.44 will perhaps fix these problems.
Re:Outsider Perspective (Score:1, Offtopic)
So where is the IIS download and how do I make sure it hasn't been messed with.
Re:Outsider Perspective (Score:1)
As the download-page [php.net] on php.net [php.net] announces: "PHP 4.3.0 zip package [php.net] [5,811Kb] - 27 December 2002 (CGI binary plus server API versions for Apache, Apache2 (experimental)"
Who's using Apache 2? (Score:2)
No one I know has found a compelling reason to switch from Apache 1.
Re:Who's using Apache 2? (Score:5, Insightful)
If mod_perl 2.0 was released....
Re:Who's using Apache 2? (Score:2)
It would be nice if tomcat didn't require a priest, a monk, and a shaman to install, too.
Re:Who's using Apache 2? (Score:1)
# rpm -q httpd mod_perl
httpd-2.0.40-11
mod_perl-1.99_05-3
One problem was that it didn't start with the current
directory set so my use's didn't work. Anyone had any luck with RH8.0?
Re:Who's using Apache 2? (Score:5, Informative)
We do on several of our servers. The main reason is that it's much, much easier to build an Apache server with SSL support on Apache 2 than it is on Apache 1.x, particularly if you're adding additional modules on top.
Re:Who's using Apache 2? (Score:2)
Ssl works fine on it too : )
Re:Who's using Apache 2? (Score:2)
Re:Who's using Apache 2? (Score:2)
They do more then just port scan the box, they use a nessus server against it. I still think its a waste of cash, but hell the client pays for it, so......
More than that... (Score:2)
First one to tell me to go to the Apache forum sites gets a swift kick...that's like going to the dump to look for an old magazine. Far too much material to wade thru...I've tried, so don't get smart
Re:Who's using Apache 2? (Score:2)
Hrmph. (Score:1, Redundant)
Re:Hrmph. (Score:2, Insightful)
Perhaps what you were thinking of is the fact that the last number in the version is generally a statement of which release is better. This is generally true, since the last number is the revision number and is usually only incremented for bug fixes.
Re:Hrmph. (Score:2)
I assume you're talking about the Linux numbering system where an odd/even minor version indicates developer/stable releases? Apache doesn't even use that system. The previous stable version is 1.3.x.
Re:Hrmph. (Score:2)
Oops. I'll have to admit that I didn't read the story since I already knew about the release and was only interested in other readers' comments. Sorry.
first apache news on Slashdot in over a month... (Score:1)
Long Overdue. Hopefully more news to come.
Apache 2.x and PHP (Score:1)
Anybody out there been using Apache 2.x and PHP enough to call it stable in their environment?
Other than huge threading improvements, are there any compelling reasons to switch from 1.3.x to 2.x right now?
Re:Apache 2.x and PHP (Score:1)
What I want to know is what exactly are the current showstoppers that are keeping everyone away from 2.x? Does everyone know something I don't?
Re:Apache 2.x and PHP (Score:2)
I would stick with version 1 unless there's something in apache2 that you absolutely need.
Re:Apache 2.x and PHP (Score:2, Insightful)
Re:Apache 2.x and PHP (Score:2)
Re:Apache 2.x and PHP (Score:1, Funny)
So I guess there are quite a few people using it.
You have a buddy that runs Apache2 so all the sudden quite a few people must be using it? What kind of clusterfart extrapolation is that?
Re:Apache 2.x and PHP (Score:2)
Apache 2.x and PHP and mini-howto (Score:5, Informative)
Still no SSL for Windows (Score:3, Insightful)
However, I do know of one company (whom my friend's father works for) that decided not to use Apache because they wanted 2.0.?? (because it was the latest release, so there was no way they would consider 1.x) but couldn't live without SSL. Of course they're using IIS on an unpatched WinNT4 box
What Apache needs to become the server of choice in companies like this is an education campaign. If you work at such a company, please tell the people in charge of this stuff about Apache, IIS and general security/stability issues under Windows. Mind you, Apache is still the #1 server around, so it is debatable whether this is a necessary step. But for the sake of secure, stable websites that don't leave your site open wider than a $2 hooker (ie, as wide open as the RIAA) please spread the word about Apache.
And Apache/SSL guys, I'm sure you're working on the issue, so best of luck solving it!
Re:Still no SSL for Windows (Score:1)
Re:Still no SSL for Windows (Score:1)
In fact, as reported in an ApacheCon 2000 paper [geoffthorpe.net], an Athlon 600 can outperform most of the SSL accelerator boards. And that is with 1/3 of the cost. So, I usually recommend my friends/colleagues to set up a seperate Apache box to do the SSL and then reverse-proxy requests to the real web server.
But SSL accelerator boards do have an advantage when considering key management.
There are other non-free good solutions (Score:5, Funny)
If you are willing to use a non-free solution like IIS, then a non-free product based upon Apache that provides SSL should be attractive to you. I am referring to IHS (IBM HTTP Server) which is a value added (to Apache) product from IBM.
MOD PARENT DOWN (Score:4, Informative)
Re:Still no SSL for Windows (Score:5, Informative)
http://marc.theaimsgroup.com/?l=apache-httpd-de
IANAAD (I am not an Apache developer), so don't kill me if I'm wrong, but that's what I read from the mailing list...
THERE IS SSL Apache 2.0.4x for Windows!!! (Score:5, Informative)
Actually, the issues they have under Windows are legal and nothing else. In fact, it works just great (if you don't believe me, compile Apache with SSL under Windows (you'll need Visual C++ 5 and up)... Apache Software Foundation even gives you detailed instructions on how to do it! [apache.org])!
Since Apache 2.0.x is the first version of Apache for Windows that is largely considered a Production release they are debating the legal issues of releasing a BINARY version of Apache 2.0.x for Win32 compiled with OpenSSL libraries. This is especially the case since they are not SELLING the software to do it, so they can not really control who would use it. They will figure something out, but in the meantime, do not release it in their binaries.
As a matter of fact, Apache 2.0.4x Win32 can easily be setup to use OpenSSL and ModSSL! This is thoroughly explained at this web site [raibledesigns.com]. It even explains to you where to get binary distributions of it (not directly from Apache as discussed above).
In fact, on a single Pentium II or III with Win2k (even workstation) you have plenty of horsepower to use SSL and Apache 2.0.x. I would like to mention a couple of things, I use it in an academic environment and it has been running stable and secure for almost half a year now.
It has a commercial SSL certificate on it. Apache 2.0.x on Win32 is quite a bit tricky to get your private key and public certificate to work if it is PEM encoded. If it is not PEM encoded, it is a snap! That right there is one thing that can save you hours of head banging on wall! Make sure your key and certificate after you've received them are not PEM encoded for less aggravation. You can always run them through (at least the cert) OpenSSL to remove the encoding.
Also, your certificate chain must be put together the right way, but you should get instructions for that from your certificate authority.
I agree, Apache on Win32 is a much better choice than IIS. IIS can be a relatively secure product if administered properly. There are, of course, numerous security holes that have been publicized, and it should be mentioned that most were left open by the administrators who should have known better. They got IIS to work and didn't bother with security! Most of the reasons to NOT use IIS are the fact that you need at least NT Server 4, 5, 6, etc. (the workstation version of IIS is too limited for production usage) and the steep licensing that costs, and the fact that it has much more features than 99.9% of websites will need!
Apache, on the other hand, gives you a relatively secure environment from the get-go that makes you ADD the features you need. After working with Apache it should become apparent that this is clearly the way to go. Intelligent administration of servers can really make almost any modern OS relatively secure. Perhaps if Apache on Win32 catches on it may encite people to port more great open source server software to natively run on Win32 as Apache does (does not use Cygwin... though you CAN of couse, use the Cygwin version of Apache which won't perform as well as the Native Win32 version does). Plus, Apache can run just fine on NT workstation (saving plenty of money on the NT server licenses)!
Interestingly enough, Apache Win32 in our setup outperforms other departments at our institution using IIS on Win32! Perhaps benchmarks in this area should be publicized a bit more!
Re:Still no SSL for Windows (Score:2, Interesting)
http://uptime.netcraft.com/up/graph?mode_u=off&mo
to be exact. =)
Interesting... (Score:2)
Re:Interesting... (Score:3, Interesting)
still unsure (Score:5, Insightful)
hmmm, this is great! (Score:5, Funny)
I wonder... does this mean there are some security problems left in the Windows Version under OSes other than Windows?
It seems a bit slugish on XP (Score:1)
If you plan on running 2.0.44 under Win9x/ME... (Score:5, Informative)
Security issues? (Score:2, Informative)
Reverse Proxy/load balancer, Http/Https, very small, tight code, minimises security risks. No matter what web server you're using, this should solve most of your security problems.
The apace development model (Score:1)
Perchild MPM (Score:1)
Be careful upgrading (Score:3, Informative)
Cheers!
Apache and PHP (Score:2, Informative)
Good news to Win users (Score:3, Interesting)
Now Apache 2 has worked around these issues while also improving security. Halleluia, I say. I can get rid of my old Linux server now and cannabalize the spare parts to augment my current XP server.
Aargh, not again! (Score:3, Funny)
Hopefully I'll be able to work around that Gentoo bug a bit quicker next time, now I know where it's lurking in wait to catch me out
Always Have a "Backup" Plan (Score:3, Interesting)
I have been playing with Apache 2.0 line for a while and it most assuredly does not have the stability of the 1.3 line. Each release does get a little better.
What I end up doing is keeping a 2.0 and 1.3 server compiled with modules and configuration necessary. If it turns out that the 2.0 has a devistating problem or fails to work then then 1.3 is ready to go. The code bases aren't that large and although the configurations do differ they are managable.
I recommend anyone who wants to try out Apache 2.0 but can't tolerate disruptions to maintain two configured servers.
Apache 2.x and ZoneAlarm (Score:2)
RMN
~~~
Re:What exactly are the differences... (Score:1)
Re:What exactly are the differences... (Score:3, Informative)
Production releases are more
- fully qa'd
- apache is more accountable if something goes wrong
- steady documentation
Dev versions are more
- unstable, they can have serious errors
- experimental, and have features that might be thrown away
- not fully documented, so using the greatest might be hard
- use at your own risk, it is a sandbox for development, not production quality
Re:What exactly are the differences... (Score:2)
Split releases give a stable API for modules (Score:2)
The example I know about is PHP. Everytime a Apache 2.0.x came out, PHP was broken (wouldn't compile) and I'd have to wait for a new PHP version that would handle the new or modified API. With this release I didn't even have to recompile and the existing PHP worked with Apache 2.0.x. Yeah!!!!!
Re:What exactly are the differences... (Score:1)
Re:What exactly are the differences... (Score:2)
Here are some major differences (Score:5, Informative)
Actually a great article as a whole [aceshardware.com]
Re:Here are some major differences (Score:2, Interesting)
Re:Here are some major differences (Score:1)
Can anybody out there in Slashdot land comment on or detail current performance and stability with this combo?
Re:Here are some major differences (Score:1)
Re:What exactly are the differences... (Score:5, Informative)
Your fancy math (Score:3, Funny)
2.x
- 1.x
-----
1.0
Duh.
Re:IIS and .Net are still better (Score:5, Funny)
Linux CVS? Bitkeeper (Score:1, Offtopic)
Re:Stuff (Score:3, Insightful)
Re:Stuff (Score:1, Funny)
MS works fine, you just don't know how to use it (Score:4, Insightful)
I run Apache 1.3.26 on Windows 2K and have been for the past 2 years. The only time a BSOD happened was when the HD cable came loose from all the heating and cooling. I had my server running 100% for 46 days and only rebooted because I was trying out some new SMTP (not MS) software which turned out to be complete and utter crap and a wasted reboot. It's now been going again for 15 days without a single issue. I've never had a Windows issue. On average I do a reboot once a month for software updates or whatever but never because I have to.
If your Windows machine has issues it's because your hardware is crap or you've loaded crappy software/drivers on it. I have 4 Win2K machines of various configurations that never have issues.
If you have security issues it's because you havn't clued into the fact that MS doesn't include much of a firewall. I have no security issues because I have an excellent hardware solution. There are plenty of excellent software solutions like ZoneAlarm.
If you're actually a netadmin/webmaster worth their salt I'm wondering why in the world you'd have security issues with any OS. Are you plugging the line directly into the computer? And if so, what do you expect? I wouldn't put Linux right on the wire either.
IIS has known exploits and if you're actually worth your salt you'd know how to prevent them from being used. If you NEED APACHE then you probably have no idea how to deal with and correct security issues. I like Apache because it's simple and effective.
On topic, I'll care about Apache 2.whatever when PHP is no longer broken. Apache 1.3.x is kinda the old reliable. Until 2.x can match it, there's no real burning need to upgrade.
Ben
fuzzy math (Score:1)
Re:fuzzy math (Score:2)
http://uptime.netcraft.com/up/graph?mode_u=off&
Or was that too difficult for you?
"YOU are not worth your salt, any way you take that lie."
Way to go. You sure got me. I never said I was on a shedule. Next time, recognize the fact there are many many ways to verify what people say instead of just butchering the English language.
and as an added bonus: site ranking
http://www.alexa.com/data/details/traffic_detai
Not too bad after only 2 years. My goal is to break 100,000 by the end of the year.
Script Kiddies can't pull those kinds of numbers.
Ben
Re:MS works fine, you just don't know how to use i (Score:2)
While that is quite an accomplishment, its nothing for a Unix server to have that kind of uptime.
However, you almost certainly ran a security risk by keeping IIS up that long. I have Win2K pro on my desktop, and with Windows Update pulling down security updates automatically, I certainly don't remember a period where 46 days went by with out a security flaw - that needed to be patched - that required a reboot.
If you're keeping your server patch you're really looking at a week's uptime between reboots, on average.
Its more stable than Win9x to be sure, but thats not saying much. Windwos still has a long way to go before it really makes a decent server.