<?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: Google Earth (Pro) and SSL Decrypt in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/408844#M92398</link>
    <description>&lt;P&gt;No, I end up just making a decrypt bypass rule just for it.&amp;nbsp; I find google, like many other vendors (talking about you ArcGIS and many network appliances) are hard coding / cert pinning rather than using the OS certificate root store hence I ended up making all sorts of holes for this. I assume it's only going to get worse in the future given the move by major vendors and movers in the IT world to squash MITM "attacks" under the guise of privacy though in reality it has nothing to do with that.&lt;/P&gt;</description>
    <pubDate>Tue, 25 May 2021 01:54:25 GMT</pubDate>
    <dc:creator>PeterT</dc:creator>
    <dc:date>2021-05-25T01:54:25Z</dc:date>
    <item>
      <title>Google Earth (Pro) and SSL Decrypt</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/342123#M85781</link>
      <description>&lt;P&gt;Anybody figured out a the magic combo to get Google Earth (Pro) not to warn on startup with SSL Decrypt?&amp;nbsp; Before you ask "yes" SSL decrypt is working no errors or warnings in browsers (i.e. CA's in trust store) and yes I thought about the ICA issue and imported the GTS CA 1O1 cert on the off chance that was the issue.&amp;nbsp; Any other ideas outside "bypass or ignore it".&amp;nbsp; Google Earth (Pro) the only Google app/suite I'm still having issues with here.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2020 01:09:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/342123#M85781</guid>
      <dc:creator>PeterT</dc:creator>
      <dc:date>2020-08-05T01:09:40Z</dc:date>
    </item>
    <item>
      <title>Re: Google Earth (Pro) and SSL Decrypt</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/408840#M92396</link>
      <description>&lt;P&gt;Did you ever find an answer to this?&amp;nbsp; &amp;nbsp;I have put google earth in our whitlested apps and its not working.&amp;nbsp; This started last Friday after some Palo updates...&lt;/P&gt;</description>
      <pubDate>Tue, 25 May 2021 01:21:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/408840#M92396</guid>
      <dc:creator>Chad_DBI</dc:creator>
      <dc:date>2021-05-25T01:21:51Z</dc:date>
    </item>
    <item>
      <title>Re: Google Earth (Pro) and SSL Decrypt</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/408844#M92398</link>
      <description>&lt;P&gt;No, I end up just making a decrypt bypass rule just for it.&amp;nbsp; I find google, like many other vendors (talking about you ArcGIS and many network appliances) are hard coding / cert pinning rather than using the OS certificate root store hence I ended up making all sorts of holes for this. I assume it's only going to get worse in the future given the move by major vendors and movers in the IT world to squash MITM "attacks" under the guise of privacy though in reality it has nothing to do with that.&lt;/P&gt;</description>
      <pubDate>Tue, 25 May 2021 01:54:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/google-earth-pro-and-ssl-decrypt/m-p/408844#M92398</guid>
      <dc:creator>PeterT</dc:creator>
      <dc:date>2021-05-25T01:54:25Z</dc:date>
    </item>
  </channel>
</rss>

