You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Austin Gonyou <au...@coremetrics.com> on 2001/04/09 23:37:20 UTC

mod_tls support

Compiling with ssl causes a problem. Here is the error message and
config.log

-> checking for SSL library... checking whether to enable mod_tls... yes
-> configure: error: no - Unable to locate yes/inc/ssl.h

It apears that the TLS --enable-tls option was read, but then the ssl libs
are all screwey.
I've found the following section in the configure script which seems to be
causing the problem. Can anyone confirm or deny this? What should be the
proper syntax?


------begin code snippet-------
  # Check whether --with-ssl or --without-ssl was given.
if test "${with_ssl+set}" = set; then
  withval="$with_ssl"                          #Notice here that withval
      searchfile="$withval/inc/ssl.h"	 	#is set to 'yes'. All
      if test -f $searchfile ; then		#tests fail from here on.
          INCLUDES="$INCLUDES -I$withval/inc"
          LIBS="$LIBS -L$withval -lsslc"
          ssl_lib="SSLC"
      else
          searchfile="$withval/ssl/ssl.h"
          if test -f $searchfile ; then
              INCLUDES="$INCLUDES -I$withval/include"
              LIBS="$LIBS -L$withval -lssl -lcrypto"
              ssl_lib="OpenSSL"
          else
              searchfile="$withval/openssl/ssl.h"  #changing this from
              if test -f $searchfile ; then	   #withval to /usr/include
                  INCLUDES="$INCLUDES -I$withval/openssl" #seems to work.
                  LIBS="$LIBS -L$withval -lssl -lcrypto"
                  ssl_lib="OpenSSL"
              else
                  { echo "configure: error: no - Unable to locate
$withval/inc/ssl.h" 1>&2; exit 1; }
              fi
          fi
      fi
      echo "$ac_t""found $ssl_lib" 1>&6

else

      { echo "configure: error: --with-ssl not given" 1>&2; exit 1; }

fi
-------End code snippet--------

So the question here is what should withval be set to or how should it be
used. When I change the $withval/openssl/ssl.h to
/usr/include/openssl/ssl.h then everything works and it reports:

checking for SSL library... checking whether to enable mod_tls... yes
found OpenSSL

Anyone?

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com



Re: mod_tls support

Posted by Austin Gonyou <au...@coremetrics.com>.
I prefer that it ONLY work with OpenSSL 0.9.6 or better. Just my
preferrence, but I've found some improvement with each release of openssl.

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com

On Mon, 9 Apr 2001 rbb@covalent.net wrote:

>
> The config.m4 stuff for mod_tls still requires major work.  In fact, that
> whole module does.  The last time I checked, it only worked with OpenSSL
> 0.9.6 or better.  A lot of the config.m4 logic is to try to find the SSL
> libraries, and the SSL headers, for OpenSSL, and the RSA BSafe libraries.
> So far, we have only tried to make it work with source distributions of
> OpenSSL, not installed versions.  Getting it to work with installed
> versions across all the different platforms will take some time.
>
> Ryan
>
> > the modules/tls/config.m4 logic here strikes me as quite bogus. what
> > is the path being supplied? it peers into a number of subdirectories
> > to find the header files, but assumes the libraries are in the
> > supplied directory.
> >
> > it should also either try to guess the path or bail when just
> > --with-ssl is used. the current behavior (using 'yes' as the path)
> > is more than a little confusing.
> >
> > i'm not familiar enough with how openssl is installed (by default
> > or by various distributions) to know what the right thing to do is,
> > but on a debian system, the libraries are in /usr/lib and the
> > headers in /usr/include/openssl. if a read the current config.m4
> > right, i would supply --with-ssl=/usr/include, and a -L/usr/include
> > would get added to the link flags. that's obviously wrong.
> >
> > jim
> >
> >
>
>
> _______________________________________________________________________________
> Ryan Bloom                        	rbb@apache.org
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------
>


Re: mod_tls support

Posted by rb...@covalent.net.
The config.m4 stuff for mod_tls still requires major work.  In fact, that
whole module does.  The last time I checked, it only worked with OpenSSL
0.9.6 or better.  A lot of the config.m4 logic is to try to find the SSL
libraries, and the SSL headers, for OpenSSL, and the RSA BSafe libraries.
So far, we have only tried to make it work with source distributions of
OpenSSL, not installed versions.  Getting it to work with installed
versions across all the different platforms will take some time.

Ryan

> the modules/tls/config.m4 logic here strikes me as quite bogus. what
> is the path being supplied? it peers into a number of subdirectories
> to find the header files, but assumes the libraries are in the
> supplied directory.
>
> it should also either try to guess the path or bail when just
> --with-ssl is used. the current behavior (using 'yes' as the path)
> is more than a little confusing.
>
> i'm not familiar enough with how openssl is installed (by default
> or by various distributions) to know what the right thing to do is,
> but on a debian system, the libraries are in /usr/lib and the
> headers in /usr/include/openssl. if a read the current config.m4
> right, i would supply --with-ssl=/usr/include, and a -L/usr/include
> would get added to the link flags. that's obviously wrong.
>
> jim
>
>


_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Re: mod_tls support

Posted by Austin Gonyou <au...@coremetrics.com>.
Right. This is part of my confusion here. I've looked at the logic, I even
posted it to show what it's trying to do. It's obvious that withval is
getting set to yes. Not sure why, and supplying a path to openssl hasn't
solved anything as yet, except to give me an even more ridiculous error.
I'm going to do my usual punnet and see if that works. I'll report status
as soon as I'm done.

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com

On Mon, 9 Apr 2001, Jim Winstead wrote:

> On Mon, Apr 09, 2001 at 02:44:50PM -0700, rbb@covalent.net wrote:
> > > So the question here is what should withval be set to or how should it be
> > > used. When I change the $withval/openssl/ssl.h to
> > > /usr/include/openssl/ssl.h then everything works and it reports:
> > >
> > > checking for SSL library... checking whether to enable mod_tls... yes
> > > found OpenSSL
> > >
> > > Anyone?
> >
> > You should be using --with-ssl=/path/to/openssl.  This argument is used to
> > find your SSL header files.  If you do not provide a path, we can not find
> > them.
>
> the modules/tls/config.m4 logic here strikes me as quite bogus. what
> is the path being supplied? it peers into a number of subdirectories
> to find the header files, but assumes the libraries are in the
> supplied directory.
>
> it should also either try to guess the path or bail when just
> --with-ssl is used. the current behavior (using 'yes' as the path)
> is more than a little confusing.
>
> i'm not familiar enough with how openssl is installed (by default
> or by various distributions) to know what the right thing to do is,
> but on a debian system, the libraries are in /usr/lib and the
> headers in /usr/include/openssl. if a read the current config.m4
> right, i would supply --with-ssl=/usr/include, and a -L/usr/include
> would get added to the link flags. that's obviously wrong.
>
> jim
>


Re: mod_tls support

Posted by Jim Winstead <ji...@trainedmonkey.com>.
On Mon, Apr 09, 2001 at 02:44:50PM -0700, rbb@covalent.net wrote:
> > So the question here is what should withval be set to or how should it be
> > used. When I change the $withval/openssl/ssl.h to
> > /usr/include/openssl/ssl.h then everything works and it reports:
> >
> > checking for SSL library... checking whether to enable mod_tls... yes
> > found OpenSSL
> >
> > Anyone?
> 
> You should be using --with-ssl=/path/to/openssl.  This argument is used to
> find your SSL header files.  If you do not provide a path, we can not find
> them.

the modules/tls/config.m4 logic here strikes me as quite bogus. what
is the path being supplied? it peers into a number of subdirectories
to find the header files, but assumes the libraries are in the
supplied directory.

it should also either try to guess the path or bail when just
--with-ssl is used. the current behavior (using 'yes' as the path)
is more than a little confusing.

i'm not familiar enough with how openssl is installed (by default
or by various distributions) to know what the right thing to do is,
but on a debian system, the libraries are in /usr/lib and the
headers in /usr/include/openssl. if a read the current config.m4
right, i would supply --with-ssl=/usr/include, and a -L/usr/include
would get added to the link flags. that's obviously wrong.

jim

Re: mod_tls support

Posted by Greg Stein <gs...@lyra.org>.
On Mon, Apr 09, 2001 at 03:05:12PM -0700, rbb@covalent.net wrote:
> 
> I don't have a good answer for you.  I haven't looked at mod_tls for a few
> months.  I keep meaning to go back to it, but I haven't had time recently.
> I will try to clean this up later this week.

Don't you mean that you'll add an item to STATUS for it? ;-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

mod_tls support - Demystified!

Posted by Austin Gonyou <au...@coremetrics.com>.
is you use --with-ssl=/path/to/openssl

path/to/openssl should be your openssl source tree. It configured with no
modifications whatsoever after I did that. So, like with mod_ssl, you can
build it, but not actually have it installed on your system anywhere. Good
deal. I'll let everyone know if it builds successfully and works. If it
doesn't I'll supply my build log.

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com



Re: mod_tls support

Posted by rb...@covalent.net.
The goal is to get SSL support into AB.  I believe Dirk began to do this
work last week sometime.

Ryan

On Mon, 9 Apr 2001, Austin Gonyou wrote:

> Sorry to ask a dumb question but since apache 2.0 has ssl support, does
> that mean AB will support ssl?
>
> --
> Austin Gonyou
> Systems Architect
> Coremetrics, Inc.
> Phone: 512-796-9023
> email: austin@coremetrics.com
>
>
>


_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Re: mod_tls support

Posted by Austin Gonyou <au...@coremetrics.com>.
Sorry to ask a dumb question but since apache 2.0 has ssl support, does
that mean AB will support ssl?

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com



Re: mod_tls support

Posted by Austin Gonyou <au...@coremetrics.com>.
That's ok. I'm just asking questions here and trying to get/help get
clarity on the subject.

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com

On Mon, 9 Apr 2001 rbb@covalent.net wrote:

>
> I don't have a good answer for you.  I haven't looked at mod_tls for a few
> months.  I keep meaning to go back to it, but I haven't had time recently.
> I will try to clean this up later this week.
>
> Ryan
>
> On Mon, 9 Apr 2001, Austin Gonyou wrote:
>
> >
> > I agree, but if I give it --with-ssl=/usr/include/openssl then it still
> > fails and instead of yes/inc/ssl.h I just get
> > /usr/include/openssl/yes/inc/ssl.h. Or is it that I should give it the
> > path to the openssl binary? Or is it like mod_ssl where I usually just
> > build openssl, not install it, and then tell mod_ssl configure where the
> > source tree is?
> >
> > --
> > Austin Gonyou
> > Systems Architect
> > Coremetrics, Inc.
> > Phone: 512-796-9023
> > email: austin@coremetrics.com
> >
> > On Mon, 9 Apr 2001 rbb@covalent.net wrote:
> >
> > >
> > > > So the question here is what should withval be set to or how should it be
> > > > used. When I change the $withval/openssl/ssl.h to
> > > > /usr/include/openssl/ssl.h then everything works and it reports:
> > > >
> > > > checking for SSL library... checking whether to enable mod_tls... yes
> > > > found OpenSSL
> > > >
> > > > Anyone?
> > >
> > > You should be using --with-ssl=/path/to/openssl.  This argument is used to
> > > find your SSL header files.  If you do not provide a path, we can not find
> > > them.
> > >
> > > Ryan
> > >
> > > _______________________________________________________________________________
> > > Ryan Bloom                        	rbb@apache.org
> > > 406 29th St.
> > > San Francisco, CA 94131
> > > -------------------------------------------------------------------------------
> > >
> >
> >
>
>
> _______________________________________________________________________________
> Ryan Bloom                        	rbb@apache.org
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------
>


Re: mod_tls support

Posted by rb...@covalent.net.
I don't have a good answer for you.  I haven't looked at mod_tls for a few
months.  I keep meaning to go back to it, but I haven't had time recently.
I will try to clean this up later this week.

Ryan

On Mon, 9 Apr 2001, Austin Gonyou wrote:

>
> I agree, but if I give it --with-ssl=/usr/include/openssl then it still
> fails and instead of yes/inc/ssl.h I just get
> /usr/include/openssl/yes/inc/ssl.h. Or is it that I should give it the
> path to the openssl binary? Or is it like mod_ssl where I usually just
> build openssl, not install it, and then tell mod_ssl configure where the
> source tree is?
>
> --
> Austin Gonyou
> Systems Architect
> Coremetrics, Inc.
> Phone: 512-796-9023
> email: austin@coremetrics.com
>
> On Mon, 9 Apr 2001 rbb@covalent.net wrote:
>
> >
> > > So the question here is what should withval be set to or how should it be
> > > used. When I change the $withval/openssl/ssl.h to
> > > /usr/include/openssl/ssl.h then everything works and it reports:
> > >
> > > checking for SSL library... checking whether to enable mod_tls... yes
> > > found OpenSSL
> > >
> > > Anyone?
> >
> > You should be using --with-ssl=/path/to/openssl.  This argument is used to
> > find your SSL header files.  If you do not provide a path, we can not find
> > them.
> >
> > Ryan
> >
> > _______________________________________________________________________________
> > Ryan Bloom                        	rbb@apache.org
> > 406 29th St.
> > San Francisco, CA 94131
> > -------------------------------------------------------------------------------
> >
>
>


_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------


Re: mod_tls support

Posted by Austin Gonyou <au...@coremetrics.com>.
I agree, but if I give it --with-ssl=/usr/include/openssl then it still
fails and instead of yes/inc/ssl.h I just get
/usr/include/openssl/yes/inc/ssl.h. Or is it that I should give it the
path to the openssl binary? Or is it like mod_ssl where I usually just
build openssl, not install it, and then tell mod_ssl configure where the
source tree is?

-- 
Austin Gonyou
Systems Architect
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@coremetrics.com

On Mon, 9 Apr 2001 rbb@covalent.net wrote:

>
> > So the question here is what should withval be set to or how should it be
> > used. When I change the $withval/openssl/ssl.h to
> > /usr/include/openssl/ssl.h then everything works and it reports:
> >
> > checking for SSL library... checking whether to enable mod_tls... yes
> > found OpenSSL
> >
> > Anyone?
>
> You should be using --with-ssl=/path/to/openssl.  This argument is used to
> find your SSL header files.  If you do not provide a path, we can not find
> them.
>
> Ryan
>
> _______________________________________________________________________________
> Ryan Bloom                        	rbb@apache.org
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------
>


Re: mod_tls support

Posted by rb...@covalent.net.
> So the question here is what should withval be set to or how should it be
> used. When I change the $withval/openssl/ssl.h to
> /usr/include/openssl/ssl.h then everything works and it reports:
>
> checking for SSL library... checking whether to enable mod_tls... yes
> found OpenSSL
>
> Anyone?

You should be using --with-ssl=/path/to/openssl.  This argument is used to
find your SSL header files.  If you do not provide a path, we can not find
them.

Ryan

_______________________________________________________________________________
Ryan Bloom                        	rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------