-==-=-=---=---==-==---==--=-==--=--==-
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
At 03:18 PM 3/10/2002 +0100, you wrote:
On Sun, Mar 10, 2002 at 09:04:04AM +0100, [EMAIL PROTECTED] wrote:
> Full_Name: Ari D Jordon
> Version: 2.8.7
> OS: Solaris 2
On Sun, Mar 10, 2002 at 11:30:29AM -0500, R. DuFresne wrote:
>
> So the engin version should be compatible with the non-engine version
> unless there has been something I have missed in the list here or
> elsewhere?
>
It probably is - I just haven't seen that error before, so it was an
obvious p
Hi,
On Monday 11 March 2002 03:18, [EMAIL PROTECTED] wrote:
> Are you using the engine version of openssl? Unless you have a supported
> crypto accelerator, then you shouldn't be using the engine version.
I can assure you that it should make no difference. The only reason the
non-engine version
On Sun, 10 Mar 2002 [EMAIL PROTECTED] wrote:
> On Sun, Mar 10, 2002 at 09:04:04AM +0100, [EMAIL PROTECTED] wrote:
> > Full_Name: Ari D Jordon
> > Version: 2.8.7
> > OS: Solaris 2.8
> > Submission from: (NULL) (68.49.144.213)
> >
> >
> > using apache 1.3.23, starting httpd with -DSSL immediately
On Sun, Mar 10, 2002 at 09:04:04AM +0100, [EMAIL PROTECTED] wrote:
> Full_Name: Ari D Jordon
> Version: 2.8.7
> OS: Solaris 2.8
> Submission from: (NULL) (68.49.144.213)
>
>
> using apache 1.3.23, starting httpd with -DSSL immediately seg faults. post
> mortem revealed it was dying in ssl_cmd_S
Full_Name: Ari D Jordon
Version: 2.8.7
OS: Solaris 2.8
Submission from: (NULL) (68.49.144.213)
using apache 1.3.23, starting httpd with -DSSL immediately seg faults. post
mortem revealed it was dying in ssl_cmd_SSLEngine, specifically in that
mySrvConfig() was returning 0. not quite sure if th
