Yes, you were right. I found this out when I was examining the log
this morning. I put a fix so that the pass phase will be asked only
once and get passed to the child.
I am also interested in your fix, but searched the archieve without
success. Can you point me to it directly?
Thanks!
Andrew
----- Original Message -----
From: "Kirk Benson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 02, 2000 2:01 PM
Subject: RE: Connection to mod_ssl 2.7.1 blocked on WinNT
> This may be the same problem for which I submitted a fix several months
ago.
> Since the problem was in the Apache code and not mod_ssl, Ralf can't fix
it
> in mod_ssl releases.
>
> You can check the list archive for the fix, which has two parts:
>
> a) don't prompt for the passphrase in the parent process unless the -X
> parameter is set; this is because mod_ssl is not invoked by the parent in
a
> 2-process runmode.
>
> b) correctly propagate STDOUT/STDIN/STDERR to the child process so that
the
> passphrase prompt is visible in the apache console window. The child
> process is in fact prompting for the passphrase, but because it does not
> inherit the handles, the prompt isn't displayed.
>
> One way to verify that this is in fact the problem is to run apache, enter
> the passphrase on the initial prompt, and then enter it again "blind"
> several seconds later.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David Rees
> Sent: Thursday, November 02, 2000 3:03 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Connection to mod_ssl 2.7.1 blocked on WinNT
>
>
> Wasn't there some bugs related to the NT version in the latest release?
>
> You might want to try the last CVS snapshot.
>
> -Dave
>
> > I've seen this behavior too. Do you have a pass phrase enabled on
> > the key? I
> > did and when I stripped the pass phrase out of the key, I was
> > able to get the
> > server started OK. Haven't figure out much more yet.
> >
> > Hope that helps,
> > Bruce
> >
> > "Andrew C. Wong" wrote:
> >
> > > Hi,
> > >
> > > I just have the latest and greatest Apache1.3.14 + mod_ssl2.7.1
> > > compiled on NT 4.0. It worked fine without loading SSL module.
> > >
> > > However, when SSL was enabled, it worked only if -X was specified
> > > on command line. Otherwise, any HTTP or HTTPS connection to it
> > > would be blocked and never return. The forked child seemed getting
> > > into a funny state.
> > >
> > > Any idea?
> > >
> > > Thanks!
> > > Andrew
> > > ---------------------------------------
> > > CONNECTED(00000004)
> > > SSL_connect:before/connect initialization
> > > write to 0017F0C0 [00181788] (130 bytes => 130 (0x82))
> > > 0000 - 80 80 01 03 01 00 57 00-00 00 20 00 00 16 00 00
> > ......W... .....
> > > 0010 - 13 00 00 0a 07 00 c0 00-00 66 00 00 07 00 00 05
> > .........f......
> > > 0020 - 00 00 04 05 00 80 03 00-80 01 00 80 08 00 80 00
> > ................
> > > 0030 - 00 65 00 00 64 00 00 63-00 00 62 00 00 61 00 00
> > .e..d..c..b..a..
> > > 0040 - 60 00 00 15 00 00 12 00-00 09 06 00 40 00 00 14
> > `...........@...
> > > 0050 - 00 00 11 00 00 08 00 00-06 00 00 03 04 00 80 02
> > ................
> > > 0060 - 00 80 f5 6a 27 fa 37 f1-15 4c aa 7e 48 c7 11 74
> > ...j'.7..L.~H..t
> > > 0070 - cb f8 10 b2 61 8a be a8-35 d3 9e 77 a2 45 56 b8
> > ....a...5..w.EV.
> > > 0080 - 72 ce r.
> > > SSL_connect:SSLv2/v3 write client hello A
> > > <<< blocked >>>
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
> ______________________________________________________________________
> Apache Interface to OpenSSL (mod_ssl) www.modssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
