<?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 Thanks Ashish. 3DES-AWS is in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054351#M22903</link>
    <description>&lt;P&gt;Thanks Ashish. 3DES-AWS is enabled, but how do i check if the ssh keys are above 768? Also what does that exactly mean?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;And yes ssh version 2 is supported.&lt;/P&gt;</description>
    <pubDate>Mon, 08 May 2017 22:04:59 GMT</pubDate>
    <dc:creator>ramesh.8901</dc:creator>
    <dc:date>2017-05-08T22:04:59Z</dc:date>
    <item>
      <title>Moving to SSH version 2 from compatible mode - Do i need to re-generate keys?</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054349#M22897</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;On my ASAs (5545 - version 9.5(2)), i am trying to move from the compatible version and forcing it to only version 2. Is there something that i need to take care of while doing this so that i don't get locked out? Do i need to re-generate the ssh keys once i do this?&lt;/P&gt;
&lt;P&gt;I do not have console access to these ASAs, so i want to make sure that i do this right. Please can someone advise?&lt;/P&gt;
&lt;P&gt;Here's the output for ssh on my firewall:&lt;/P&gt;
&lt;P&gt;sh ssh&lt;BR /&gt;Timeout: 60 minutes&lt;BR /&gt;Versions allowed: 1 and 2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;sh run aaa&lt;BR /&gt;aaa authentication ssh console LOCAL&lt;BR /&gt;aaa authentication http console LOCAL&lt;BR /&gt;aaa authorization command LOCAL&lt;BR /&gt;aaa authorization exec LOCAL&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:42:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054349#M22897</guid>
      <dc:creator>ramesh.8901</dc:creator>
      <dc:date>2019-03-11T07:42:15Z</dc:date>
    </item>
    <item>
      <title>Make sure you have following</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054350#M22901</link>
      <description>&lt;P&gt;Make sure you have following&lt;/P&gt;
&lt;P&gt;-3DES-AES license is enabled&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Make sure SSH keys are above 768 if not re-generate.&lt;/P&gt;
&lt;P&gt;-command to enable ssh V2 is below "ssh version 2"&lt;/P&gt;
&lt;P&gt;-SSH client should support V2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;you can also perform these changes from ASDM by going to Configuration&amp;gt;Device Management&amp;gt;Management access&amp;gt;ASDM/HTTPS/Telnet/SSH -- change allowed version to 2 only&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Ashish&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 19:26:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054350#M22901</guid>
      <dc:creator>Ashish Jhaldiyal</dc:creator>
      <dc:date>2017-05-08T19:26:08Z</dc:date>
    </item>
    <item>
      <title>Thanks Ashish. 3DES-AWS is</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054351#M22903</link>
      <description>&lt;P&gt;Thanks Ashish. 3DES-AWS is enabled, but how do i check if the ssh keys are above 768? Also what does that exactly mean?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;And yes ssh version 2 is supported.&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 22:04:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054351#M22903</guid>
      <dc:creator>ramesh.8901</dc:creator>
      <dc:date>2017-05-08T22:04:59Z</dc:date>
    </item>
    <item>
      <title>Ignore it, I just tested ssh</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054352#M22904</link>
      <description>&lt;P&gt;Ignore it, I just tested ssh v 2 with 512 key length and it works fine..&lt;/P&gt;
&lt;P&gt;So all you need is&lt;/P&gt;
&lt;P&gt;3des license&lt;/P&gt;
&lt;P&gt;ssh version 2&lt;/P&gt;
&lt;P&gt;client which supports ssh version 2&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 22:52:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054352#M22904</guid>
      <dc:creator>Ashish Jhaldiyal</dc:creator>
      <dc:date>2017-05-08T22:52:28Z</dc:date>
    </item>
    <item>
      <title>For security 2048 is</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054353#M22906</link>
      <description>&lt;P&gt;For security 2048 is recommended.&lt;/P&gt;</description>
      <pubDate>Mon, 08 May 2017 23:47:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054353#M22906</guid>
      <dc:creator>Ashish Jhaldiyal</dc:creator>
      <dc:date>2017-05-08T23:47:05Z</dc:date>
    </item>
    <item>
      <title>Here is a guide for enabling</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054354#M22908</link>
      <description>&lt;P&gt;Here is a guide for enabling SSH:&lt;/P&gt;
&lt;P&gt;https://supportforums.cisco.com/document/12338141/guide-better-ssh-security&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 06:43:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054354#M22908</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2017-05-09T06:43:57Z</dc:date>
    </item>
    <item>
      <title>Thanks Karsten. I did take a</title>
      <link>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054355#M22910</link>
      <description>&lt;P&gt;Thanks Karsten. I did take a look at this document when i was googling for answers before putting this question up over here. &amp;nbsp;It's really good! I was however wondering in my case, how do i go about check to see how i can go about looking at the length of the RSA keys i have an more importantly if i would have to renegotiate the keys is force to SSH version 2 from the compatible mode.&lt;/P&gt;</description>
      <pubDate>Tue, 09 May 2017 23:38:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/moving-to-ssh-version-2-from-compatible-mode-do-i-need-to-re/m-p/3054355#M22910</guid>
      <dc:creator>ramesh.8901</dc:creator>
      <dc:date>2017-05-09T23:38:05Z</dc:date>
    </item>
  </channel>
</rss>

