Closed
Bug 448474
Opened 18 years ago
Closed 17 years ago
OCSP Interoperability tests failing frequently on branch Tinderbox
Categories
(NSS :: Test, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 404874
People
(Reporter: nelson, Unassigned)
Details
In the last 24 hours or so, we've had 4 tinderbox test failures.
All fail in the same place (see log excerpt below).
They all claim that the test OCSP responder rejected NSS's OCSP request
for having been improperly formed.
We really need to get to the bottom of this.
TIMESTAMP ocsp BEGIN: Tue Jul 29 13:15:11 PDT 2008
ocsp.sh: OCSP tests ===============================
Testing ocsp interoperability.
Client: local(tstclnt).
Responder: remote(dochinups.red.iplanet.com)
ocsp.sh: OCSP testing with responder at dochinups.red.iplanet.com. <br> Test Type: CA key is used to sign OCSP response ===============================
ocspclnt -d /export/tinderbox/Linux_2.6.9-42.ELsmp/mozilla/tests_results/security/touquet.2/client_ocsp_iopr_dochinups.red.iplanet.com -S ocspRCATestUser518-rsa
ocspclnt output:
Check of certificate "ocspRCATestUser518-rsa" failed. Reason:
The OCSP server found the request to be corrupted or improperly formed.
ocsp.sh: Getting status of a valid cert (ocspRCATestUser518-rsa) produced a returncode of 1, expected is 0. FAILED
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•