Slashdot Mirror
Apache 2.0.44 Released
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.
I've been noticing that Apache doesn't make news anymore--at least on Slashdot, but to be fair I think it's because Apache is so stable (in the 1.3.x series, especially) people don't even think about it anymore. Good job, Apache Foundation!
-- @rjamestaylor on Ello
The biggest security problem with running apache on Windows is Windows. Anyone who uses windows for a server deserves what happens to their server.
Jason
ProfQuotes
They both have to do with running the server on 9x or ME.
Is Apache's security really the problem here?
I have been pwned because my
- Use the mirrors!
- 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.
"Rich notes that it fixes some important security problems (under Windows) for the Windows version"
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.
Better than a poke in the eye? Two in the bush? Using a bloke manually replying to all server requests?
I don't deal much with Apache. But, I decided to take a look at the download page to get a feel for its usability. What struck me the most was that there seem to be two important versions:
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. It ain't perfect, but at least you don't have to work about file integrity...
How to Download YouTube Videos
Charts showing the differences between apache 1.x and 2.x.
Actually a great article as a whole
new features
--
the strongest word is still the word "free"
Heck, we'd use it....
If mod_perl 2.0 was released....
-- Spankmeister General
Unfortunately, they still haven't been able to solve the issues with SSL under windows, so the windows release comes without SSL. The effect of this can range from none (lots of sites don't use SSL) to the typical IT-Manager complaint "but we NEED SSL". Unfortunately, what they don't realise is that staying with IIS is not the solution.
...
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!
This sig intentionally left bla... dammit!
Who's got the whiteout?
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.
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.
- jon
Ganymede, a GPL'ed metadirectory for UNIX
I've used apache 2.0, and it's great and all, but I ain't switching over until the PHP folks say that the PHP-apache-2 module is good to go.
"Quoting famous computer scientists out of context is the root of all evil (or at least most of it) in programming." - K
For me it is merely a case of "if it ain't broke, don't fix it". I just haven't found a good reason to switch yet. Bug fixes and security patches keep on coming out for 1.3.x, and performance hasn't been an issue for me yet. (not that 2.x is supposed to fix everyone's performance woes)
2.x
- 1.x
-----
1.0
Duh.
It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
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.
There is no such thing as luck. Luck is nothing but an absence of bad luck.
from the post: it fixes some important security problems (under Windows) for the Windows version.
I wonder... does this mean there are some security problems left in the Windows Version under OSes other than Windows?
my
Because...
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
-
ping -f 255.255.255.255 # if only
I think you're getting feature-rich and better confused. Normally newer releases have more in them, but this does not always equal better. For something to be better, stability, ease of use, speed, and so on are also factors. If version numbers told you which release was better, then they would likely change and be much more confusing in general.
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.
I have a mini-howto on Apache 2.x and PHP 4 at http://dan.drydog.com/apache2php.html As for the new 2.0.x stable series--that's great news. What it means is "no more recompiling modules between minor releases."
Um... you've been gravely misinformed. Microsoft DOESN'T work fine. Really. As a netadmin/webmaster myself, I shouldn't have to worry about BSODs, frozen boxes, vulnerabilities and the like. With M$, I would have to worry about that all the time, rather than when a security patch is out (you know, the ones that don't replace your config when you implement them?). The truth of the matter is, I NEED APACHE.
Support Israeli punk bands. Man Alive.
There are no issues with SSL and Apache for windows. Apache(binary) for win32 does not come compiled with SSL due to some confusion with strong crypto laws. You can compile Apache with SSL integrated by downloading the source and using VC++. And IIRC, there is already a binary in the contrib dir on openssl.org.
as a professional bank robber, i refuse to let laws dictate how _I_ feed my family.
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!)!
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. 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!
-Joe
If we're all god's children, what's so special about Jesus? - Jimmy Carr
...You'll need this patch. A bit of a glitch, now solved.
You're a pretty crappy admin then.
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
Work Safe Porn
I'm developing a website right now using the httpd, php, and postgresql packages from RH 8. No problems yet.
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.
Be careful with upgrading to 2.0.44 for some people report big problems with the new version. See this and this thread on google groups for reference.
Cheers!
I think it is time for the Foundation to maybe ramp up the development of the PHP module. 2.x has been out for quite awhile now, but there has not been any mass changing probably due to this fact. I have tried 2.x but couldn't get PHP to be stable enough for production so I had to go back to 1.x. Given the fact that PHP usage is still growing by leaps and bounds, you'd think Apache would want to really highlight the performance of 2.x by getting on the ball.
This is excellent news for Windows users who wish to run Apache 2 from their systems. For ages, it seems, Apache 2 had a security issue under Windows XP that would not allow it to run properly under the OS. Only users wh ohad registered with Microsfot online could download the special patches that fixed these problems.
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.