<?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: SSL Inspection for Chromebooks in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/312169#M80740</link>
    <description>&lt;P&gt;HI Mr. Bbilut,&lt;/P&gt;&lt;DIV class="lia-message-author-rank lia-component-author-rank lia-component-message-view-widget-author-rank"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm also having this issues with my chrome book.Is it this solution works for you..If its work, can you guide me how to whitelisted all the hostname whitelist for all chrome device? I'm still a new in Paloalto Firewall.. My chrome book also managed by organization for your information&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Host name whitelist for all Chrome devices&lt;/P&gt;&lt;P&gt;accounts.google.com&lt;BR /&gt;accounts.gstatic.com&lt;BR /&gt;accounts.youtube.com&lt;BR /&gt;clients1.google.com&lt;BR /&gt;clients2.google.com&lt;BR /&gt;clients3.google.com&lt;BR /&gt;clients4.google.com&lt;BR /&gt;commondatastorage.googleapis.com&lt;BR /&gt;cros-omahaproxy.appspot.com&lt;BR /&gt;dl.google.com&lt;BR /&gt;dl-ssl.google.com&lt;BR /&gt;gweb-gettingstartedguide.appspot.com&lt;BR /&gt;m.google.com&lt;BR /&gt;omahaproxy.appspot.com&lt;BR /&gt;pack.google.com&lt;BR /&gt;safebrowsing-cache.google.com&lt;BR /&gt;safebrowsing.google.com&lt;BR /&gt;ssl.gstatic.com&lt;BR /&gt;storage.googleapis.com&lt;BR /&gt;tools.google.com&lt;BR /&gt;&lt;A href="http://www.googleapis.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;www.googleapis.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.gstatic.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;www.gstatic.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Host name whitelist for single-app kiosk devices&lt;/P&gt;&lt;P&gt;If you use single-app kiosk devices, whitelist the following host names in addition to the host names listed above:&lt;/P&gt;&lt;P&gt;cache.pack.google.com&lt;BR /&gt;chrome.google.com&lt;BR /&gt;clients2.googleusercontent.com&lt;BR /&gt;lh3.ggpht.com&lt;BR /&gt;lh4.ggpht.com&lt;BR /&gt;lh5.ggpht.com&lt;BR /&gt;lh6.ggpht.com&lt;/P&gt;</description>
    <pubDate>Thu, 20 Feb 2020 08:15:13 GMT</pubDate>
    <dc:creator>syafeera90</dc:creator>
    <dc:date>2020-02-20T08:15:13Z</dc:date>
    <item>
      <title>SSL Inspection for Chromebooks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/77053#M42513</link>
      <description>&lt;P&gt;I was having some trouble with SSL decryption on my chromebooks and after a bit of Google searching I came across this Google article and I wanted to share with others since there was nothing like this in the community. If I didn't exclude these when my chromebook booted I would just end up with a blank box and you could not login or anything. You only option was to power off. This fixed my problems.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.google.com/chrome/a/answer/6334001" target="_self"&gt;https://support.google.com/chrome/a/answer/6334001&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For Chrome devices to work on a domain with SSL inspection, some host names need to be exempt from inspection. This is because certificates can only be imported at the user level and are only honored for user-level traffic. Some device-level traffic doesn’t use the SSL certificate to protect users against certain kinds of security risks.&lt;/P&gt;
&lt;P&gt;To ensure that Chrome devices work with SSL inspection, you need to whitelist the following host names on your proxy server. For details on how to whitelist host names, check with your web filter provider.&lt;/P&gt;
&lt;H3&gt;Updates&lt;/H3&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;STRONG&gt;Dec 2 2015:&lt;/STRONG&gt; Added host names to whitelist for single-app kiosk devices.&lt;/LI&gt;
&lt;LI&gt;&lt;STRONG&gt;Aug 5 2015:&lt;/STRONG&gt; Added accounts.gstatic.com.&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;Host name whitelist for all Chrome devices&lt;/H3&gt;
&lt;P&gt;accounts.google.com&lt;BR /&gt;accounts.gstatic.com&lt;BR /&gt;accounts.youtube.com&lt;BR /&gt;clients1.google.com&lt;BR /&gt;clients2.google.com&lt;BR /&gt;clients3.google.com&lt;BR /&gt;clients4.google.com&lt;BR /&gt;commondatastorage.googleapis.com&lt;BR /&gt;cros-omahaproxy.appspot.com&lt;BR /&gt;dl.google.com&lt;BR /&gt;dl-ssl.google.com&lt;BR /&gt;gweb-gettingstartedguide.appspot.com&lt;BR /&gt;m.google.com&lt;BR /&gt;omahaproxy.appspot.com&lt;BR /&gt;pack.google.com&lt;BR /&gt;safebrowsing-cache.google.com&lt;BR /&gt;safebrowsing.google.com&lt;BR /&gt;ssl.gstatic.com&lt;BR /&gt;storage.googleapis.com&lt;BR /&gt;tools.google.com&lt;BR /&gt;&lt;A href="http://www.googleapis.com" target="_blank"&gt;www.googleapis.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.gstatic.com" target="_blank"&gt;www.gstatic.com&lt;/A&gt;&lt;/P&gt;
&lt;H3&gt;Host name whitelist for single-app kiosk devices&lt;/H3&gt;
&lt;P&gt;If you use single-app kiosk devices, whitelist the following host names in addition to the host names listed above:&lt;/P&gt;
&lt;P&gt;cache.pack.google.com&lt;BR /&gt;chrome.google.com&lt;BR /&gt;clients2.googleusercontent.com&lt;BR /&gt;lh3.ggpht.com&lt;BR /&gt;lh4.ggpht.com&lt;BR /&gt;lh5.ggpht.com&lt;BR /&gt;lh6.ggpht.com&lt;/P&gt;</description>
      <pubDate>Tue, 26 Apr 2016 14:27:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/77053#M42513</guid>
      <dc:creator>bbilut</dc:creator>
      <dc:date>2016-04-26T14:27:38Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Inspection for Chromebooks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/312169#M80740</link>
      <description>&lt;P&gt;HI Mr. Bbilut,&lt;/P&gt;&lt;DIV class="lia-message-author-rank lia-component-author-rank lia-component-message-view-widget-author-rank"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm also having this issues with my chrome book.Is it this solution works for you..If its work, can you guide me how to whitelisted all the hostname whitelist for all chrome device? I'm still a new in Paloalto Firewall.. My chrome book also managed by organization for your information&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Host name whitelist for all Chrome devices&lt;/P&gt;&lt;P&gt;accounts.google.com&lt;BR /&gt;accounts.gstatic.com&lt;BR /&gt;accounts.youtube.com&lt;BR /&gt;clients1.google.com&lt;BR /&gt;clients2.google.com&lt;BR /&gt;clients3.google.com&lt;BR /&gt;clients4.google.com&lt;BR /&gt;commondatastorage.googleapis.com&lt;BR /&gt;cros-omahaproxy.appspot.com&lt;BR /&gt;dl.google.com&lt;BR /&gt;dl-ssl.google.com&lt;BR /&gt;gweb-gettingstartedguide.appspot.com&lt;BR /&gt;m.google.com&lt;BR /&gt;omahaproxy.appspot.com&lt;BR /&gt;pack.google.com&lt;BR /&gt;safebrowsing-cache.google.com&lt;BR /&gt;safebrowsing.google.com&lt;BR /&gt;ssl.gstatic.com&lt;BR /&gt;storage.googleapis.com&lt;BR /&gt;tools.google.com&lt;BR /&gt;&lt;A href="http://www.googleapis.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;www.googleapis.com&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://www.gstatic.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;www.gstatic.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Host name whitelist for single-app kiosk devices&lt;/P&gt;&lt;P&gt;If you use single-app kiosk devices, whitelist the following host names in addition to the host names listed above:&lt;/P&gt;&lt;P&gt;cache.pack.google.com&lt;BR /&gt;chrome.google.com&lt;BR /&gt;clients2.googleusercontent.com&lt;BR /&gt;lh3.ggpht.com&lt;BR /&gt;lh4.ggpht.com&lt;BR /&gt;lh5.ggpht.com&lt;BR /&gt;lh6.ggpht.com&lt;/P&gt;</description>
      <pubDate>Thu, 20 Feb 2020 08:15:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/312169#M80740</guid>
      <dc:creator>syafeera90</dc:creator>
      <dc:date>2020-02-20T08:15:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Inspection for Chromebooks</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/428089#M94664</link>
      <description>&lt;P&gt;same issue here - I have noticed that a reboot typically resolves it but not before people come and say that they can't login.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2021 13:27:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inspection-for-chromebooks/m-p/428089#M94664</guid>
      <dc:creator>TerryBradford</dc:creator>
      <dc:date>2021-08-20T13:27:19Z</dc:date>
    </item>
  </channel>
</rss>

