I knew this is old but we can't stop production right a way! need some time to
upgrade.. I am looking for small hack...
After couple of changes in Makefile of mod_ssl i build libssl.so module with
the help of apxs. But what if i want name like mod_ssl.so what should i do ? or
just rename libssl.so to mod_ssl.so
[satish@donkey mod_ssl-2.8.1-1.3.19]$ ldd ./pkg.sslmod/libssl.so
statically linked
> From: [email protected]
> Date: Wed, 30 Mar 2011 16:57:29 -0400
> To: [email protected]
> Subject: Re: [users@httpd] mod_ssl with apach-1.3.19
>
> 1.3 is no longer supported, and 1.3.19 is an ancient version of 1.3. Over ten
> years old.
>
> However, reaching back into the past ... generally mod_ssl was built
> statically, rather than as a so. If it *was* built as a so, you might be able
> to rebuild it using apxs, but I'm not sure.
>
> This seems like the perfect opportunity to bring yourself into the current
> decade.
>
> On Mar 30, 2011, at 4:41 PM, satish patel wrote:
>
> > Hello Users,
> >
> > We have complicated issue here. let me explain in a bit. We have production
> > machine running on apache-1.3.19 / mod_ssl-2.8.1 / OpenSSL 0.9.5a. Now
> > issue in security scanner we found some issue in openssl 0.9.5a version and
> > mod_ssl-2.8.1 is statically compiled with openssl so we can just upgrade
> > openssl.
> >
> > So i am planing to compile mod_ssl-2.8.1 with fixed version of
> > openssl-0.9.5a so how should i proceed with this ? On other server i have
> > compile mod_ssl but module name is libssl.so why not mod_ssl.so
> >
> > can anybody suggest how to compule mod_ssl.so without re-compile apache..
> >
> > -Satish
>
> --
> Rich Bowen
> [email protected]
> [email protected]
> PGP Key ID CC78C893
>
>
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: [email protected]
> " from the digest: [email protected]
> For additional commands, e-mail: [email protected]
>