<?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 redirection? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263822#M1076906</link>
    <description>&lt;P&gt;No, transport preferred none should be that way.&lt;/P&gt;&lt;P&gt;Transport output SSH has been shut down and I'm still getting those log entries.&lt;/P&gt;&lt;P&gt;ip ssh source-interface,&amp;nbsp; doesn't seem to have anything to do with it.&lt;/P&gt;&lt;P&gt;From another user response: "The command "ip ssh source-interface" controls the sessions that are initiated &lt;STRONG&gt;*from*&lt;/STRONG&gt; your switch/router. They don't change how you ssh to that device."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 25 Dec 2020 22:28:54 GMT</pubDate>
    <dc:creator>kirm</dc:creator>
    <dc:date>2020-12-25T22:28:54Z</dc:date>
    <item>
      <title>SSH redirection?</title>
      <link>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263559#M1076902</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I have a security question if you'd like to chime in. First, here's my VTY and ACL config:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ip access-list extended SSH_Access_Control&lt;BR /&gt;permit tcp 192.168.1.0 0.0.0.255 any eq 22&lt;BR /&gt;deny tcp any any eq 22 log&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;line vty 0 4&lt;BR /&gt;access-class SSH_Access_Control in&lt;/P&gt;&lt;P&gt;transport preferred none&lt;BR /&gt;transport input ssh&lt;BR /&gt;transport output ssh&lt;/P&gt;&lt;P&gt;I'm using aaa.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cut out what I consider to be extraneous info but please let me know if you need to know more.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now here's the log:&lt;/P&gt;&lt;P&gt;Dec 23 20:37:18 local 270: Dec 23 20:37:17.687: %SEC-6-IPACCESSLOGP: list SSH_Access_Control denied tcp 81.161.63.103(35532) -&amp;gt; 33.252.197.152(22), 1 packet&lt;/P&gt;&lt;P&gt;And there are lots of these.&lt;/P&gt;&lt;P&gt;So 81.161.63.103, which is either a Chinese or Russian hacker, is...redirecting...I'm not sure...SSH to a US gov server(33.252.197.152) using my 2901?!?!&lt;/P&gt;&lt;P&gt;Man, I hope not.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Two questions if I may:&lt;/P&gt;&lt;P&gt;Is "transport output ssh" necessary?&lt;/P&gt;&lt;P&gt;And what's going on with that log?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;And a bonus question:&lt;/P&gt;&lt;P&gt;Why doesn't this work:&lt;/P&gt;&lt;P&gt;5 permit tcp 192.168.1.0 0.0.0.255 host 192.168.1.254 eq 22 (2 matches)&lt;/P&gt;&lt;P&gt;If I put the host in like above I can't SSH to the router.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Let me know if you have any other input please.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;You know, the wider you open your eyes the more you wish you would have kept them shut. My router is just getting hammered by Chinese and Russian IPs. Yikes.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2020 19:11:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263559#M1076902</guid>
      <dc:creator>kirm</dc:creator>
      <dc:date>2020-12-24T19:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: SSH redirection?</title>
      <link>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263612#M1076904</link>
      <description>&lt;P&gt;Try below config ( always make changes from console)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ine vty 0 4&lt;BR /&gt;access-class SSH_Access_Control in&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;no transport preferred none&lt;/STRONG&gt;&lt;BR /&gt;transport input ssh&lt;BR /&gt;&lt;STRONG&gt;no transport output ssh&lt;/STRONG&gt;&amp;nbsp; ( you do not need this , since this is used to use from this device to ssh to outside)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;since SSH enable listen all interface, if you like to restrict you can do with source interface.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;(config)# &lt;STRONG&gt;ip ssh ?&lt;/STRONG&gt;
 authentication-retries&amp;nbsp;Specify number of authentication retries
 Port&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Starting (or only) port number to listen
                        on
 Rsa&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Configure RSA keypair name for SSH&amp;nbsp; 
 source-interface &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Specify interface for source address in SSH
                        connections
 time-out&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Specify SSH time-out interval
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Dec 2020 01:02:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263612#M1076904</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-12-25T01:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: SSH redirection?</title>
      <link>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263822#M1076906</link>
      <description>&lt;P&gt;No, transport preferred none should be that way.&lt;/P&gt;&lt;P&gt;Transport output SSH has been shut down and I'm still getting those log entries.&lt;/P&gt;&lt;P&gt;ip ssh source-interface,&amp;nbsp; doesn't seem to have anything to do with it.&lt;/P&gt;&lt;P&gt;From another user response: "The command "ip ssh source-interface" controls the sessions that are initiated &lt;STRONG&gt;*from*&lt;/STRONG&gt; your switch/router. They don't change how you ssh to that device."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 25 Dec 2020 22:28:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263822#M1076906</guid>
      <dc:creator>kirm</dc:creator>
      <dc:date>2020-12-25T22:28:54Z</dc:date>
    </item>
    <item>
      <title>Re: SSH redirection?</title>
      <link>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263843#M1076907</link>
      <description>&lt;P&gt;The "SSH_Access_Control denied tcp" log entries are the ACL doing its job. Logging any intern-facing ACL will always give you a long list of attempts by scripts from all around the world trying to access your system or (as you observed) use it to access other systems.&lt;/P&gt;
&lt;P&gt;You may want to refer here for best practices:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/ip/access-lists/13608-21.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/ip/access-lists/13608-21.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;This is a good third party site with some sample configs:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.techspacekh.com/security-hardening-cisco-router/" target="_blank"&gt;http://www.techspacekh.com/security-hardening-cisco-router/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Dec 2020 02:42:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263843#M1076907</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-12-26T02:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: SSH redirection?</title>
      <link>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263872#M1076908</link>
      <description>&lt;P&gt;yes agreed, only trying to tweak my best to see if any security hole to fix. not to use your device as transit to connect to other devices.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Then ACL is the correct and the outside interface is blocking the connection - that is expected, just like any other Firewall. (if this is connected directly to interface on wan side interface - this is expected.)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Dec 2020 09:10:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-redirection/m-p/4263872#M1076908</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2020-12-26T09:10:35Z</dc:date>
    </item>
  </channel>
</rss>

