NSS:CompletedFromBurnDownList
From MozillaWiki
Completed from Burn Down List
This page lists items that have been completed that were being tracked in the SSL Burn Down List.
Pr | Enhancement | Related Bugs | Dependencies | Release | Notes |
---|---|---|---|---|---|
P3 NSS | Support OCSP GET | bug 436414 | Automated tests, OCSP server in NSS test tools | NSS 3.15.3 | GET and POST are two alternative transfer mechanisms used with HTTP, and only GET can be cached, but currently NSS only supports POST.
|
P2 NSS | Implement TLS 1.2 | bug 480514 | See bug | NSS 3.15.1 | bug 861266 - Implement TLS 1.2 (RFC 5246) in Gecko (Firefox, Thunderbird), on by default. bug 707275 - Implement SSL certificate and cipher suite telemetry. |
P2 NSS | NSS Testing
|
This is important to avoid regressions in the NSS software component. In moving to libpkix we will need to make sure our testing is as complete as possible so that we don't regress anything when we fix bugs requiring tricky changes to libpkix. Our current automated NSS testing may not be insufficient, because a lot of configuration was hidden on computers run by Sun/Oracle. | |||
P3 PSM | PSM changes and tests to support OCSP stapling | bug 700693 | Mozilla27 | Postponed from Firefox 25 due to bug 929617. | |
P3 NSS | Improve OCSP testing | bug 811317, bug 663733 | 3.14.1 | Needed to test OCSP response handling in general, and OCSP stapling in particular.
|
|
Migrate NSS from CVS to Mercurial | bug 844385 | Test Repositories created. Request that everyone land changes into both CVS and Mercurial/HG for now. | |||
P3* NSS | Implement OCSP stapling | bug 360420 | bug 663733 | NSS 3.14.4 | bug 700693 - PSM preference to have OCSP stapling off by default. |
P2 NSS | Implement TLS 1.1 | bug 565047 | See bug | NSS 3.14 | Blocks DTLS, which blocks WebRTC. NSS part needs to be landed. PSM part can be deferred, bug 733647 to have Firefox use this. |
P1* PSM/Gecko | Implement mechanism to prevent sending insecure requests from a secure context | bug 62178 | See bug | FF 18 | Determine whether showing security indicators in Firefox is really deserved. It's not deserved if a page loads insecure content. By default we shouldn't load such content, because it can leak authentication cookies, allow cross-site scripting attacks, etc. |
P1 PSM | Fix SSL error handling regressions | bug 783974 | FF17 |
|
|
P1 NSS | Cannot validate valid certificate chain when looping/cross-signed certs are involved | bug 634074, bug 764393 | FF 15, 16, 17 |
|
|
P2 NSS PSM | Disable MD5 Signatures | bug 650355, bug 590364 | bug 758314, bug 732390 | FF16 |
|
P5 PSM | Auto-Update of CRLs not working with DD.MM.YYYY date locale | bug 682244 | FF14 | The entire automatic fetching of CRLs in PSM is completely broken and an ugly old workaround. Let's get libPKIX done (651246), which will give us automatic fetching of CRL. Once done, we can remove the auto-update CRL feature. | |
P1 NSS | Generic blacklisting mechanism | bug 470994, bug 727204, bug 642503 | NSS 3.13.3 | We can now block cert by issuer and serial number in NSS, and the Trustwave subCA certs have been added to this list. Any branch that desires this blocking ability will have to upgrade to a newer NSS release with this bug fixed, which will be NSS 3.13.3 at the earliest. | |
P1 NSS PSM | Something in networking and/or SSL layer takes lots of processing power | bug 710176 | FF 11 | Regression from landing SSL thread removal, probably | |