<?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: only allowing users to ssh in with 3DES in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859021#M957917</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If I'm not mistaking, are you talking about the ssh ver?  In global config just change it to ver 2..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;router(config)#ip ssh version 2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 30 Dec 2007 17:07:38 GMT</pubDate>
    <dc:creator>Adam Frederick</dc:creator>
    <dc:date>2007-12-30T17:07:38Z</dc:date>
    <item>
      <title>only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859020#M957915</link>
      <description>&lt;P&gt;I have a cisco router running IOS 12.3,&lt;/P&gt;&lt;P&gt;c2600-ik9o3s3-mz.123-12.bin.  I've enabled&lt;/P&gt;&lt;P&gt;ssh on the device so that other administrators can ssh into the device for&lt;/P&gt;&lt;P&gt;administration purposes.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to disable the DES feature from the device.  In other words, currently&lt;/P&gt;&lt;P&gt;anyone can log into the device with&lt;/P&gt;&lt;P&gt;either DES or 3DES cipher, as seen below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[root@LinuxES root]# ssh -v -c des -l cisco 192.168.1.1&lt;/P&gt;&lt;P&gt;OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f&lt;/P&gt;&lt;P&gt;debug1: Reading configuration data /etc/ssh/ssh_config&lt;/P&gt;&lt;P&gt;debug1: Applying options for *&lt;/P&gt;&lt;P&gt;debug1: Rhosts Authentication disabled, originating port will not be trusted.&lt;/P&gt;&lt;P&gt;debug1: Connecting to 192.168.1.1 [192.168.1.1] port 22.&lt;/P&gt;&lt;P&gt;debug1: Connection established.&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/identity type -1&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/id_rsa type 1&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/id_dsa type -1&lt;/P&gt;&lt;P&gt;debug1: Remote protocol version 1.5, remote software version Cisco-1.25&lt;/P&gt;&lt;P&gt;debug1: no match: Cisco-1.25&lt;/P&gt;&lt;P&gt;debug1: Local version string SSH-1.5-OpenSSH_3.6.1p2&lt;/P&gt;&lt;P&gt;debug1: Waiting for server public key.&lt;/P&gt;&lt;P&gt;debug1: Received server public key (768 bits) and host key (1024 bits).&lt;/P&gt;&lt;P&gt;debug1: Host '192.168.1.1' is known and matches the RSA1 host key.&lt;/P&gt;&lt;P&gt;debug1: Found key in /root/.ssh/known_hosts:10&lt;/P&gt;&lt;P&gt;debug1: Encryption type: des&lt;/P&gt;&lt;P&gt;debug1: Sent encrypted session key.&lt;/P&gt;&lt;P&gt;Warning: use of DES is strongly discouraged due to cryptographic weaknesses&lt;/P&gt;&lt;P&gt;debug1: Installing crc compensation attack detector.&lt;/P&gt;&lt;P&gt;debug1: Received encrypted confirmation.&lt;/P&gt;&lt;P&gt;debug1: Doing password authentication.&lt;/P&gt;&lt;P&gt;cisco@192.168.1.1's password:&lt;/P&gt;&lt;P&gt;debug1: Requesting pty.&lt;/P&gt;&lt;P&gt;debug1: Requesting X11 forwarding with authentication spoofing.&lt;/P&gt;&lt;P&gt;Warning: Remote host denied X11 forwarding.&lt;/P&gt;&lt;P&gt;debug1: Requesting shell.&lt;/P&gt;&lt;P&gt;debug1: Entering interactive session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BGP_Trigger&amp;gt;exit&lt;/P&gt;&lt;P&gt;Connection to 192.168.1.1 closed.&lt;/P&gt;&lt;P&gt;debug1: Transferred: stdin 5, stdout 20, stderr 37 bytes in 2.0 seconds&lt;/P&gt;&lt;P&gt;debug1: Bytes per second: stdin 2.5, stdout 9.9, stderr 18.3&lt;/P&gt;&lt;P&gt;debug1: Exit status 0&lt;/P&gt;&lt;P&gt;[root@LinuxES root]# ssh -v -c 3des -l cisco 192.168.1.1&lt;/P&gt;&lt;P&gt;OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f&lt;/P&gt;&lt;P&gt;debug1: Reading configuration data /etc/ssh/ssh_config&lt;/P&gt;&lt;P&gt;debug1: Applying options for *&lt;/P&gt;&lt;P&gt;debug1: Rhosts Authentication disabled, originating port will not be trusted.&lt;/P&gt;&lt;P&gt;debug1: Connecting to 192.168.1.1 [192.168.1.1] port 22.&lt;/P&gt;&lt;P&gt;debug1: Connection established.&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/identity type -1&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/id_rsa type 1&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/id_dsa type -1&lt;/P&gt;&lt;P&gt;debug1: Remote protocol version 1.5, remote software version Cisco-1.25&lt;/P&gt;&lt;P&gt;debug1: no match: Cisco-1.25&lt;/P&gt;&lt;P&gt;debug1: Local version string SSH-1.5-OpenSSH_3.6.1p2&lt;/P&gt;&lt;P&gt;debug1: Waiting for server public key.&lt;/P&gt;&lt;P&gt;debug1: Received server public key (768 bits) and host key (1024 bits).&lt;/P&gt;&lt;P&gt;debug1: Host '192.168.1.1' is known and matches the RSA1 host key.&lt;/P&gt;&lt;P&gt;debug1: Found key in /root/.ssh/known_hosts:10&lt;/P&gt;&lt;P&gt;debug1: Encryption type: 3des&lt;/P&gt;&lt;P&gt;debug1: Sent encrypted session key.&lt;/P&gt;&lt;P&gt;debug1: Installing crc compensation attack detector.&lt;/P&gt;&lt;P&gt;debug1: Received encrypted confirmation.&lt;/P&gt;&lt;P&gt;debug1: Doing password authentication.&lt;/P&gt;&lt;P&gt;cisco@192.168.1.1's password:&lt;/P&gt;&lt;P&gt;debug1: Requesting pty.&lt;/P&gt;&lt;P&gt;debug1: Requesting X11 forwarding with authentication spoofing.&lt;/P&gt;&lt;P&gt;Warning: Remote host denied X11 forwarding.&lt;/P&gt;&lt;P&gt;debug1: Requesting shell.&lt;/P&gt;&lt;P&gt;debug1: Entering interactive session.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BGP_Trigger&amp;gt;exit&lt;/P&gt;&lt;P&gt;Connection to 192.168.1.1 closed.&lt;/P&gt;&lt;P&gt;debug1: Transferred: stdin 5, stdout 20, stderr 37 bytes in 1.0 seconds&lt;/P&gt;&lt;P&gt;debug1: Bytes per second: stdin 4.9, stdout 19.7, stderr 36.4&lt;/P&gt;&lt;P&gt;debug1: Exit status 0&lt;/P&gt;&lt;P&gt;[root@LinuxES root]#&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How do go about disabling DES on the system?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know how to accomplish this with Unix&lt;/P&gt;&lt;P&gt;devices.  Not sure if it is possible with&lt;/P&gt;&lt;P&gt;Cisco devices.  This is seen as a security risk to me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CCIE Security&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 00:55:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859020#M957915</guid>
      <dc:creator>cisco24x7</dc:creator>
      <dc:date>2019-03-13T00:55:38Z</dc:date>
    </item>
    <item>
      <title>Re: only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859021#M957917</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If I'm not mistaking, are you talking about the ssh ver?  In global config just change it to ver 2..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;router(config)#ip ssh version 2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Dec 2007 17:07:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859021#M957917</guid>
      <dc:creator>Adam Frederick</dc:creator>
      <dc:date>2007-12-30T17:07:38Z</dc:date>
    </item>
    <item>
      <title>Re: only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859022#M957919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What are you talking about?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BGP_Trigger(config)#ip ssh ?&lt;/P&gt;&lt;P&gt;  authentication-retries  Specify number of authentication retries&lt;/P&gt;&lt;P&gt;  break-string            break-string&lt;/P&gt;&lt;P&gt;  port                    Starting (or only) Port number to listen on&lt;/P&gt;&lt;P&gt;  rsa                     Configure RSA keypair name for SSH&lt;/P&gt;&lt;P&gt;  source-interface        Specify interface for source address in SSH connections&lt;/P&gt;&lt;P&gt;  time-out                Specify SSH time-out interval&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BGP_Trigger(config)#ip ssh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The feature you're talking about is in&lt;/P&gt;&lt;P&gt;12.3T, 12.4 and later.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Furthermore, I just want to disable des ssh &lt;/P&gt;&lt;P&gt;login, not changing it to version 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CCIE Security&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Dec 2007 17:21:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859022#M957919</guid>
      <dc:creator>cisco24x7</dc:creator>
      <dc:date>2007-12-30T17:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859023#M957920</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ssh version 2 does not even support DES, so changing your config to "ip ssh version 2" seems to solve your problem - like adam said.&lt;/P&gt;&lt;P&gt;If your IOS version doesn't support version 2, then you probably need to upgrade it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 05:27:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859023#M957920</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2007-12-31T05:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859024#M957921</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Let me re-phrase my question a little differently:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1-  How can I disable users from ssh into&lt;/P&gt;&lt;P&gt;the router with 3des?  I only want users&lt;/P&gt;&lt;P&gt;to ssh into my device with aes256?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2- I want users to login with only AES256/sha-1&lt;/P&gt;&lt;P&gt;only.  I do not want to use aes256/md5, as&lt;/P&gt;&lt;P&gt;seen below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[root@Linux]# ssh -v -c aes256-cbc -l cisco 192.168.1.1&lt;/P&gt;&lt;P&gt;OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f&lt;/P&gt;&lt;P&gt;debug1: Reading configuration data /etc/ssh/ssh_config&lt;/P&gt;&lt;P&gt;debug1: Applying options for *&lt;/P&gt;&lt;P&gt;debug1: Rhosts Authentication disabled, originating port will not be trusted.&lt;/P&gt;&lt;P&gt;debug1: ssh_connect: needpriv 0&lt;/P&gt;&lt;P&gt;debug1: Connecting to 192.168.1.1 [192.168.1.1] port 22.&lt;/P&gt;&lt;P&gt;debug1: Connection established.&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/identity type -1&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/id_rsa type -1&lt;/P&gt;&lt;P&gt;debug1: identity file /root/.ssh/id_dsa type -1&lt;/P&gt;&lt;P&gt;debug1: Remote protocol version 2.0, remote software version Cisco-1.25&lt;/P&gt;&lt;P&gt;debug1: no match: Cisco-1.25&lt;/P&gt;&lt;P&gt;debug1: Enabling compatibility mode for protocol 2.0&lt;/P&gt;&lt;P&gt;debug1: Local version string SSH-2.0-OpenSSH_3.5p1&lt;/P&gt;&lt;P&gt;debug1: SSH2_MSG_KEXINIT sent&lt;/P&gt;&lt;P&gt;debug1: SSH2_MSG_KEXINIT received&lt;/P&gt;&lt;P&gt;debug1: kex: server-&amp;gt;client aes256-cbc hmac-md5 none&lt;/P&gt;&lt;P&gt;debug1: kex: client-&amp;gt;server aes256-cbc hmac-md5 none&lt;/P&gt;&lt;P&gt;debug1: dh_gen_key: priv key bits set: 243/512&lt;/P&gt;&lt;P&gt;debug1: bits set: 500/1024&lt;/P&gt;&lt;P&gt;debug1: sending SSH2_MSG_KEXDH_INIT&lt;/P&gt;&lt;P&gt;debug1: expecting SSH2_MSG_KEXDH_REPLY&lt;/P&gt;&lt;P&gt;debug1: Host '192.168.1.1' is known and matches the RSA host key.&lt;/P&gt;&lt;P&gt;debug1: Found key in /root/.ssh/known_hosts:4&lt;/P&gt;&lt;P&gt;debug1: bits set: 522/1024&lt;/P&gt;&lt;P&gt;debug1: ssh_rsa_verify: signature correct&lt;/P&gt;&lt;P&gt;debug1: kex_derive_keys&lt;/P&gt;&lt;P&gt;debug1: newkeys: mode 1&lt;/P&gt;&lt;P&gt;debug1: cipher_init: set keylen (16 -&amp;gt; 32)&lt;/P&gt;&lt;P&gt;debug1: SSH2_MSG_NEWKEYS sent&lt;/P&gt;&lt;P&gt;debug1: waiting for SSH2_MSG_NEWKEYS&lt;/P&gt;&lt;P&gt;debug1: newkeys: mode 0&lt;/P&gt;&lt;P&gt;debug1: cipher_init: set keylen (16 -&amp;gt; 32)&lt;/P&gt;&lt;P&gt;debug1: SSH2_MSG_NEWKEYS received&lt;/P&gt;&lt;P&gt;debug1: done: ssh_kex2.&lt;/P&gt;&lt;P&gt;debug1: send SSH2_MSG_SERVICE_REQUEST&lt;/P&gt;&lt;P&gt;debug1: service_accept: ssh-userauth&lt;/P&gt;&lt;P&gt;debug1: got SSH2_MSG_SERVICE_ACCEPT&lt;/P&gt;&lt;P&gt;debug1: authentications that can continue: password&lt;/P&gt;&lt;P&gt;debug1: next auth method to try is password&lt;/P&gt;&lt;P&gt;cisco@192.168.1.1's password:&lt;/P&gt;&lt;P&gt;debug1: ssh-userauth2 successful: method password&lt;/P&gt;&lt;P&gt;debug1: channel 0: new [client-session]&lt;/P&gt;&lt;P&gt;debug1: send channel open 0&lt;/P&gt;&lt;P&gt;debug1: Entering interactive session.&lt;/P&gt;&lt;P&gt;debug1: ssh_session2_setup: id 0&lt;/P&gt;&lt;P&gt;debug1: channel request 0: pty-req&lt;/P&gt;&lt;P&gt;debug1: channel request 0: shell&lt;/P&gt;&lt;P&gt;debug1: fd 3 setting TCP_NODELAY&lt;/P&gt;&lt;P&gt;debug1: channel 0: open confirm rwindow 1024 rmax 4096&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Router&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can accomplish on a Linux box by modifying&lt;/P&gt;&lt;P&gt;the /etc/ssh/sshd_config file.  How can&lt;/P&gt;&lt;P&gt;I do the same thing in cisco IOS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 15:03:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859024#M957921</guid>
      <dc:creator>cisco24x7</dc:creator>
      <dc:date>2007-12-31T15:03:25Z</dc:date>
    </item>
    <item>
      <title>Re: only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859025#M957922</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need sshv2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think to completely cover all you want done you need to look at adding a AAA server or look into VPNs for more control.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 15:42:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859025#M957922</guid>
      <dc:creator>Adam Frederick</dc:creator>
      <dc:date>2007-12-31T15:42:25Z</dc:date>
    </item>
    <item>
      <title>Re: only allowing users to ssh in with 3DES</title>
      <link>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859026#M957923</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sshv2?  Can you elaborate on this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AAA or VPNs?  Can you also elaborate on this&lt;/P&gt;&lt;P&gt;as well?  How will AAA solve my disabling&lt;/P&gt;&lt;P&gt;3des and aes256/md5 issue?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Dec 2007 15:59:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/only-allowing-users-to-ssh-in-with-3des/m-p/859026#M957923</guid>
      <dc:creator>cisco24x7</dc:creator>
      <dc:date>2007-12-31T15:59:12Z</dc:date>
    </item>
  </channel>
</rss>

