<?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: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340140#M85379</link>
    <description>&lt;P&gt;Hmn ... strange ... (I want to have TLS1.3 on my IIS too but something obviously I am doing wrong &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt; )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, back to the actual issue:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Did you try to do a packet capture of the full connection? Traffic between the client and the firewall and also between the firewall and the iis? In this capture you should see the TLS handshake packets including the ciphersuite proposal&lt;/LI&gt;
&lt;LI&gt;Did you do a packet capture when you connect from a client either directly to the reverse proxy or then with the unsupported protocol/algorithm checkbox disabled?&lt;/LI&gt;
&lt;LI&gt;Compare the TLS handshakes in the packet captures if there are differences&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If not done already maybe you should consider doing these captures and maybe post the results here.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jul 2020 19:18:01 GMT</pubDate>
    <dc:creator>Remo</dc:creator>
    <dc:date>2020-07-22T19:18:01Z</dc:date>
    <item>
      <title>Broken SSL Inbound Inspection After July Windows Updates Enables TLS 1.3</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/339858#M85326</link>
      <description>&lt;P&gt;I have been using SSL Inbound Decryption for over a year with options&lt;/P&gt;&lt;P&gt;1) Block sessions with unsupported versions&lt;/P&gt;&lt;P&gt;2) Block sessions with unsupported cipher suites&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After applying Windows 10 updates to a reverse proxy server, it&amp;nbsp;appears that&lt;SPAN&gt;&amp;nbsp;connection to website is encrypted and authenticated using TLS 1.3, X25519, and AES_256_GCM (based on Google Chrome developer tools security tab).&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I now get the error SSL_ERROR_NO_CYPHER_OVERLAP.&amp;nbsp; This error goes away only if I disable 2) Block sessions with unsupported cipher suites from the SSL Inbound Decryption policy.&amp;nbsp; Permitting all the cipher suites in the decryption profile without disabling #2 does not work.&amp;nbsp; Does Palo Alto support Inbound SSL decryption for TLS 1.3 for any PanOS?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone resolved a similar issue update windows registry keys to force the connection to use TLS 1.2?&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2020 14:54:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/339858#M85326</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-23T14:54:27Z</dc:date>
    </item>
    <item>
      <title>Re: Broken SSL Inbound Inspection After July Windows Updates Enables TLS 1.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/339970#M85344</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/93469"&gt;@fhewiufhwefhwe&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Decryption of TLS 1.3 is supported in PAN-OS 10 (but I definately do not recommend to install this just released PAN-OS version in a production environment).&lt;/P&gt;
&lt;P&gt;So the other way is to diable TLS1.3 untill PAN-OS 10 becomed a prefered release by PaloAlto TAC Support. So far I was not able to find anything related to disable TLS1.3 but I assume it should work the same way as you can disable older versions like TLS1.0/TLS1.1:&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-11" target="_blank"&gt;https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings#tls-11&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jul 2020 23:46:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/339970#M85344</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2020-07-21T23:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: Broken SSL Inbound Inspection After July Windows Updates Enables TLS 1.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/339971#M85345</link>
      <description>&lt;P&gt;I tried disabling TLS 1.3 on the reverse proxy server with the &lt;SPAN&gt;HKLM SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL registry keys&lt;/SPAN&gt;, but wasn't able to get the webpages to load.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have been able to get it to load by either turning off ssl inbound decryption, or rolling back a critical windows update.&amp;nbsp; &amp;nbsp;I'm doing the former now.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 00:14:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/339971#M85345</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-22T00:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: Broken SSL Inbound Inspection After July Windows Updates Enables TLS 1.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340028#M85356</link>
      <description>&lt;P&gt;I assume you did reboot the system after the TLS1.3 deactivation?&lt;/P&gt;
&lt;P&gt;Btw. did you install an insider preview build? I was only able to find information about TLS1.3 activation in such preview builds...&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 09:52:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340028#M85356</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2020-07-22T09:52:56Z</dc:date>
    </item>
    <item>
      <title>Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS 1.3</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340044#M85362</link>
      <description>&lt;P&gt;No, it is not a preview release.&amp;nbsp; The reverse proxy server is using Windows 10 Pro.&amp;nbsp; I had the problem both with and without installing the May 2020 feature pack.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 13:16:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340044#M85362</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-22T13:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340121#M85377</link>
      <description>&lt;P&gt;What software do you use exactly for the reverse proxy part?&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 17:58:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340121#M85377</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2020-07-22T17:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340122#M85378</link>
      <description>&lt;P&gt;IIS&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 18:00:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340122#M85378</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-22T18:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340140#M85379</link>
      <description>&lt;P&gt;Hmn ... strange ... (I want to have TLS1.3 on my IIS too but something obviously I am doing wrong &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt; )&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, back to the actual issue:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Did you try to do a packet capture of the full connection? Traffic between the client and the firewall and also between the firewall and the iis? In this capture you should see the TLS handshake packets including the ciphersuite proposal&lt;/LI&gt;
&lt;LI&gt;Did you do a packet capture when you connect from a client either directly to the reverse proxy or then with the unsupported protocol/algorithm checkbox disabled?&lt;/LI&gt;
&lt;LI&gt;Compare the TLS handshakes in the packet captures if there are differences&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If not done already maybe you should consider doing these captures and maybe post the results here.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 19:18:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340140#M85379</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2020-07-22T19:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340162#M85384</link>
      <description>&lt;P&gt;No, I will look into a packet capture.&amp;nbsp; I did configure a restricted vpn as a temporary workaround for a 3rd party whose access was broken.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2020 19:57:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340162#M85384</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-22T19:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340375#M85434</link>
      <description>&lt;P&gt;Monitor-&amp;gt;Traffic-&amp;gt;Logs shows&amp;nbsp;&lt;/P&gt;&lt;P&gt;session end reason = decrypt-unsupport-param&lt;/P&gt;&lt;P&gt;from zone = trust&lt;/P&gt;&lt;P&gt;to zone = DMZ&lt;/P&gt;&lt;P&gt;source = client&lt;/P&gt;&lt;P&gt;destination = public ipaddress for website hosted on DMZ&lt;/P&gt;&lt;P&gt;NAT applied&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wireshark 3.2.4 packet capture from client to public ipaddress for website hosted on DMZ&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fhewiufhwefhwe_0-1595525350618.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/26994i80DE02CBDD99361D/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="fhewiufhwefhwe_0-1595525350618.png" alt="fhewiufhwefhwe_0-1595525350618.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For purposes of testing, both the reverse proxy server and the client have the following windows registry key settings.&amp;nbsp; I'll review and disable weak ciphers once SSL Inbound Inspection works again...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HKLM\System\ControlSet001\Control\Cryptography\Configuration\Local\SSL\00010002\Functions&lt;BR /&gt;TLS_AES_256_GCM_SHA384&lt;BR /&gt;TLS_AES_128_GCM_SHA256&lt;BR /&gt;TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384&lt;BR /&gt;TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256&lt;BR /&gt;TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384&lt;BR /&gt;TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256&lt;BR /&gt;TLS_DHE_RSA_WITH_AES_256_GCM_SHA384&lt;BR /&gt;TLS_DHE_RSA_WITH_AES_128_GCM_SHA256&lt;BR /&gt;TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384&lt;BR /&gt;TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256&lt;BR /&gt;TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384&lt;BR /&gt;TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256&lt;BR /&gt;TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;TLS_RSA_WITH_AES_256_GCM_SHA384&lt;BR /&gt;TLS_RSA_WITH_AES_128_GCM_SHA256&lt;BR /&gt;TLS_RSA_WITH_AES_256_CBC_SHA256&lt;BR /&gt;TLS_RSA_WITH_AES_128_CBC_SHA256&lt;BR /&gt;TLS_RSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;TLS_RSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;TLS_RSA_WITH_3DES_EDE_CBC_SHA&lt;BR /&gt;TLS_RSA_WITH_NULL_SHA256&lt;BR /&gt;TLS_RSA_WITH_NULL_SHA&lt;BR /&gt;TLS_PSK_WITH_AES_256_GCM_SHA384&lt;BR /&gt;TLS_PSK_WITH_AES_128_GCM_SHA256&lt;BR /&gt;TLS_PSK_WITH_AES_256_CBC_SHA384&lt;BR /&gt;TLS_PSK_WITH_AES_128_CBC_SHA256&lt;BR /&gt;TLS_PSK_WITH_NULL_SHA384&lt;BR /&gt;TLS_PSK_WITH_NULL_SHA256&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jul 2020 17:37:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340375#M85434</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-23T17:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: Broken SSL Inbound Inspection After July Windows Updates Enables TLS 1.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340455#M85448</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fhewiufhwefhwe_0-1595553395531.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27001iF41653481B5650BF/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="fhewiufhwefhwe_0-1595553395531.png" alt="fhewiufhwefhwe_0-1595553395531.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Confirmed support for TLS 1.3 via a scanning tool&lt;/P&gt;&lt;P&gt;I'll try moving the TLS 1.3 ciphers to the end of the list.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2020 01:17:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340455#M85448</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-24T01:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Broken SSL Inbound Inspection After July Windows Updates Enables TLS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340662#M85476</link>
      <description>&lt;P&gt;I tried upgrading to PanOS 10.0 to see if it would fix the issue, but that also does not work surprisingly.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Jul 2020 18:23:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/broken-ssl-inbound-inspection-after-july-windows-updates-enables/m-p/340662#M85476</guid>
      <dc:creator>fhewiufhwefhwe</dc:creator>
      <dc:date>2020-07-25T18:23:24Z</dc:date>
    </item>
  </channel>
</rss>

