<?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: Linux users are not able to connect to SNX after removing weak ciphers in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181707#M4959</link>
    <description>&lt;P&gt;Thank you all! I was hoping for some easy solution (like pushing a config setting here and there &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Still this perfectly explains why this issue occured. I guess we will keep these ciphers (although security scans state they are weak) at least until RFE becomes a vital SNX client option.&lt;BR /&gt;&lt;BR /&gt;Cheers mates!&lt;/P&gt;</description>
    <pubDate>Tue, 23 May 2023 07:40:39 GMT</pubDate>
    <dc:creator>AngelS</dc:creator>
    <dc:date>2023-05-23T07:40:39Z</dc:date>
    <item>
      <title>Linux users are not able to connect to SNX after removing weak ciphers</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181614#M4955</link>
      <description>&lt;P&gt;Hi all!&lt;BR /&gt;After disabling some weak ciphers users on Linux and MAC are not able to connect to SSLVPN.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Firewall OS version: R81.10&lt;BR /&gt;User's OS: Ubuntu 22.04&lt;BR /&gt;SNX agent&amp;nbsp; on Users's PC: 800008304&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;openssl version: 3.0.2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Weak ciphers being disabled are:&lt;BR /&gt;&lt;BR /&gt;TLS_RSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;TLS_RSA_WITH_AES_128_CBC_SHA256&lt;BR /&gt;TLS_RSA_WITH_AES_128_GCM_SHA256&lt;BR /&gt;TLS_RSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;TLS_RSA_WITH_AES_256_CBC_SHA256&lt;BR /&gt;TLS_RSA_WITH_AES_256_GCM_SHA384&lt;BR /&gt;&lt;SPAN&gt;TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Weak ciphers were disabled according sk126613 (&lt;A href="https://support.checkpoint.com/results/sk/sk126613#20" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk126613#20&lt;/A&gt;)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;All users using Windows can connect to SSLVPN, all users using Checkpoint Mobile client also can connect. (The ones using SSLVPN are not allowed to use Checkpoint Mobile client due to Compliance prerequisites - they are working with their personal PCs).&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;nsx.elg debug shows following 5 ciphers on nsx's ciphers list:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;[ 80536 -138049728]@user[20 May 22:27:43] Cipher List:&lt;BR /&gt;[ 80536 -138049728]@user[20 May 22:27:43] 0: AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1&lt;BR /&gt;[ 80536 -138049728]@user[20 May 22:27:43] 1: AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1&lt;BR /&gt;[ 80536 -138049728]@user[20 May 22:27:43] 2: DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1&lt;BR /&gt;[ 80536 -138049728]@user[20 May 22:27:43] 3: RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1&lt;BR /&gt;[ 80536 -138049728]@user[20 May 22:27:43] 4: DES-CBC-SHA SSLv3 Kx=RSA Au=RSA Enc=DES(56) Mac=SHA1&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;My guess is changing this list will solve the issue.&lt;BR /&gt;So is there any way this nsx cipher list to be changed?&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 08:56:40 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181614#M4955</guid>
      <dc:creator>AngelS</dc:creator>
      <dc:date>2023-05-22T08:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: Linux users are not able to connect to SNX after removing weak ciphers</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181676#M4958</link>
      <description>&lt;P&gt;I had this issue a while back. Basically there are much more methods implemented in the Windows client than in the MAC/Linux ones. At least the Mac, I haven't used the Linux yet but I would assume they're similar.&lt;/P&gt;&lt;P&gt;&lt;A href="https://datatracker.ietf.org/doc/html/rfc5246#section-9" target="_blank" rel="noopener"&gt;RFC 5246 - The Transport Layer Security (TLS) Protocol Version 1.2 (ietf.org)&lt;/A&gt;&amp;nbsp;section 9 defines that&amp;nbsp;TLS_RSA_WITH_AES_128_CBC_SHA is mandatory and with the clients you mentioned it seems to be a limitation of non-Windows clients, by adding&amp;nbsp;TLS_RSA_WITH_AES_128_CBC_SHA and&amp;nbsp;TLS_RSA_WITH_AES_256_CBC_SHA MAC, clients could connect again.&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 19:28:44 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181676#M4958</guid>
      <dc:creator>Alex-</dc:creator>
      <dc:date>2023-05-22T19:28:44Z</dc:date>
    </item>
    <item>
      <title>Re: Linux users are not able to connect to SNX after removing weak ciphers</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181684#M4956</link>
      <description>&lt;P&gt;This SK says this is currently an RFE:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk180837" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk180837&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 22:04:35 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181684#M4956</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-05-22T22:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: Linux users are not able to connect to SNX after removing weak ciphers</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181685#M4957</link>
      <description>&lt;P&gt;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;is 100% right...had customer in the past work with TAC and they were told exact same thing, it is an RFE.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 22:20:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181685#M4957</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-05-22T22:20:28Z</dc:date>
    </item>
    <item>
      <title>Re: Linux users are not able to connect to SNX after removing weak ciphers</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181707#M4959</link>
      <description>&lt;P&gt;Thank you all! I was hoping for some easy solution (like pushing a config setting here and there &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Still this perfectly explains why this issue occured. I guess we will keep these ciphers (although security scans state they are weak) at least until RFE becomes a vital SNX client option.&lt;BR /&gt;&lt;BR /&gt;Cheers mates!&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2023 07:40:39 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Linux-users-are-not-able-to-connect-to-SNX-after-removing-weak/m-p/181707#M4959</guid>
      <dc:creator>AngelS</dc:creator>
      <dc:date>2023-05-23T07:40:39Z</dc:date>
    </item>
  </channel>
</rss>

