<?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: What are the implications of the Encrypted  SNI During TLS Negotation? in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29224#M5986</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it did not take long for this to move from theoretical to practical issues:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://blog.mozilla.org/security/2018/10/18/encrypted-sni-comes-to-firefox-nightly/" title="https://blog.mozilla.org/security/2018/10/18/encrypted-sni-comes-to-firefox-nightly/"&gt;https://blog.mozilla.org/security/2018/10/18/encrypted-sni-comes-to-firefox-nightly/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firefox now supports encrypted SNI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 20 Oct 2018 15:22:35 GMT</pubDate>
    <dc:creator>Vladimir</dc:creator>
    <dc:date>2018-10-20T15:22:35Z</dc:date>
    <item>
      <title>What are the implications of the Encrypted  SNI During TLS Negotation?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29222#M5984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The SNI has been a major pain for HTTPS inspection for quite a while and I was told that CP is working on it.&lt;/P&gt;&lt;P&gt;Today I am seeing the article about CloudFlare implementing&amp;nbsp;Encrypted SNI During TLS Negotation:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.bleepingcomputer.com/news/security/cloudflare-improves-privacy-by-encrypting-the-sni-during-tls-negotation/" title="https://www.bleepingcomputer.com/news/security/cloudflare-improves-privacy-by-encrypting-the-sni-during-tls-negotation/"&gt;Cloudflare Improves Privacy by Encrypting the SNI During TLS Negotation&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone chime in on how this will impact our ability to use HTTPS inspection?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Sep 2018 13:54:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29222#M5984</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-09-24T13:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: What are the implications of the Encrypted  SNI During TLS Negotation?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29223#M5985</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't see this having a lot of impact initially, given that browsers will also need to support this and the spec is draft.&lt;/P&gt;&lt;P&gt;It will definitely be something we have to track going forward.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can see this being problematic in situations where HTTPS Categorization is done, where SNI is the only way you can figure out what&amp;nbsp;service the end user is truly accessing.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Sep 2018 00:29:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29223#M5985</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2018-09-25T00:29:11Z</dc:date>
    </item>
    <item>
      <title>Re: What are the implications of the Encrypted  SNI During TLS Negotation?</title>
      <link>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29224#M5986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it did not take long for this to move from theoretical to practical issues:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://blog.mozilla.org/security/2018/10/18/encrypted-sni-comes-to-firefox-nightly/" title="https://blog.mozilla.org/security/2018/10/18/encrypted-sni-comes-to-firefox-nightly/"&gt;https://blog.mozilla.org/security/2018/10/18/encrypted-sni-comes-to-firefox-nightly/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firefox now supports encrypted SNI.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Oct 2018 15:22:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/What-are-the-implications-of-the-Encrypted-SNI-During-TLS/m-p/29224#M5986</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-10-20T15:22:35Z</dc:date>
    </item>
  </channel>
</rss>

