<story><title>Chrome Requiring Certificate Transparency in 2017</title><url>https://groups.google.com/a/chromium.org/forum/#!msg/ct-policy/78N3SMcqUGw/ykIwHXuqAQAJ</url></story><parent_chain></parent_chain><comment><author>rfugger</author><text>For those wondering what Certificate Transparency is:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.certificate-transparency.org&amp;#x2F;what-is-ct&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.certificate-transparency.org&amp;#x2F;what-is-ct&lt;/a&gt;</text></comment>
<story><title>Chrome Requiring Certificate Transparency in 2017</title><url>https://groups.google.com/a/chromium.org/forum/#!msg/ct-policy/78N3SMcqUGw/ykIwHXuqAQAJ</url></story><parent_chain></parent_chain><comment><author>mcpherrinm</author><text>This is very cool.  CT is a good step in monitoring for CA misbehavior. My employer&amp;#x27;s users can be target of phishing attacks, so having all TLS certs in CT is a great source of data to detect phishing sites earlier.&lt;p&gt;I wonder how this will work for &amp;quot;internal&amp;quot; domains issued off a private CA, though.  Will this be enforced by chrome, or is this just a CA&amp;#x2F;B rule?</text></comment>