<?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: SSLv2.0 and R80.20 in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63678#M12930</link>
    <description>You can do bypass by IP address for sites you know use SSLv2.&lt;BR /&gt;</description>
    <pubDate>Wed, 25 Sep 2019 17:37:41 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2019-09-25T17:37:41Z</dc:date>
    <item>
      <title>SSLv2.0 and R80.20</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63668#M12924</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello All,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;We turned on SSL Inspection on R80.20 and basically everything in our environment crashed. Looking at the logs it showed that majority of the drops were SSLv2.0 is not supported. I saw sk108654, however was notified by Checkpoint support that there is no hotfix for R80.20. There are too many sites that are using SSLv2.0 so a workaround is needed in our environment. Is there anyway to bypass all SSLv2.0 traffic other than based on category?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 15:36:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63668#M12924</guid>
      <dc:creator>ed300zx</dc:creator>
      <dc:date>2019-09-25T15:36:24Z</dc:date>
    </item>
    <item>
      <title>Re: SSLv2.0 and R80.20</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63678#M12930</link>
      <description>You can do bypass by IP address for sites you know use SSLv2.&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Sep 2019 17:37:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63678#M12930</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-09-25T17:37:41Z</dc:date>
    </item>
    <item>
      <title>Re: SSLv2.0 and R80.20</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63679#M12931</link>
      <description>&lt;P&gt;I did an export of the logs and it showed more than 65k IP's that were SSLv2.&amp;nbsp; It brought down Skype, Outlook and internal sites.&amp;nbsp; Can we bypass based on applications such as Skype, Outlook?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 17:56:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63679#M12931</guid>
      <dc:creator>ed300zx</dc:creator>
      <dc:date>2019-09-25T17:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSLv2.0 and R80.20</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63684#M12932</link>
      <description>&lt;P&gt;Ed300zx,&lt;/P&gt;&lt;P&gt;I‘m thinking your problem isn‘t related to SSLv2.0 .&lt;/P&gt;&lt;P&gt;None of your mentioned sites is using SSLv2, these is an unsecure protocol and should not used by the website owners. And most of the common owners doesn‘t.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you really sure that outlook and Skype in your connections is using SSLv2 ?&lt;/P&gt;&lt;P&gt;Maybee the logs are showing something wrong...can you please provide one ?&lt;/P&gt;&lt;P&gt;Did you opened a TAC case to check this behaviour ?&lt;/P&gt;&lt;P&gt;Wolfgang&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 19:41:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63684#M12932</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2019-09-25T19:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: SSLv2.0 and R80.20</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63685#M12933</link>
      <description>&lt;P&gt;Well correction, Skype and Outlook went down due to expired certs.&amp;nbsp; SSLv2 has to do with internal sites we have.&amp;nbsp; Totally agree SSLv2 is insecure and should not be used.&amp;nbsp; But its a up hill battle with the web app team.&amp;nbsp; So trying to figure out a work around.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 19:52:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63685#M12933</guid>
      <dc:creator>ed300zx</dc:creator>
      <dc:date>2019-09-25T19:52:10Z</dc:date>
    </item>
    <item>
      <title>Re: SSLv2.0 and R80.20</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63690#M12934</link>
      <description>&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;sk112214 -&amp;nbsp;&lt;SPAN&gt;Several HTTPS web sites and applications might not work properly when HTTPS Inspection is enabled on Security Gateway.&amp;nbsp; I guess found my answer.&amp;nbsp; &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Wed, 25 Sep 2019 20:29:10 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SSLv2-0-and-R80-20/m-p/63690#M12934</guid>
      <dc:creator>ed300zx</dc:creator>
      <dc:date>2019-09-25T20:29:10Z</dc:date>
    </item>
  </channel>
</rss>

