<?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 ASA CiscoSSH Stack vs ASA Proprietary SSH stack in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-ciscossh-stack-vs-asa-proprietary-ssh-stack/m-p/5294813#M1121190</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;ASA 9.20 release (on FPR2100 device). I had a TAC case about TACACS+ Remote Address = 0.0.0.0 in certain Authentication Requests (when using public key auth, and also in Authorization requests) - the TAC told me to "no&amp;nbsp;&lt;SPAN&gt;ssh stack ciscossh" - that fixed the TACACS+ Remote Address issue (it's populated correctly in this mode). I wasn't aware of the "proprietary SSH stack"&lt;/SPAN&gt;&amp;nbsp;until now.&lt;/P&gt;
&lt;P&gt;Anyone know what the downsides are of running this SSH stack vs the CiscoSSH? I don't need FIPS compliance. I am more concerned about the TACACS+ Remote Address working.&lt;/P&gt;
&lt;P&gt;I can't be sure, but it sounds like CiscoSSH is updated more regularly (due to the openssh link) - but does that mean the other stack is not maintained?&amp;nbsp; Cisco docs don't explain that well.&amp;nbsp; And then then obvious question: has any pen testing been done to compare the two stacks and how they compare?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 May 2025 10:29:14 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2025-05-29T10:29:14Z</dc:date>
    <item>
      <title>ASA CiscoSSH Stack vs ASA Proprietary SSH stack</title>
      <link>https://community.cisco.com/t5/network-security/asa-ciscossh-stack-vs-asa-proprietary-ssh-stack/m-p/5294813#M1121190</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
&lt;P&gt;ASA 9.20 release (on FPR2100 device). I had a TAC case about TACACS+ Remote Address = 0.0.0.0 in certain Authentication Requests (when using public key auth, and also in Authorization requests) - the TAC told me to "no&amp;nbsp;&lt;SPAN&gt;ssh stack ciscossh" - that fixed the TACACS+ Remote Address issue (it's populated correctly in this mode). I wasn't aware of the "proprietary SSH stack"&lt;/SPAN&gt;&amp;nbsp;until now.&lt;/P&gt;
&lt;P&gt;Anyone know what the downsides are of running this SSH stack vs the CiscoSSH? I don't need FIPS compliance. I am more concerned about the TACACS+ Remote Address working.&lt;/P&gt;
&lt;P&gt;I can't be sure, but it sounds like CiscoSSH is updated more regularly (due to the openssh link) - but does that mean the other stack is not maintained?&amp;nbsp; Cisco docs don't explain that well.&amp;nbsp; And then then obvious question: has any pen testing been done to compare the two stacks and how they compare?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2025 10:29:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ciscossh-stack-vs-asa-proprietary-ssh-stack/m-p/5294813#M1121190</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2025-05-29T10:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: ASA CiscoSSH Stack vs ASA Proprietary SSH stack</title>
      <link>https://community.cisco.com/t5/network-security/asa-ciscossh-stack-vs-asa-proprietary-ssh-stack/m-p/5294925#M1121197</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/146370"&gt;@Ashley Pilbeam&lt;/a&gt;&amp;nbsp;I know you have explained this in the past in the FirePower Foundry Webex Space.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2025 15:41:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-ciscossh-stack-vs-asa-proprietary-ssh-stack/m-p/5294925#M1121197</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2025-05-29T15:41:23Z</dc:date>
    </item>
  </channel>
</rss>

