Operations » Editor » Public Comments

See also https://www.eugridpma.org/meetings/2015-05/summary-eugridpma-2015-05-copenhagen.txt which says:

SHA-2 implementation status
---------------------------
New developments and discussions like those held on the Mozilla NSS
bug tracker at https://bugzilla.mozilla.org/show_bug.cgi?id=1129083
have raised concerns about the long-term viability of SHA-512. Although
there are no current poignant issues, it may be advisable to
not use SHA-512 for new long-term choices, but instead use SHA-256
(or SHA-384 which is not specifically better but, it being included in
the TLS1.2 suite of digest functions is better supported).

We remind issuing authorities that
- it is now allowed and encouraged to issue SHA-2 familty CRLs
- for long lives CRLs (those issues by off-line Root CAs that are not
issuing CAs), it is RECOMMENDED to issue SHA-2 (sha256) CRLs now
- there are quite a few intermediate CAs still using SHA-1. These can
be re-issued with a new serial number (provided the end-entity EEC
certificates do not have an explicit serialNumber in their authorityKeyID)
Registration is through your PMA chair or trusted registrar

and when you are at it, new CAs should probably start using 4096-RSA bit
key pairs and sha-256 for longevity and compatibility.

Summarizing the Bratislava CAOPS consensus:
Updated guidance to that at least SHA-256 MUST be used, and added footnote to refer to MS KB 2973337 on SHA-51 support.