<?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: Different behaviors when using Unix via SSH - Keys in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408285#M84291</link>
    <description>&lt;P&gt;The cpm uses the CyberArk TPC framework to verify and change passwords .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The PSM uses Plink to connect to target accounts .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TPC can handle various key formats , plink can't .&lt;/P&gt;</description>
    <pubDate>Wed, 21 Jan 2026 16:45:30 GMT</pubDate>
    <dc:creator>Mal</dc:creator>
    <dc:date>2026-01-21T16:45:30Z</dc:date>
    <item>
      <title>Different behaviors when using Unix via SSH - Keys</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408284#M84290</link>
      <description>&lt;P&gt;Hello! I wanted to understand the behavior of the SSH connector with Keys.&lt;/P&gt;&lt;P&gt;I embedded an account with a private key, and CPM works normally, successfully verifying the key and setting it to "compliance".&lt;/P&gt;&lt;P&gt;The issue is that when a connection attempt is made, it returns a failure. The error in question is: SH019E PSMSSHClient Initialization failed. Code -1.&lt;/P&gt;&lt;P&gt;This same PSM is working normally on other connections. I found a community thread discussing the key format, stating that "-----BEGIN OPENSSH PRIVATE KEY-----" is not supported, only "----BEGIN RSA PRIVATE KEY-----".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I requested the infrastructure team to build a new key in the correct format, but I wanted to understand if this is really the cause of the error and how CPM is able to verify it.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 16:40:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408284#M84290</guid>
      <dc:creator>vgaidis</dc:creator>
      <dc:date>2026-01-21T16:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: Different behaviors when using Unix via SSH - Keys</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408285#M84291</link>
      <description>&lt;P&gt;The cpm uses the CyberArk TPC framework to verify and change passwords .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The PSM uses Plink to connect to target accounts .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TPC can handle various key formats , plink can't .&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 16:45:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408285#M84291</guid>
      <dc:creator>Mal</dc:creator>
      <dc:date>2026-01-21T16:45:30Z</dc:date>
    </item>
    <item>
      <title>Re: Different behaviors when using Unix via SSH - Keys</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408286#M84292</link>
      <description>&lt;P&gt;This explains the difference in behavior and reinforces the action of generating a new key in the correct format. Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 16:49:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/different-behaviors-when-using-unix-via-ssh-keys/m-p/1408286#M84292</guid>
      <dc:creator>vgaidis</dc:creator>
      <dc:date>2026-01-21T16:49:58Z</dc:date>
    </item>
  </channel>
</rss>

