SHA1 deprecation strategy for signature algorithm
for SSL certificate and Code signing certificate, Microsoft has set a different schedule:
1, allWindowsTrusted Root Certification authorities(CA)from .years1Month1the date must cease to issue newSHA1Signature AlgorithmSSLCertificate and Code signing certificate;
2, forSSLcertificates,Windowswill be in .years1Month1stop support from daySHA1certificate. In other words: any previously issuedSHA1The certificate must be replaced withSHA2certificate;
3, for code signing certificates,Windowswill be in .years1Month1Day to stop accepting no time stampSHA1the signed code andSHA1certificate. In other words,Windowsstill accept in .years1Month1used before the daySAH1the signature has been addedRFC3161time-stamped code until Microsoft thought it might appearSHA1when attacking.
wosign (wosign) remind the general user :
· 1, Wosign(wosign)certificate Issuance system supports selecting when the user ordersSHA1or isSHA2certificate and issue the corresponding user certificate;
· 2, please select the majority of users carefullySHA2certificate, because at present our country still has more than -million user computers still not supportedSHA2Signature Algorithm(Windows XP SP2User);
3 , Wosign (wosign) will advance 3 months notice may be affected by a SHA1 certificate users are free to replace SHA2 certificate.
Microsoft will stop accepting SHA1 certificates for SSL and code signing