<?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: PSMP known_hosts file in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415167#M86275</link>
    <description>&lt;P&gt;Thanks for the feedback @Patrick Booth​&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are indeed still running on v14.2. And indeed we had to create a SELinux with more permissions for storing the recordings on an external storage.&lt;/P&gt;&lt;P&gt;Coming back to the known_hosts file problem, the only feedback we got from R&amp;amp;D so far is that the root cause are incorrect SELinux labels on the `.ssh` directory and the `errors` path under `/home/PSMShadowUser/`. They did not mention any permanent fix in v14.6+.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Feb 2026 07:28:25 GMT</pubDate>
    <dc:creator>P.Uytdenhoef582017</dc:creator>
    <dc:date>2026-02-03T07:28:25Z</dc:date>
    <item>
      <title>PSMP known_hosts file</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415163#M86271</link>
      <description>&lt;P&gt;What happens to the known_hosts file when it is deleted daily? Does it affect performance? And what happens to active sessions, given that it stores the fingerprints of the destination servers? What is the correct way to delete it when I have a fingerprint error in PSMP?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 20:15:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415163#M86271</guid>
      <dc:creator>W.Shinin143320</dc:creator>
      <dc:date>2026-01-29T20:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: PSMP known_hosts file</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415164#M86272</link>
      <description>&lt;P&gt;Hey @William Shinin​&amp;nbsp;If using 14.2+, you can leverage the recommended method to use the ServerHostKeyNotInCacheBehavior=4 parameter in basic_psmpserver.conf to manage the issue:&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-the-verification-of-a-servers-host-key.htm#Configuretheserverhostkeyforconnections" href="https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-the-verification-of-a-servers-host-key.htm#Configuretheserverhostkeyforconnections" target="_blank"&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-the-verification-of-a-servers-host-key.htm#Configuretheserverhostkeyforconnections&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;♦If you're not on a version that supports that option, or you prefer to manage in manually - you can refer to these options:&lt;/P&gt;&lt;P&gt;A) Remove this file.&amp;nbsp;It will be created again, and the ssh host keys will be cached as if this was the first time connecting to the target.&lt;/P&gt;&lt;P&gt;B) Update/edit the file, and remove the line with the corresponding IP/FQDN/Hostname of the target server, and it will be updated with the new SSH Host Key, on next connection.&lt;/P&gt;&lt;P&gt;C) Update the Fingerprint/SSH Host Key, for the corresponding line of the target server, in the correct format as noted above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/00004310" href="https://community.cyberark.com/s/article/00004310" target="_blank"&gt;https://community.cyberark.com/s/article/00004310&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Jan 2026 22:17:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415164#M86272</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-01-29T22:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: PSMP known_hosts file</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415165#M86273</link>
      <description>&lt;P&gt;There is currently an issue with ServerHostKeyNotInCacheBehavior=4 when SELinux is in enforcing mode.&lt;/P&gt;&lt;P&gt;You'll get error like:&lt;/P&gt;&lt;P&gt;&lt;I&gt;Failed to add the host to the list of known hosts (/home/PSMShadowUser/.ssh/known_hosts.0000000000000xxx).&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Until it is fixed, the easiest workaround is to go for session separation as each shadow user will have their own home directory.&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/psm_for_ssh_session_separation.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Jan 2026 09:23:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415165#M86273</guid>
      <dc:creator>P.Uytdenhoef582017</dc:creator>
      <dc:date>2026-01-30T09:23:03Z</dc:date>
    </item>
    <item>
      <title>Re: PSMP known_hosts file</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415166#M86274</link>
      <description>&lt;P&gt;@Pierre-Yves Uytdenhoef​&amp;nbsp;I believe the issue you're referring to is a bug in setups with non-standard SELinux contexts. However, that known issue is resolved in PSMP 14.6.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Feb 2026 19:52:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415166#M86274</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-02T19:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: PSMP known_hosts file</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415167#M86275</link>
      <description>&lt;P&gt;Thanks for the feedback @Patrick Booth​&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are indeed still running on v14.2. And indeed we had to create a SELinux with more permissions for storing the recordings on an external storage.&lt;/P&gt;&lt;P&gt;Coming back to the known_hosts file problem, the only feedback we got from R&amp;amp;D so far is that the root cause are incorrect SELinux labels on the `.ssh` directory and the `errors` path under `/home/PSMShadowUser/`. They did not mention any permanent fix in v14.6+.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 07:28:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415167#M86275</guid>
      <dc:creator>P.Uytdenhoef582017</dc:creator>
      <dc:date>2026-02-03T07:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: PSMP known_hosts file</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415168#M86276</link>
      <description>&lt;P&gt;@Pierre-Yves Uytdenhoef​&amp;nbsp;I believe you are actually speaking about a different issue (not fixed yet). I created an article for the issue you are referring to: https://community.cyberark.com/s/article/KI00025524&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That issue arises if initial selinux attributes on PSMShadowUser home directory were changed, and restorecon will not restore to correct selinux attributes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The workaround is to manually restore selinux attributes on PSMShadowUser home directory. "chcon -R -t home_root_t /home/PSMShadowUser/.ssh /home/PSMShadowUser/errors&lt;/P&gt;</description>
      <pubDate>Tue, 03 Feb 2026 15:19:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psmp-known-hosts-file/m-p/1415168#M86276</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-03T15:19:44Z</dc:date>
    </item>
  </channel>
</rss>

