[cabfpub] Guidance on Microsoft SHA1 Deprecation Policy

[Doug Beattie]

The Microsoft policy is located here, as I'm sure you all know:

http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.as
px

 

The policy clearly states the scope of this policy is for SSL and Code
Signing, but I wanted to validate that this is in-fact the entire set of
users which will be impacted in 2017.

 

While not clear in the blog, in side discussions it became evident that that
all CAs in the hierarchy of an SSL or Code Signing certificate (except the
root) must also be SHA2.  This makes sense even if not explicitly stated (it
should be stated at some point).  This means legacy SHA1 Intermediates
cannot be used to sign subordinate SHA2 CAs and be trusted in 2017 for SSL
and Code Signing certificates.  

 

I wanted for inquire about personal certificates used for secure mail,
client authentication to web sites (including Microsoft web servers),
document signing (outside of Adobe), file encryption, etc.  Will SHA1
certificates and CA hierarchies continue to be trusted by Microsoft within
these applications, or is Microsoft rolling out new validation logic
globally for all certificates?

 

Doug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/public/attachments/20140122/343a513f/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4287 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/public/attachments/20140122/343a513f/attachment.p7s>