<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Chris – a serious question. Is it true that
<span class="apple-converted-space"><span style="background:white"> </span></span><a href="http://google.com/" target="_blank"><span style="color:windowtext;border:none windowtext 1.0pt;padding:0in;background:white;text-decoration:none">google.com</span></a><span class="apple-converted-space"><span style="background:white"> </span></span><span style="background:white">is
still using <span style="color:#222222">SHA-1 in both end-entity and intermediate certificates today (as has been posted to this site)? If so, how can Google be so condemning of ordinary websites that are also using SHA-1 certs today, even though there has
been discussion of SHA-1’s potential weakness, as you say, for several years?<o:p></o:p></span></span></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#222222;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#222222;background:white">So many of the postings on this topics have shown a strong antipathy toward CAs – toward ALL CAs, without making any distinctions. Google
is painting everyone with the same brush. How can we turn this around, and create a more collaborative environment among browsers, browser users, CAs, website owners?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#222222;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#222222;background:white">Google’s current policy will be creating a kind of chaos for many website owners in the next few weeks who have no idea why this is happening.
It will be affecting websites that have already started transition plans to SHA-256 certs before 2017. Isn’t there a better way?</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> security-dev@chromium.org [mailto:security-dev@chromium.org]
<br>
<b>Sent:</b> Thursday, August 28, 2014 9:54 PM<br>
<b>To:</b> Jeremy Rowley<br>
<b>Cc:</b> blink-dev; security-dev; rsleevi; net-dev<br>
<b>Subject:</b> Re: Intent to Deprecate: SHA-1 certificates<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><br>
> Only if one ignores fairly clear statements from 6 months ago. Keep in mind that it's already 12 *years* after we've known from public literature that SHA-1 is significantly weaker than its designed guarantee.<o:p></o:p></p>
<p>Oops, 9 years now; 12 years in 2017. Sorry about that.<o:p></o:p></p>
<p class="MsoNormal">To unsubscribe from this group and stop receiving emails from it, send an email to
<a href="mailto:security-dev+unsubscribe@chromium.org">security-dev+unsubscribe@chromium.org</a>.<o:p></o:p></p>
</div>
</body>
</html>
<table><tr><td bgcolor=#ffffff><font color=#000000><pre><table class="TM_EMAIL_NOTICE"><tr><td><pre>
TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential
and may be subject to copyright or other intellectual property protection.
If you are not the intended recipient, you are not authorized to use or
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.
</pre></td></tr></table></pre></font></td></tr></table>