Re: mod_ssl on Linux requires gnu libc?
At 17:49 1998-10-13 -0500, Jeffrey W. Baker wrote: >Hi. I just tried to build the latest 2.0 version of mod_ssl. It complained >about not finding the header gnu/stubs.h. The system is a Linux libc5 slackware >box. on my libc6 box, this header exists. So the question is, does mod_ssl on >Linux require libc6, or is this a case of a broken configure script. No. mod_ssl does not require libc6. I've built 1.3.3 + mod_ssl 2.0.13-1.3.3 just fine with the old libc5 under RedHat 4.2. - -- magnus bodin http://åäö.x42.com/ __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: bind: Address already in use
At 13:39 1998-10-06 -0500, Patrick <[EMAIL PROTECTED]> wrote: > >apachectl startssl > >gives me this in error_log > > [Tue Oct 6 13:19:10 1998] ssl_gcache started > bind: Address already in use > >What is bind complaining about and why can't I run startssl? > SSLCacheServerPort has to be set to a port that is not used. This is only used internally within the machine for the session cache. You've probably set this port to 80, 443 or some other port already in use. 12345 works fine if you don't have any other daemon running there. http://www.engelschall.com/sw/mod_ssl/docs/#SSLCacheServerPort cheers. - -- magnus bodin http://bodin.org/ ** http://$sum(2,2).x42.com/ ** http://www.altameter.com/ __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Available: mod_perl 1.16
>I'm totally busy with other mod_ssl things these days but those of you who had >problems with the Apache+mod_perl+mod_ssl combination last time perhaps want >to try out this new release. Give us feedback if it works and if it doesn't >where problems still exist. Doug also created a INSTALL.simple.mod_ssl file >in the mod_perl distribution as I recognized via the CVS commit messages. >Look also at this file and give Doug MacEachern <[EMAIL PROTECTED]> feedback >when you discover problems. It works like a charm. However; I do it like this: ./configure \ --prefix=/usr/local/apache\ --enable-module=rewrite\ --enable-module=ssl\ --activate-module=src/modules/extra/mod_myownextra.o\ --enable-module=myownextra\ --activate-module=src/modules/perl/libperl.a\ --enable-module=perl\ But in the Configuration.apaci, the AddModuler-perl line always is last, but I suppose the mod_ssl, should, so I hand-reorder these lines in Configuration.apaci so that the last 3 lines appear in this order (top->bottom) myownextra, perl, ssl. Do I really have to be this paranoid? In what order do they HAVE to be? If this is important -- In what order should they appear in the configure-options to be correct from the start in the Configuration.apaci-file?I've experimented a lot, but the addmodule-ssl-line never seem to get to the bottom. Thanks again for every help, Victor and Ralf! - -- magnus bodin -- http://$sum(2,2).x42.com/ __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Problems "make certification"
At 11:48 1998-09-29 -0700, Ted Arden wrote: >A couple of things really: > >1) in your FAQ, you mentioned an app called "s_client" in the >SSLeay dist. that is used for testing the 443 port. I couldn't >find the app. SSL_DIR/bin e.g. /usr/local/ssl/bin/s_client >2) running the "make certification" produce the following errors: the make certificate only works before installation, doesn't it? Use the FAQ; #13 and #14 and remember not to call the CA the same name as the server, because then ca.sign won't work. (learnt the hard way ;-) My tip: copy ca.crt ca.crt.pem and mv ca.crt to ca.pem and run $ pem2der ca so you run up with a ca.crt in der-format. This is readable by both MSIE and netscape (mimetype: application/x-x509-ca-cert). If the clients install this ca.crt in their browser, they will accept your signed signed server-certs. This of course only holds if you distribute the ca.cert in a secure manner (i.e. neither by unencrypted mail nor http) - -- magnus bodin - now a happy mod_ssl user __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
more faqs(?) (was: mod_perl s/t broke mod_ssl u A/1.3.2
At 03:43 1998-09-28 +0400, Khimenko Victor wrote: >While testing binary version of apache for KSI-Linux I'm found nasty error >with mod_perl (1.15_01) and mod_ssl (2.0.11) under apache 1.3.2. > >This version >-- cut -- >AddModule mod_perl.c >... >AddModule mod_ssl.c >-- cut -- >will be ok, while this version >-- cut -- >AddModule mod_ssl.c >... >AddModule mod_perl.c >-- cut -- >will not start ssl_gcache and will core dump somewhere in the ap_run_cleanup ! Is this really a bug? mod_ssl demands to be first to be able to negotiate the protocols before any other module gets their dirty fingers into the request. Thanks for all the help, by the way! I still can't get ssl to work along with my namedvirtualhosts. I've tried to do NameVirtualHost 194.16.2.88 Listen 80 Listen 443 . . SSLEnable SSLRequireSSL . . . . It work's fine apart from that accessing the host with https results in hanged browser. BUT: http://:443 works fine, and the -block is not even used. I would like it to work without having to allocate another ip uniquely used for the SSL-part of the server. the does not work; [Sun Sep 27 10:32:35 1998] [error] VirtualHost 194.16.2.89:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results. I would like a recipy for defining just 1 SSL-host for a setup that now uses namedvirtualhosts. URL doesn't matter. It can be the default. Another FAQ: It does apparaently matter what you set in ServerName; as mod_ssl gives different errors. This is from a test with just a ssl-server; [Sun Sep 27 10:45:02 1998] [error] mod_ssl: No SSL Certificate set for server kemal.netch.se:443 [hint: SSLCertificateFile] [Sun Sep 27 10:46:26 1998] [error] mod_ssl: No SSL Certificate set for server bodin.org:443 [hint: SSLCertificateFile] Where I actually have set the Certfile. OK. Doesn't some part of the certificate contain the HOSTNAME SOMEHOW? Either the whole hostname or at least the domainname. But where? Could be a faq. - -- magnus bodin - -- magnus bodin http://bodin.org/ ** http://åäö.x42.com/ ** http://www.altameter.com/ __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
more faqs(?) (was: mod_perl s/t broke mod_ssl u A/1.3.2
At 03:43 1998-09-28 +0400, Khimenko Victor wrote: >While testing binary version of apache for KSI-Linux I'm found nasty error >with mod_perl (1.15_01) and mod_ssl (2.0.11) under apache 1.3.2. > >This version >-- cut -- >AddModule mod_perl.c >... >AddModule mod_ssl.c >-- cut -- >will be ok, while this version >-- cut -- >AddModule mod_ssl.c >... >AddModule mod_perl.c >-- cut -- >will not start ssl_gcache and will core dump somewhere in the ap_run_cleanup ! Is this really a bug? mod_ssl demands to be first to be able to negotiate the protocols before any other module gets their dirty fingers into the request. Thanks for all the help, by the way! I still can't get ssl to work along with my namedvirtualhosts. I've tried to do NameVirtualHost 194.16.2.88 Listen 80 Listen 443 . . SSLEnable SSLRequireSSL . . . . It work's fine apart from that accessing the host with https results in hanged browser. BUT: http://:443 works fine, and the -block is not even used. I would like it to work without having to allocate another ip uniquely used for the SSL-part of the server. the does not work; [Sun Sep 27 10:32:35 1998] [error] VirtualHost 194.16.2.89:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results. I would like a recipy for defining just 1 SSL-host for a setup that now uses namedvirtualhosts. URL doesn't matter. It can be the default. Another FAQ: It does apparaently matter what you set in ServerName; as mod_ssl gives different errors. This is from a test with just a ssl-server; [Sun Sep 27 10:45:02 1998] [error] mod_ssl: No SSL Certificate set for server kemal.netch.se:443 [hint: SSLCertificateFile] [Sun Sep 27 10:46:26 1998] [error] mod_ssl: No SSL Certificate set for server bodin.org:443 [hint: SSLCertificateFile] Where I actually have set the Certfile. OK. Doesn't some part of the certificate contain the HOSTNAME SOMEHOW? Either the whole hostname or at least the domainname. But where? Could be a faq. - -- magnus bodin __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: INSTALLING mod_perl + mod_ssl + extra modules?
At 18:04 1998-09-24 +0200, I wrote: > >Thanks. It worked finally. > The building, that is. Starting with apachectl $ sbin/apachectl start sbin/apachectl start: httpd could not be started $ cat var/log/error_log: [Thu Sep 24 18:52:21 1998] [error] mod_ssl: Required SSLCacheServerPort missing And I don't even enable SSL in httpd.conf I use namevirtualhost like this (httpd.conf:) #no explicit host; as it generates errors. #Port 80 NameVirtualHost 194.16.2.89 ... ... ... Is it possible to use ssl in one of the virtualhost:s and there enable ssl? - -- magnus bodin http://bodin.org/ __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: INSTALLING mod_perl + mod_ssl + extra modules?
At 12:50 1998-09-24 +0200, Ralf S. Engelschall wrote: >What? H... I've extra tried it now again with > > Apache 1.3.2 > mod_ssl 2.0.11 > mod_perl 1.0.15_01 > >and with _exactly_ the steps from the INSTALL file (except for the above bug). >And it works fine. So you either have confused yourself while testing the >variants or your have a local platform problem? Thanks. It worked finally. I don't know what the problem was; but the final key was to remove all directories, unpack it from start and do it by hand instead of from a shellscript. And, yeah. I used Apache 1.3.2 mod_ssl 2.0.11 mod_perl 1.0.15_01 $ ./configure\ --prefix=/usr/local/apache\ --enable-module=rewrite\ --activate-module=src/modules/extra/mod_auth_cookie.o\ --enable-module=auth_cookie --activate-module=src/modules/perl/libperl.a\ --enable-module=perl\ --enable-module=ssl\ and then I checked src/Configuration.apaci just to be sure if the moduleorder was correct. - -- magnus bodin __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: INSTALLING mod_perl + mod_ssl + extra modules?
At 10:58 1998-09-24 +0200, Ralf S. Engelschall wrote: > >In article <> you wrote: >>[...] >>>> --activate-module=src/modules/perl > >> In my case it was >> --activate-module=src/modules/perl/libperl.a >> and compilation was succesful... > >Ops, seems like I cut & pasted it wrongly from my shell. Yes, >.../perl/libperl.a, of course. Will be fixed for mod_ssl 2.0.12. >Thanks for the feedback. Not only that. if the suggested (Ralf's) options are given to Makefile.PL *NO* perl directory is created under $APACHE_DIR/src/modules which is a Bad Thingie because the apache-make bails out after leaving src/modules/ssl and are about to enter src/modules/perl magnus bodin - still can't build mod_ssl + mod_perl http://x42.com/ __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: INSTALLING mod_perl + mod_ssl + extra modules?
Sorry for interfering in the middle of tarball-rolling; I'm in no hurry, but install-integration between mod_perl and mod_ssl ought to be easier. At 09:45 1998-09-21 +0200, Ralf S. Engelschall wrote: > > And here are the examples: > >$ gzip -d -c apache_1.3.x.tar.gz | tar xvf - >$ gzip -d -c mod_ssl-2.0.x-1.3.x.tar.gz | tar xvf - >$ gzip -d -c mod_perl-1.xx.tar.gz | tar xvf - >$ cd mod_ssl-2.0.x-1.3.x >$ ./configure > --with-apache=../apache_1.3.x >$ cd ../mod_perl-1.xx >$ perl Makefile.PL > EVERYTHING=1 > APACHE_SRC=../apache_1.3.x/src > USE_APACI=1 > PREP_HTTPD=1 > DO_HTTPD=1 >$ make >$ make install >$ cd ../apache_1.3.x >$ SSL_BASE=/path/to/ssleay > ./configure > --prefix=/path/to/apache > --enable-module=ssl > --activate-module=src/modules/perl > --enable-module=perl >$ make Everything went fine until mod_perl should compile. <=== src/modules/ssl ===> src/modules/perl make[4]: *** No rule to make target `libperl.', needed by `lib'. Stop. make[3]: *** [all] Error 1 something wrong with $(LIBEXT) ? I really like to have a more automated way to recompile a new httpd; Used my own lousy script below; Such ought to be included in some way. or a perl one. regards, magnus # makemyhttpd.sh YOU_ARE_HERE=/usr/local/www # # These dirs must be on the same level as this script MOD_SSLDIR=mod_ssl-2.0.9-1.3.1 MOD_PERLDIR=mod_perl-1.15_01 APACHEDIR=apache_1.3.1 # ssl-root # SSL_BASE=/usr/local/ssl cd $MOD_SSLDIR ./configure --with-apache=../$APACHEDIR cd ../$MOD_PERLDIR perl Makefile.PL EVERYTHING=1 APACHE_SRC=../$APACHEDIR USE_APACI=1\ PREP_HTTPD=1 DO_HTTPD=1 make sleep 5 make install sleep 5 cd ../$APACHEDIR ./configure --prefix=$YOU_ARE_HERE/$APACHEDIR\ --enable-module=ssl --activate-module=src/modules/perl --enable-module=perl make #make certificate #make install __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
INSTALLING mod_perl + mod_ssl + extra modules?
OK; this is very trivial; but the new APACI-interface and the lack of having control over module-order buzzes me off to ask this simple question: How do I (step by step) compile apache with both mod_ssl + mod_perl and + some extra module (in my case mod_auth_cookie.c) I have no problem with just mod_perl and mod_auth_cookie, as I can do the mod_perl thing first, then hand edit apache_1.3.1/Configuration; but with two (both mod_ssl and mod_perl) auto-script-modifiers I do have some problems. I also have no problem with just mod_ssl apaci-style. In what order do I do stuff? This ought to be a FAQ and be answered somewhere. /magnus http://åäö.x42.com __ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
