<?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: ssh config on a PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407924#M536234</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With my experiance, it's been that you're using DES (Putty defaults to 3DES I think).  If you go to the ssh category in the Putty config you can move DES up above the "warn below here" line.  Or the "ca save all" wasn't issued and you lost the key on reboot.  It could be an accesslist somewhere else in the configuration also.  Have you tried to capture the packets and see if they're in fact getting to the machine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 Jun 2005 10:15:52 GMT</pubDate>
    <dc:creator>david_leach</dc:creator>
    <dc:date>2005-06-30T10:15:52Z</dc:date>
    <item>
      <title>ssh config on a PIX</title>
      <link>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407920#M536221</link>
      <description>&lt;P&gt;I have generated and saved a RSA Key and then set a ssh statement for my address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Putty returns a connection refused statement.  What have I missed?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:14:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407920#M536221</guid>
      <dc:creator>john.graves</dc:creator>
      <dc:date>2020-02-21T08:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: ssh config on a PIX</title>
      <link>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407921#M536223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you save the CA with the "ca save all" command?  If not, I would check to see if you have an ACL permitting the connection to the PIX.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 27 Jun 2005 18:06:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407921#M536223</guid>
      <dc:creator>jripkey</dc:creator>
      <dc:date>2005-06-27T18:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: ssh config on a PIX</title>
      <link>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407922#M536226</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Most flavors of PIX IOS only support SSH version 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try it as SSH version 1 with 3DES (or DES if that's all your license permits). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you do a 'sh ver' it will give you your license restrictions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good Luck&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Jun 2005 01:47:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407922#M536226</guid>
      <dc:creator>scottmac</dc:creator>
      <dc:date>2005-06-28T01:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: ssh config on a PIX</title>
      <link>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407923#M536231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just like the other reply mentioned, "ca save all" will save the RSA Key information, a "write memory" will not. Upon reboot, if this command wasn't specified, you will be unable to gain access with SSH. Also, if you change the domain name/host name of the device, this will also cause your SSH sessions to not work. The RSA Key is bound to your domain name you specify.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Jun 2005 03:23:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407923#M536231</guid>
      <dc:creator>matt.austin</dc:creator>
      <dc:date>2005-06-29T03:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: ssh config on a PIX</title>
      <link>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407924#M536234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With my experiance, it's been that you're using DES (Putty defaults to 3DES I think).  If you go to the ssh category in the Putty config you can move DES up above the "warn below here" line.  Or the "ca save all" wasn't issued and you lost the key on reboot.  It could be an accesslist somewhere else in the configuration also.  Have you tried to capture the packets and see if they're in fact getting to the machine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jun 2005 10:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-config-on-a-pix/m-p/407924#M536234</guid>
      <dc:creator>david_leach</dc:creator>
      <dc:date>2005-06-30T10:15:52Z</dc:date>
    </item>
  </channel>
</rss>

