On Fri, Dec 04, 1998, Jake Buchholz wrote:

> > > > mod_ssl 2.1.x doesn't pick up the primary port number for the server
> > > > from the Listen directive the way 2.0.x appears to have done.  Using
> > > > the Port directive solves the problem, but I'm wondering if this may
> > > > have been an oversight.
> > > 
> > > Hmmm... no changes were made in this direction. So how do you know that the
> > > Port setting is not inherited?  What's the effect, i.e. where do you see that
> > > the port is not correct? And what particular config file are you using?
> > 
> > I'm using a custom set of heirarchical config files:
> 
> [snip]
> 
> I've confirmed that this behavior can be duplicated with the normal
> httpd.conf that's gets made from Apache + mod_ssl.  All you have to do
> is try using 'Listen 10.1.2.3:443' (substitute in the real IP, of course)
> instead of 'Listen 443' (which is in the /IfDefine) or it's alter-ego
> 'Port 443'.
> 
> > [info]  Init: 1st startup round (still not detached)
> > [info]  Init: Initializing SSLeay library
> > [info]  Init: Loading certificate & private key of SSL-aware server host:0
> >                                                                     ^^^^^^
> > [trace] Init: (host:0) unencrypted private key - pass phrase not required
> > [info]  Init: 2nd startup round (already detached)
> > [info]  Init: Initializing SSLeay library
> > [info]  Init: Generating temporary (512 bit) RSA private key
> > [info]  Init: Initializing (virtual) servers for SSL
> > [info]  Init: Configuring server host:0 for SSL protocol
> >                                  ^^^^^^             
> > [trace] Init: (host:443) Creating new SSL context
> > [trace] Init: (host:443) Configuring permitted SSL ciphers
> > [trace] Init: (host:443) Configuring server certificate
> > [error] Init: (host:443) Ops, can't find server certificate?!
> >                ^^^^^^^^
> >     It was saving the certificate and key in the table as host:0 and then
> >     trying to read it back later as host:443!
> > 
> >     I decided to take a gamble and add one line to my ssl.conf file right
> >     after my Listen directive: "Port 443".  Problem solved...

That's a really interesting problem. I've installed a fresh version with the
default config: works fine. I've now changed the "Listen 443" to "Listen
192.76.162.40:443" and it still works fine. In other words: I cannot reproduce
this problem on my box. You can send me your _exact_ and _complete_ server
config files (the ones you derived from the default config)? There has to be
still a subtle difference, I think.
                                       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]

Reply via email to