<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>The Microsoft policy is located here, as I’m sure you all know:<o:p></o:p></p><p class=MsoNormal><a href="http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx">http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>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?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Doug<o:p></o:p></p></div></body></html>