Slashdot Mirror

chipster writes "Apache 1.3.32 has been released. This version of Apache is principally a security and bug fix release. You can read about the new features here, and get Apache 1.3.32 here. Also available is the 1.3 ChangeLog. Additionally, to compliment this release of Apache, mod_ssl- 2.8.21-1.3.32 has also been released."

Ralf S. Engelschall writes: "The slide set of my presentation, 'Security Solutions with SSL,' which I gave at ApacheCon 2000/EU in London last Monday is available online under http://www.modssl.org/docs/apachecon2000/. Check it out if you have not attended ApacheCon but if you are nevertheless interested in Apache and SSL. A PNG-capable browser is required to view."

Skapare asks: "A year ago, this question about using Apache and SSL in a commercial environment was asked in the Apache section of Slashdot. The RSA patent was still in force back then, and the focus was on commercial products like Raven. Since then, the RSA patent has been released and then expired. That same month a year ago, Ask Slashdot also featured a question about encumbrance of SSL/PGP. But with the RSA patent gone, and Diffie-Hellman before it, this surely opens up Apache with SSL free for commercial use. Now I'm exploring options for free SSL for Apache, and note at least two choices, Apache-SSL, and mod_ssl. What I'd like to ask is what are the fundamental and principle differences between these free versions that I should consider in deciding which I should use in a commercial environment."

EraseMe asks: "I have a great idea for an open source project, but I don't know where to begin. I'm tired of paying large cash for SSL Certifications from companies such as VeriSign. It would be great to provide companies and individuals with free certifications, with one central server providing the solution. I would imagine this wouldn't be terribly difficult to implement over exisiting applications such as OpenSSL and mod_ssl." This would be a cool idea, but if the certs are free, how would such an entity stay afloat and pay for things like servers, office space and bandwidth?

x00 writes "I am looking into using a SSL Server (preferably with Apache) and I came across mod_ssl and Apache-SSL. What I'd like to know is, what are the differences between the two, and what are their benefits and disadvantages. I've looked at the respective sites and they give you little information on this. mod_ssl just says to compare the code changes between the two and Apache-SSL just acknowledges that mod_ssl exists. " jimjag responds: a short description of the differences between the 2 are that mod_ssl uses the module approach of "hooking" into Apache, whereas Apache-SSL is more of a "built in" solution. Both require patching the official Apache source code, to allow for the actual SSL hooks. mod_ssl was heavily based on the original Apache-SSL and was written to make it less a "big patch" and more of a "drop-in" module that can be used. Loyal /. readers, please add your comments and suggestions! :)