<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [Action Required] Review hostname exemptions requirements for TLS inspection for ChromeOS starti in Peer-Peer Topics</title>
    <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2177#M1705</link>
    <description>&lt;P&gt;&lt;STRONG&gt;So, the solution is to &lt;EM&gt;NOT&lt;/EM&gt; do TLS Inspection&lt;/STRONG&gt;&amp;nbsp;of the hosts listed in the article.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jan 2024 14:49:28 GMT</pubDate>
    <dc:creator>Kim_Nilsson</dc:creator>
    <dc:date>2024-01-18T14:49:28Z</dc:date>
    <item>
      <title>[Action Required] Review hostname exemptions requirements for TLS inspection for ChromeOS starting F</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2174#M1702</link>
      <description>&lt;P&gt;Can anyone tell me more about this email (assuming others have gotten it)?&amp;nbsp; I am not sure what exactly it is for or what we have to do.&amp;nbsp; Do we need to add the addresses to our filter exclusion list so they bypass filtering?&amp;nbsp; The link brings you to a page that has a bunch of steps, adding certificates to devices, etc.&amp;nbsp; Does anyone have more information on this?&amp;nbsp; reading through everything I think I am beginning to understand it, but right now I feel like I know just enough to be dangerous&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":face_with_rolling_eyes:"&gt;🙄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 14:23:29 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2174#M1702</guid>
      <dc:creator>panderson</dc:creator>
      <dc:date>2024-01-18T14:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: [Action Required] Review hostname exemptions requirements for TLS inspection for ChromeOS starti</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2175#M1703</link>
      <description>&lt;P&gt;Link:&amp;nbsp;&lt;A href="https://support.google.com/chrome/a/answer/6334001" target="_blank"&gt;https://support.google.com/chrome/a/answer/6334001&lt;/A&gt;&lt;BR /&gt;E-Mail:&lt;/P&gt;&lt;P&gt;Dear EDU Administrator,&lt;/P&gt;&lt;P&gt;We are writing to let you know that starting&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;February 2024&lt;/STRONG&gt;, managed users may be unable to log-in to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;ChromeOS&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;within your network following an upgrade to our sign-in infrastructure, unless you allowlist relevant hostnames.&lt;/P&gt;&lt;H3&gt;What does this mean for your organization?&lt;/H3&gt;&lt;P&gt;For users to work on&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;ChromeOS devices&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in an enterprise network environment that utilizes TLS inspection (also known as SSL inspection), some hostnames need to be exempt from inspection, as explained in this&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://notifications.google.com/g/p/ANiao5oXXFycVLkgaAiGt2cXKuuSZz4sHYpj5BrZbcR7Y_ck75BkdlFwh3TS92sE3xhfHu9GVjjECiNYa88o0Y4LhFJwiZHaSY2RRZYGZLkCuEcjrtS66T2LTzUON7dmsPwwFUKxHCLqGBSTVHkJAnEJpKwdtlNjx2VRVGtXk5ADrkSrBojgplKpqIYsJPWJCLirsqePKFf3FQ7_EjQgPvzhF-qH22s_sYPc1mAhIERCiexD" target="_blank" rel="noopener"&gt;support article&lt;/A&gt;.&lt;/P&gt;&lt;H3&gt;What do you need to do?&lt;/H3&gt;&lt;P&gt;&lt;STRONG&gt;Review and confirm&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A rel="nofollow" target="_blank"&gt;www.gstatic.com&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A rel="nofollow" target="_blank"&gt;ssl.gstatic.com&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;are allowed in your enterprise network and exempt from TLS inspection. If these hostnames are not allowlisted, users may be unable to sign-in to their Chromebooks when connected to your enterprise network.&lt;/P&gt;&lt;P&gt;On&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;February 16, 2024&lt;/STRONG&gt;, the Google Team will begin an infrastructure migration that would require these hostnames.&lt;/P&gt;&lt;P&gt;Thanks for choosing Google for Education.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;– The Google Chrome Team&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 14:45:48 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2175#M1703</guid>
      <dc:creator>Bill_Gibson</dc:creator>
      <dc:date>2024-01-18T14:45:48Z</dc:date>
    </item>
    <item>
      <title>Re: [Action Required] Review hostname exemptions requirements for TLS inspection for ChromeOS starti</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2176#M1704</link>
      <description>&lt;P&gt;Talk to your network admin.&lt;/P&gt;&lt;P&gt;If your firewall does TLS Inspection, then you need to exclude ALL Google's addresses listed in the support article.&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.google.com/chrome/a/answer/6334001" target="_blank"&gt;https://support.google.com/chrome/a/answer/6334001&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 14:48:41 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2176#M1704</guid>
      <dc:creator>Kim_Nilsson</dc:creator>
      <dc:date>2024-01-18T14:48:41Z</dc:date>
    </item>
    <item>
      <title>Re: [Action Required] Review hostname exemptions requirements for TLS inspection for ChromeOS starti</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2177#M1705</link>
      <description>&lt;P&gt;&lt;STRONG&gt;So, the solution is to &lt;EM&gt;NOT&lt;/EM&gt; do TLS Inspection&lt;/STRONG&gt;&amp;nbsp;of the hosts listed in the article.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 14:49:28 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2177#M1705</guid>
      <dc:creator>Kim_Nilsson</dc:creator>
      <dc:date>2024-01-18T14:49:28Z</dc:date>
    </item>
    <item>
      <title>Re: [Action Required] Review hostname exemptions requirements for TLS inspection for ChromeOS starti</title>
      <link>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2178#M1706</link>
      <description>&lt;P&gt;Yea, this is the email that was confusing me.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 15:06:21 GMT</pubDate>
      <guid>https://www.googleforeducommunity.com/t5/Peer-Peer-Topics/Action-Required-Review-hostname-exemptions-requirements-for-TLS/m-p/2178#M1706</guid>
      <dc:creator>panderson</dc:creator>
      <dc:date>2024-01-18T15:06:21Z</dc:date>
    </item>
  </channel>
</rss>

