You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Tom Browder <to...@gmail.com> on 2015/04/28 13:36:56 UTC
OpenSSL 1.02, PCRE 2.10
I can't get httpd to work with either of the two subject packages, and
I found other, similar results from a web search. Is there a
work-around for either or both, or do I have to drop back and punt
with older packages?
Best,
-Tom
P.S. I have offered to start a tutorial on the wiki ref 2.4
configuration and installation but no reply yet.
Re: OpenSSL 1.02, PCRE 2.10
Posted by Stefan Eissing <st...@greenbytes.de>.
./configure --enable-mpms-shared=all --with-included-apr --with-ssl=<dir>
and on OS X additionally a locally installed pcre --with-pcre=<dir>
apr 1.5.1, apr-util 1.5.4, local pcre 8.36 on OS X (+ some homebrew things I already had)
Hope that helps,
Stefan
> Am 28.04.2015 um 14:08 schrieb Tom Browder <to...@gmail.com>:
>
> On Tue, Apr 28, 2015 at 7:05 AM, Stefan Eissing
> <st...@greenbytes.de> wrote:
>> Have openssl 1.0.2 running with 2.4.12 in a local installation on Ubuntu 14.04. No special wrestling other than —with-openssl=… in configure.
>
> How about apr and apr-util: locally built and installed system-wide or
> '--with-included-apr'?
>
> Best,
>
> -Tom
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Tue, Apr 28, 2015 at 7:05 AM, Stefan Eissing
<st...@greenbytes.de> wrote:
> Have openssl 1.0.2 running with 2.4.12 in a local installation on Ubuntu 14.04. No special wrestling other than —with-openssl=… in configure.
How about apr and apr-util: locally built and installed system-wide or
'--with-included-apr'?
Best,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Stefan Eissing <st...@greenbytes.de>.
Have openssl 1.0.2 running with 2.4.12 in a local installation on Ubuntu 14.04. No special wrestling other than —with-openssl=… in configure.
//Stefan
> Am 28.04.2015 um 13:45 schrieb Eric Covener <co...@gmail.com>:
>
> On Tue, Apr 28, 2015 at 7:36 AM, Tom Browder <to...@gmail.com> wrote:
>> I can't get httpd to work with either of the two subject packages, and
>> I found other, similar results from a web search. Is there a
>> work-around for either or both, or do I have to drop back and punt
>> with older packages?
>
>
> AIUI PCRE2 doesn't work and it's not just a trivial port. Surprised
> about openssl 1.02 though -- what exactly do you see?
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Wed, Apr 29, 2015 at 7:09 PM, Yann Ylavic <yl...@gmail.com> wrote:
> On Thu, Apr 30, 2015 at 1:57 AM, Tom Browder <to...@gmail.com> wrote:
>>
>> apachectl
>> httpd: Syntax error on line 147 of /usr/local/apache2/conf/httpd.conf:
>> Cannot load modules/mod_session_crypto.so into server:
>> /usr/local/apache2/modules/mod_session_crypto.so: undefined symbol:
>> ap_hook_session_encode
>
> You probably need to also:
> LoadModule session_module modules/mod_sessions.so
First I tried
--enable-session
which is supposed to have it enabled in the httpd.conf file but it
doesn't (a bug).
But the '--enable-load-all-modules' does work!
I also found that the https.conf file wasn't changing during my config
changes (I believe that warrants a better note and perhaps another
option such as '--force' which recreates all when experimenting as I
have been doing). I have to remove them before installation.
But, after I manually uncommented the session module in the httpd.conf
file all seems to work fine and I am able to start my shiny new httpd.
Thanks so much Yann for bearing with me through this useful exercise!
Warmest regards,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Apr 30, 2015 at 1:57 AM, Tom Browder <to...@gmail.com> wrote:
>
> apachectl
> httpd: Syntax error on line 147 of /usr/local/apache2/conf/httpd.conf:
> Cannot load modules/mod_session_crypto.so into server:
> /usr/local/apache2/modules/mod_session_crypto.so: undefined symbol:
> ap_hook_session_encode
You probably need to also:
LoadModule session_module modules/mod_sessions.so
And use configure's --enable-session=shared if you did not already.
Regards,
Yann.
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Wed, Apr 29, 2015 at 6:30 PM, Tom Browder <to...@gmail.com> wrote:
> On Apr 29, 2015 6:08 PM, "Yann Ylavic" <yl...@gmail.com> wrote:
...
>> Did you try --with-openssl=/opt/openssl in addition to --with-ssl?
>
> No, but I tried other variants--let me try that.
Okay, now httpd is using openssl/libcrypto.
However, when I try apachectl I get:
apachectl
httpd: Syntax error on line 147 of /usr/local/apache2/conf/httpd.conf:
Cannot load modules/mod_session_crypto.so into server:
/usr/local/apache2/modules/mod_session_crypto.so: undefined symbol:
ap_hook_session_encode
It seems we are making progress, but what should be tried next. Is
that a mod_session_crypto bug, or?
Thanks.
Best,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Apr 29, 2015 6:08 PM, "Yann Ylavic" <yl...@gmail.com> wrote:
>
> On Thu, Apr 30, 2015 at 12:39 AM, Tom Browder <to...@gmail.com>
wrote:
> >
> > configure: error: Crypto was requested but no crypto library could be
> > enabled; specify the location of a crypto library using
> > --with-openssl, --with-nss, etc.
> > configure failed for srclib/apr-util
>
> Did you try --with-openssl=/opt/openssl in addition to --with-ssl?
No, but I tried other variants--let me try that.
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Apr 30, 2015 at 12:39 AM, Tom Browder <to...@gmail.com> wrote:
>
> One more requirement: I want to use mod_session_crypto so I have to
> '--enable-sesion-crypto' and, with Yann's options, I still get the
> error:
>
> configure: error: Crypto was requested but no crypto library could be
> enabled; specify the location of a crypto library using
> --with-openssl, --with-nss, etc.
> configure failed for srclib/apr-util
Did you try --with-openssl=/opt/openssl in addition to --with-ssl?
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Wed, Apr 29, 2015 at 4:51 PM, Yann Ylavic <yl...@gmail.com> wrote:
> Hi Tom,
>
> On Wed, Apr 29, 2015 at 11:10 PM, Tom Browder <to...@gmail.com> wrote:
>>
>> I'm just trying to work around the current build systems to meet a
>> specific goal and I would appreciate anyone who can tell me EXACTLY
>> how to:
>>
>> + use the latest openssl
>> + use the latest apr and apr-util
>> + use the latest httpd
...
One more requirement: I want to use mod_session_crypto so I have to
'--enable-sesion-crypto' and, with Yann's options, I still get the
error:
configure: error: Crypto was requested but no crypto library could be
enabled; specify the location of a crypto library using
--with-openssl, --with-nss, etc.
configure failed for srclib/apr-util
I have not found any documentation in apr or apr-util on how to
specify the crypto library.
Thanks.
Best regards,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Yann Ylavic <yl...@gmail.com>.
Hi Tom,
On Wed, Apr 29, 2015 at 11:10 PM, Tom Browder <to...@gmail.com> wrote:
>
> I'm just trying to work around the current build systems to meet a
> specific goal and I would appreciate anyone who can tell me EXACTLY
> how to:
>
> + use the latest openssl
> + use the latest apr and apr-util
> + use the latest httpd
Your goal is to do that dynamically now, right?
>
> At the moment I am starting again but this time trying:
>
> + building and installing the latest openssl with shared libraries
> + building and installing apr and apr-util to use latest openssl
> + building and installing httpd to use all the above
With shared libraries then, once the first point is done (say in
/opt/openssl), the simplest way is for the two others is to:
1. tar xf httpd-2.4.12.tar.bz2
2. cd httpd-2.4.12
3. tar xf extract apr-1.5.2.tar.bz2 -C srclib && mv srclib/apr-1.5.2 srclib/apr
4. tar xf extract apr-util-1.5.4.tar.bz2 -C srclib && mv
srclib/apr-util-1.5.2 srclib/apr-util
4. ./buildconf
5. ./configure --prefix=/opt/httpd --with-included-apr
--with-ssl=/opt/openssl "LDFLAGS=-Wl,-rpath,/opt/openssl/lib" ...
(the LDFLAGS can be omitted if you plan to somehow include
/opt/openssl/lib in LD_LIBRARY_PATH at runtime, to avoid conflct with
system's own libs)
6. make && make install
Hope I'm not off topic (you meant building statically).
Regards,
Yann.
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Wed, Apr 29, 2015 at 3:29 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
> Just to point out the obvious, it would be a Very Bad Idea(tm) to build
> httpd against the dynamic apr-util linked statically to bits and pieces of the
...
I'm just trying to work around the current build systems to meet a
specific goal and I would appreciate anyone who can tell me EXACTLY
how to:
+ use the latest openssl
+ use the latest apr and apr-util
+ use the latest httpd
At the moment I am starting again but this time trying:
+ building and installing the latest openssl with shared libraries
+ building and installing apr and apr-util to use latest openssl
+ building and installing httpd to use all the above
Best,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
Just to point out the obvious, it would be a Very Bad Idea(tm) to build
httpd
against the dynamic apr-util linked statically to bits and pieces of the
libssl.a
and libcrypto.a, only to then attempt to build httpd with mod_ssl
compiled-in
against libssl.a/libcrypto.a again. Unix dl logic doesn't usually play
well, this
isn't multiple-depth namespace.
It sounds a bit like the comedy routine, "Doctor, it hurts when I move this
way..."
so could you explain better why you are trying to accomplish what you are
trying
to accomplish? If you rebuild and reinstall ssl in reaction to a critical
vulnerability,
the vulnerability will still be present in your httpd with mod_ssl compiled
in. For
that reason and many others, dynamic libs are generally your friends.
The error you encountered in ./configure is that it will attempt to
compile, link
and run a short stub based on all the input parameters. When the flags
aren't
correct to resolve the headers or libraries or run time loadable objects,
then
configure fails. It is usually helpful to go through the config.log
results to see
just what it tried to do when it failed.
On Wed, Apr 29, 2015 at 10:56 AM, Kaspar Brand <ht...@velox.ch>
wrote:
> On 29.04.2015 15:06, Tom Browder wrote:
> > On Wed, Apr 29, 2015 at 12:57 AM, Kaspar Brand <ht...@velox.ch>
> wrote:
> >> On 28.04.2015 14:04, Tom Browder wrote:
> >>> I have no system installed openssl,
> >>
> >> Hmm, what platform is this? Are you sure there are no libcrypto/libssl
> >> libraries somewhere under /usr?
> >
> > I used a netinst installation of Debian 7. But I find I do have those
> > libraries:
> >
> > /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> > /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
>
> Ok. Debian has separate packages for the libraries and the command-line
> tool, so "no system installed openssl" is true as far as the "openssl"
> package is concerned. I'd bet that Debian is barely usable when the
> "libssl1.0.0" package is missing, though.
>
> > configure: error: Crypto was requested but no crypto library could be
> > enabled; specify the location of a crypto library using
> > --with-openssl, --with-nss, etc.
>
> This is actually APR-util configure stuff, so does not apply to mod_ssl
> itself. Unless you really have a need for mod_session_crypto, just leave
> out the --enable-crypto and --enable-session-crypto options, for the
> time being (they are not needed for mod_ssl, and are probably just
> making things more complicated than necessary right now).
>
> > The question to me is: what exact configuration do I need? Do I point
> > to a path, or library, or a configure script? I see nothing
>
> For a statically linked mod_ssl, you need "--enable-ssl
> --with-ssl=/opt/openssl --enable-ssl-staticlib-deps" (assuming that you
> used --prefix=/opt/openssl for OpenSSL's ./config or ./Configure).
>
> Kaspar
>
Re: OpenSSL 1.02, PCRE 2.10
Posted by Kaspar Brand <ht...@velox.ch>.
On 29.04.2015 15:06, Tom Browder wrote:
> On Wed, Apr 29, 2015 at 12:57 AM, Kaspar Brand <ht...@velox.ch> wrote:
>> On 28.04.2015 14:04, Tom Browder wrote:
>>> I have no system installed openssl,
>>
>> Hmm, what platform is this? Are you sure there are no libcrypto/libssl
>> libraries somewhere under /usr?
>
> I used a netinst installation of Debian 7. But I find I do have those
> libraries:
>
> /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
> /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
Ok. Debian has separate packages for the libraries and the command-line
tool, so "no system installed openssl" is true as far as the "openssl"
package is concerned. I'd bet that Debian is barely usable when the
"libssl1.0.0" package is missing, though.
> configure: error: Crypto was requested but no crypto library could be
> enabled; specify the location of a crypto library using
> --with-openssl, --with-nss, etc.
This is actually APR-util configure stuff, so does not apply to mod_ssl
itself. Unless you really have a need for mod_session_crypto, just leave
out the --enable-crypto and --enable-session-crypto options, for the
time being (they are not needed for mod_ssl, and are probably just
making things more complicated than necessary right now).
> The question to me is: what exact configuration do I need? Do I point
> to a path, or library, or a configure script? I see nothing
For a statically linked mod_ssl, you need "--enable-ssl
--with-ssl=/opt/openssl --enable-ssl-staticlib-deps" (assuming that you
used --prefix=/opt/openssl for OpenSSL's ./config or ./Configure).
Kaspar
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Wed, Apr 29, 2015 at 12:57 AM, Kaspar Brand <ht...@velox.ch> wrote:
> On 28.04.2015 14:04, Tom Browder wrote:
>> Maybe I need to play tricks with ld.so.conf and openssl?
>
> Depends on whether you built OpenSSL with or without shared libraries -
> what are the contents of the /opt/openssl/lib directory?
Well, I failed to follow my original recipe and did NOT specify
'no-shared'. I blem away openssl and used 'no-shared' and now have NO
shared libraries in /opt/openssl/lib.
>> I have no system installed openssl,
>
> Hmm, what platform is this? Are you sure there are no libcrypto/libssl
> libraries somewhere under /usr?
I used a netinst installation of Debian 7. But I find I do have those
libraries:
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
> The most important thing, though, is making sure that the directory
> which appears in the LDFLAGS/MOD_LDFLAGS lines of the ./configure
> outputs (after the "checking for user-provided OpenSSL base
> directory...") in does not include any shared library files - only
> static ones.
That is now true.
After a rebuild and re-install of openssl, I reconfigured httpd.and get this:
configure: error: Crypto was requested but no crypto library could be
enabled; specify the location of a crypto library using
--with-openssl, --with-nss, etc.
The question to me is: what exact configuration do I need? Do I point
to a path, or library, or a configure script? I see nothing
I've tried '--with-openssl=<path>' and '--with-nss=<path>' to no avail.
Any suggestions?
Thanks.
Best,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Kaspar Brand <ht...@velox.ch>.
On 28.04.2015 14:04, Tom Browder wrote:
> On Tue, Apr 28, 2015 at 6:45 AM, Eric Covener <co...@gmail.com> wrote:
>> about openssl 1.02 though -- what exactly do you see?
>
> I see this when attempting to start apache:
>
> /usr/local/apache2/bin/httpd: symbol lookup error:
> /usr/local/apache2/bin/httpd: undefined symbol: SSL_CONF_CTX_new
>
> Maybe I need to play tricks with ld.so.conf and openssl?
Depends on whether you built OpenSSL with or without shared libraries -
what are the contents of the /opt/openssl/lib directory?
> I have no system installed openssl,
Hmm, what platform is this? Are you sure there are no libcrypto/libssl
libraries somewhere under /usr?
> SSLDIR=/opt/openssl
> export LDFLAGS="-L${SSLDIR}/lib"
This should not be needed.
> --enable-ssl \
> --enable-ssl-staticlib-deps \
> --enable-mods-static=ssl \
> --with-ssl=${SSLDIR} \
"--enable-mods-static=ssl" is probably not really what you want - it
includes mod_ssl in the httpd binary itself, but other than that, it
doesn't have an impact on how mod_ssl is linked against libcrypto/libssl
(you might try to see what "ldd /usr/local/apache2/bin/httpd" says).
The most important thing, though, is making sure that the directory
which appears in the LDFLAGS/MOD_LDFLAGS lines of the ./configure
outputs (after the "checking for user-provided OpenSSL base
directory...") in does not include any shared library files - only
static ones.
Kaspar
Re: OpenSSL 1.02, PCRE 2.10
Posted by Tom Browder <to...@gmail.com>.
On Tue, Apr 28, 2015 at 6:45 AM, Eric Covener <co...@gmail.com> wrote:
> On Tue, Apr 28, 2015 at 7:36 AM, Tom Browder <to...@gmail.com> wrote:
>> I can't get httpd to work with either of the two subject packages, and
>> I found other, similar results from a web search. Is there a
>> work-around for either or both, or do I have to drop back and punt
>> with older packages?
>
>
> AIUI PCRE2 doesn't work and it's not just a trivial port.
I understand.
> about openssl 1.02 though -- what exactly do you see?
I see this when attempting to start apache:
/usr/local/apache2/bin/httpd: symbol lookup error:
/usr/local/apache2/bin/httpd: undefined symbol: SSL_CONF_CTX_new
Maybe I need to play tricks with ld.so.conf and openssl? I have no
system installed openssl, just my locally built version (1.0.2). In
my configuration options I have:
SSLDIR=/opt/openssl
export LDFLAGS="-L${SSLDIR}/lib"
$SRCDIR/configure \
--prefix=/usr/local/apache2 \
--with-included-apr \
\
--enable-ssl \
--enable-ssl-staticlib-deps \
--enable-mods-static=ssl \
--with-ssl=${SSLDIR} \
\
--enable-mods-shared=reallyall \
--with-perl \
--with-python \
--enable-layout=Apache \
--with-pcre=/usr/local/bin/pcre-config \
--without-ldap \
--enable-session-crypto \
--with-crypto \
--with-openssl=/opt/openssl
Thanks, Eric.
Best,
-Tom
Re: OpenSSL 1.02, PCRE 2.10
Posted by Eric Covener <co...@gmail.com>.
On Tue, Apr 28, 2015 at 7:36 AM, Tom Browder <to...@gmail.com> wrote:
> I can't get httpd to work with either of the two subject packages, and
> I found other, similar results from a web search. Is there a
> work-around for either or both, or do I have to drop back and punt
> with older packages?
AIUI PCRE2 doesn't work and it's not just a trivial port. Surprised
about openssl 1.02 though -- what exactly do you see?