Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 4247 invoked by uid 500); 12 Oct 2001 05:06:34 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 4235 invoked from network); 12 Oct 2001 05:06:34 -0000 Date: Thu, 11 Oct 2001 22:06:18 -0700 From: Justin Erenkrantz To: dev@httpd.apache.org Subject: Re: Apache 2.0 and SSL (TLS) Message-ID: <20011011220618.A2149@ebuilt.com> References: <20011011184339.X23667@ebuilt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i X-AntiVirus: scanned for viruses by AMaViS 0.2.1-pre3 (http://amavis.org/) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, Oct 11, 2001 at 07:41:01PM -0700, Doug MacEachern wrote: > On Thu, 11 Oct 2001, Justin Erenkrantz wrote: > > > What test is it failing on? I tested it with httpd-test when I > > committed it and it passed. > > do you have Crypt::SSLeay installed? otherwise t/ssl tests are skipped. > and you need to explicitly pass the '-ssl' switch for t/TEST to run all > the other tests over ssl. > anyhow, everything segvs running though ssl, 3 different stacktraces > below... Yeah, I did, but I changed the offending section of code after I ran the test. Oh, well. I just made a commit that should have fixed that. Here's what I'm getting now: Failed Test Status Wstat Total Fail Failed List of Failed -------------------------------------------------------------------------------- modules/negotiation.t 98 44 44.90% 1-2, 6-7, 11-12, 16-17, 21-22, 24-25, 29-30, 34- 35, 39-40, 44-45, 47-48, 52-53, 57-58, 62-63, 67- 68, 70-71, 75-76, 80-81, 85-86, 90-91, 93, 95-96, 98 ssl/basicauth.t 3 2 66.67% 2-3 ssl/env.t 9 2304 22 11 50.00% 12-22 ssl/require.t 5 2 40.00% 2, 5 ssl/varlookup.t 5 5 100.00% 1-5 ssl/verify.t 3 1 33.33% 2 4 tests skipped. I'll try to take a look at the ssl-specific tests, but all of the tests were run over SSL (and passed), so I think the input filtering works. Perhaps something else is broken? -- justin