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.
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"
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
All this is answered here...
.14? .15?, can't remember exactly).
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.
Welley Corporation - SLM Scammers
php 4.3.0 is running slick on my 2.0.43 apache install.
Jeremy
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.
Some people take their .sig way too seriously
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 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."
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.
I'd wait to upgrade, because it looks like version 2.0.45 will be out early next week. There are a couple of silly problems that were introduced into this release that need to be fixed.
v &m =104321038630487&w=2
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...
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.
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.