On 6/3/06, rblythe <[EMAIL PROTECTED]> wrote:
CRL SSL Client Tests Test Case Result Wait for Server Failed TLS Request don't require client auth (client does not provide auth) (cert TestUser40 - revoked) Failed Wait for Server Failed TLS Require client auth (bad password) (cert TestUser40 - revoked) Failed Wait for Server Failed SSL3 Request don't require client auth (client does not provide auth) (cert TestUser40 - revoked) Failed Wait for Server Failed Wait for Server Failed SSL2 RC4 128 WITH MD5 Failed SSL2 RC4 128 EXPORT40 WITH MD5 Failed SSL2 RC2 128 CBC WITH MD5 Failed SSL3 RSA WITH DES CBC SHA Failed SSL3 RSA EXPORT WITH RC4 40 MD5 Failed SSL3 RSA EXPORT WITH RC2 CBC 40 MD5 Failed 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. He wrote those instructions, and he always runs testsuites if they're available.
when I use DOMSUF=blytheworks.example.org I end up with 346 not 770. when I use DOMSUF= (blank) I end up with 346. When I use any other value in DOMSUF I get 346 (the exceptions was DOMSUF=mydoman.com, That yielded only 220). Only DOMSUF=example.org freezes. When I use DOMSUF=example.org. (that is an extra . at the end) I get 346 not 770.
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. If you're not that concerned, just move on for now. You can always keep the source directory around and test some more later. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
