<?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: SCP to R81.20 after JHF 41 installation in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202325#M33675</link>
    <description>&lt;P&gt;Also noting that restarting sshd on a JHF41 host did not make any difference.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Jan 2024 15:06:30 GMT</pubDate>
    <dc:creator>Matt_Taber</dc:creator>
    <dc:date>2024-01-05T15:06:30Z</dc:date>
    <item>
      <title>SCP to R81.20 after JHF 41 installation</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202324#M33674</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;We upgraded our MGMT servers (3) to R81.20 JHF41 yesterday, smooth process.&lt;/P&gt;&lt;P&gt;After the upgrade, however, we cannot scp TO a host that has JHF41 installed, get a weird message about flags that weren't even entered:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Working to R81.20 JHF26 host:&lt;/P&gt;&lt;P&gt;[Expert@mercury:0]# scp -p 20231213_cert_list.txt admin@192.168.2.251:&lt;BR /&gt;This system is for authorized use only.&lt;BR /&gt;admin@192.168.2.251's password:&lt;BR /&gt;20231213_cert_list.txt 100% 9082 9.3MB/s 00:00&lt;/P&gt;&lt;P&gt;Non working to R81.20 JHF41 host:&lt;/P&gt;&lt;P&gt;[Expert@mercury:0]# scp -p 20231213_cert_list.txt admin@192.168.2.6:&lt;BR /&gt;This system is for authorized use only.&lt;BR /&gt;admin@192.168.2.6's password:&lt;BR /&gt;CLINFR0329 Invalid command:'&lt;STRONG&gt;scp -p -t&lt;/STRONG&gt; .'.&lt;/P&gt;&lt;P&gt;Not sure where the '-t' flag is coming from, I didn't type it. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ran it with -v:&lt;/P&gt;&lt;P&gt;debug1: Sending command: scp -v -p -t .&lt;BR /&gt;CLINFR0329 Invalid command:'scp -v -p -t .'.&lt;/P&gt;&lt;P&gt;Ran it with -v to the JHF26 host and it shows that it was also sending -v -p -t, so not sure what the issue is on JHF 41.&lt;/P&gt;&lt;P&gt;I ran a diff on /etc/ssh/sshd_config between the 2 JHFs, they're the same.&amp;nbsp; &amp;nbsp;/usr/sbin/sshd is the same between the 2 takes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for reading&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2024 15:00:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202324#M33674</guid>
      <dc:creator>Matt_Taber</dc:creator>
      <dc:date>2024-01-05T15:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: SCP to R81.20 after JHF 41 installation</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202325#M33675</link>
      <description>&lt;P&gt;Also noting that restarting sshd on a JHF41 host did not make any difference.&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2024 15:06:30 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202325#M33675</guid>
      <dc:creator>Matt_Taber</dc:creator>
      <dc:date>2024-01-05T15:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: SCP to R81.20 after JHF 41 installation</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202340#M33680</link>
      <description>&lt;P&gt;Disregard, I didn't realize that the shell was now /etc/cli.sh rather than /bin/bash for user 'admin'.&amp;nbsp; &amp;nbsp; Usually when the shell changes after an upgrade, it flips it back to clish.&amp;nbsp; I've never seen it set it to cli.sh&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Changed the shell to bash and all is well.&amp;nbsp; &amp;nbsp; &amp;nbsp;chsh --shell /bin/bash admin&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2024 18:34:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202340#M33680</guid>
      <dc:creator>Matt_Taber</dc:creator>
      <dc:date>2024-01-05T18:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: SCP to R81.20 after JHF 41 installation</title>
      <link>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202352#M33691</link>
      <description>&lt;P&gt;Note that chsh is not a supported way to change the user's login shell. Changes made outside of clish do not update the clish config, and clish sometimes overwrites the external files you changed with versions which it generates based on its config. To change a user's login shell, you&amp;nbsp;&lt;STRONG&gt;must&lt;/STRONG&gt; use 'set user admin shell /bin/bash' in clish and you &lt;STRONG&gt;must&lt;/STRONG&gt; run 'save config' afterwards.&lt;/P&gt;
&lt;P&gt;I can't stand clish, and this is one of the things I most dislike about it.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2024 19:14:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/SCP-to-R81-20-after-JHF-41-installation/m-p/202352#M33691</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2024-01-05T19:14:50Z</dc:date>
    </item>
  </channel>
</rss>

