NSS:CompletedFromBurnDownList: Difference between revisions

no edit summary
mNo edit summary
No edit summary
Line 36: Line 36:
* {{bug|738457}} - PSM change for new error code.
* {{bug|738457}} - PSM change for new error code.
* [https://wiki.mozilla.org/CA:MD5and1024 This is something that we said we would do,] and required all CAs to move their customers from MD5 by June 30, 2011. Chrome turned off MD5 support in early 2012, and found that there are still some old network products that have not updated their certs, so companies need to be able to set a preference to enable MD5 until they can get those upgraded. Wan-Teh said that the concern he raised a few years ago about there being too many MD5 intermediate certs is no longer the case.  
* [https://wiki.mozilla.org/CA:MD5and1024 This is something that we said we would do,] and required all CAs to move their customers from MD5 by June 30, 2011. Chrome turned off MD5 support in early 2012, and found that there are still some old network products that have not updated their certs, so companies need to be able to set a preference to enable MD5 until they can get those upgraded. Wan-Teh said that the concern he raised a few years ago about there being too many MD5 intermediate certs is no longer the case.  
</tr>
<tr>
  <td>P5 PSM</td>
  <td>Auto-Update of CRLs not working with DD.MM.YYYY date locale</td>
  <td>{{bug|682244}}</td>
  <td></td>
  <td>FF14</td>
  <td>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.</td>
</tr>
</tr>


Confirmed users, Administrators
5,526

edits