Dan Nicholson wrote these words on 06/03/06 17:23 CST: > On 6/3/06, rblythe <[EMAIL PROTECTED]> wrote: >> CRL SSL Client Tests >> Test Case Result >> Wait for Server Failed >> [snip others] >> This is just a small sampling taken from various places in the log >> file. The errors encompass TLS SSL2 and SSL3 and have the same types of >> failures in each category of the log file. > > Hmm. Well, I really don't know, although that doesn't look good. To > be honest, I've never run the testsuite, and NSS works fine for me. > And I do use both the SSL and TLS functionalities between Firefox and > Thunderbird. If you want specific answers about the testsuite, you'll > have to wait for Randy to reply.
I cannot explain the errors as I've never seen anything remotely close to what rblythe is showing. The tests have *always* run successfully every time I've ran them. Is the domain name used in the tests identified in the /etc/hosts file? Here is a sample entry for an /etc/hosts file where the NSS tests run perfectly. 127.0.0.1 localhost.localdomain localhost 192.168.0.232 rmlscsi.mcmurchy.prv rmlscsi scsi and this is what is in my NSS build script: export DOMSUF=mcmurchy.prv With this combination (and a similar setup on many other machines), the test always run without a hitch. > Beats me. It would seem to me that the test suite is buggy, but Randy > might be able to shed some light on the subject. I think it is more that the DOMSUF var is not being set with a *valid* domain name. But that is just a guess. -- Randy rmlscsi: [bogomips 1003.27] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 08:51:00 up 23 days, 51 min, 1 user, load average: 0.21, 0.14, 0.08 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
