Closed
Bug 1142257
Opened 9 years ago
Closed 2 years ago
JSS test suite failing after NSS changed default to maximum TLS 1.2
Categories
(JSS Graveyard :: Library, defect)
JSS Graveyard
Library
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: KaiE, Assigned: cfu, NeedInfo)
Details
See test.nss-crypto.org, the right hand side of the machines, which are testing JSS, are failing.
Reporter | ||
Comment 1•9 years ago
|
||
These are the ciphers that fail in JSS since TLS 1.2 was enabled by default: - SSL3_RSA_EXPORT_WITH_RC4_40_MD5 (f) - SSL3_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (g)
Reporter | ||
Comment 2•9 years ago
|
||
Christina, could you please check in a fix to JSS that will either disable testing these cipher suites, or some other mitigation to stop the test failures on our http://test.nss-crypto.org continuous integration system? Thank you.
Flags: needinfo?(cfu)
Reporter | ||
Comment 3•9 years ago
|
||
I checked in this change as an attempt to hide the bustage until you can work on a better patch. https://hg.mozilla.org/projects/jss/rev/81f59272b025
Reporter | ||
Comment 4•9 years ago
|
||
That didn't work...
Reporter | ||
Comment 5•9 years ago
|
||
(In reply to Kai Engert (:kaie) from comment #4) > That didn't work... backed out: https://hg.mozilla.org/projects/jss/rev/cc25ef5f2aca
Comment 6•2 years ago
|
||
JSS development has moved from the Mozilla community to the Dogtag PKI community. Please re-file this bug at https://github.com/dogtagpki/jss if it is still relevant. Thank you!
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•