On Wed, Oct 21, 1998, Tony Earnshaw wrote:
> Platform SCO 3.2v5.0.4, gcc 2.7.2.3, P166/96 MB/10 GB, maid of all work
> - does _everything_ - and a lot more ...
Fine.
> Apache 1.3.3/mod_ssl/PHP 3.0.5/MySQL 3.21.33 (still can't get mod_perl
> to compile with mod_ssl, but that's a SCO header-file problem).
What header is exactly the problem?
Perhaps we can do a workaround for SCO?
> I had mod_ssl 2.0.13 working perfectly on the above. So, I thought "why
> not try 2.1b6?"
<grin>
> Well, I'm glad I did. It's so utterly elegant that I still can't believe
> it, so congratulations to everyone who's got it this far (still shudder
> when thinking back to Apache-SSL days, that I never could get to work).
>
> Straight compiles (I use small do-conf scripts for configure, trick
> learned from php3 compilation), new make install, 20 minutes for a
> complete new configuration and up and running.
<grin> Yes, but please know don't forget to focus on the real security aspects
now. Because as I (more than once) tried to explain on my ApacheCon talk:
mod_ssl is such easy to install not to support lusers in establishing an
SSL-aware server (even this happens). No, it's such easy to install in order
to avoid waste of time, so the webmaster can immediately focus on the real
security aspects and has not to fiddle around one week building the package.
So, be happy that it was such easy to establish, but don't think you're now
secure, please ;-)
Nevertheless thanks for this nice positive feedback.
Greetings,
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
