<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Topic &#x27;Re: Who keeps their router&#x27;s SSH port open?&#x27; in forum &#x27;Cisco&#x27; - dslreports.com</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953313</link>
<description></description>
<language>en</language>
<pubDate>Wed, 19 Jun 2013 10:38:01 EDT</pubDate>
<lastBuildDate>Wed, 19 Jun 2013 10:38:01 EDT</lastBuildDate>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27968726</link>
<description><![CDATA[HELLFIRE posted : Thanks for that as well  nschlutter <A HREF="/useremail/u/767105"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A><br><br><div class="bquote"><p>Cisco refers to the second feature as &#147;quiet mode&#148; and also includes an option to specify an access-list which is exempted during the block period.</p></div><div class="bquote"><p>The second line of configuration will reference the access-list created above to never block the specified networks.</p></div>A bit vague, then again some stuff on how Cisco does it is vague... till you put it into practice.  I'm not referring to<br>the way you write it up  nschlutter <A HREF="/useremail/u/767105"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>, it's just personal experience with the way Cisco writes up the way<br>their commands (are supposed) to work.<br><br>Also, a bit of a personal gripe... why'd it take Cisco till 12.4T to introduce this command...<br><br>Regards]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27968726</guid>
<pubDate>Fri, 01 Feb 2013 10:54:31 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27965548</link>
<description><![CDATA[Network Guy posted : Interesting you post this now. I'm reading a Cisco Press book to get my CCNA Security and I just read past this very same topic explaining that command.<br><br>Cool stuff :D]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27965548</guid>
<pubDate>Thu, 31 Jan 2013 13:19:05 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27964805</link>
<description><![CDATA[nschlutter posted : Another option is to enable some of the enhanced security features mentioned in this <a href="http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_login_enhance.pdf">document</a><br><br>Basically these features allow you to deny logins after a certain number of failed logins as well as insert a delay between login attempts. <br><br>The quiet-mode can be accomplished with the commands:<br><br><code>login block-for X attempts Y within Z</code><br><br>An access-list can also be created that allows logins from certain network(s) during the quiet-mode time. The configuration for this looks like:<br><br><code>login quiet-mode access-class ACL</code><br><br>The delay is accomplished with the command:<br><br><code>login delay X</code><br><br><a href="http://www.the-lan-man.net/wordpress/2013/cisco-ios-login-enhancements/">I wrote a blog post about this as well if you're looking for a slightly more wordy version</a>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27964805</guid>
<pubDate>Thu, 31 Jan 2013 10:25:01 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27961275</link>
<description><![CDATA[Network Guy posted : The attacks seem to be done and over with from what I can see in the NAT stats and the ACL lists. I setup this 1841 last week for the first time ever. I created the ACL keeping in mind that if I opened 22 over the WAN that it would equate to hanging meat for the piranhas, but I forgot to apply it to the VTY lines.<br><br>What I should do is log any attempts that match the ACL rules applied to the VTY lines just to see what's going on.<br><br>So far from what I can see, it's been relatively quiet.<br><br><code><br>Extended IP access list 100<br>    10 deny ip 10.17.12.0 0.0.0.255 10.18.12.24 0.0.0.7 (4272 matches)<br>    20 permit ip 10.17.12.0 0.0.0.255 any (38774 matches)<br>Extended IP access list 101 ---- This is the one applied to VTY lines ----<br>    10 permit tcp host xxx any eq 22 (8 matches) ---- This is for my access from work ----<br>    20 permit tcp 10.17.12.0 0.0.0.255 any eq 22 (4 matches)<br>    30 deny ip any any (39 matches)<br>Extended IP access list 110<br>    5 permit tcp 10.17.12.0 0.0.0.255 10.18.12.24 0.0.0.7<br>    10 permit ip 10.17.12.0 0.0.0.255 10.18.12.24 0.0.0.7<br>router#<br></code><br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27961275</guid>
<pubDate>Wed, 30 Jan 2013 10:32:34 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27961055</link>
<description><![CDATA[battleop posted : If you are being attacked you need to setup some ACLs.<br><br>This is a sample from one of my routers.  We have a /24 that is used for our support group, management servers, snmp, etc.  So I just created a single ACL for everything like SSH, SNMP etc and then allow access only from that one /24.  <br><br>access-list 50 remark remote-access<br>access-list 50 permit 216.x.x.0 0.0.0.255<br>access-list 50 deny   any<br><br>line vty 0 4<br> access-class 50 in<br> exec-timeout 120 0<br><small>--<br>I do not, have not, and will not work for AT&T/Comcast/Verizon/Charter or similar sized company.</small>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27961055</guid>
<pubDate>Wed, 30 Jan 2013 09:42:56 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27960375</link>
<description><![CDATA[HELLFIRE posted : @jh2010<br>I still have the CPU screenshot of what my first attempt at leaving my SSH port open to the world at large looked like,<br>plus the logfiles to back it up.... fun times indeed.<br><br>@nosx<br>Wanna give a breakdown of what each line of that config does?  Some of the commands I've never seen before.<br>But it looks interesting...<br><br>Regards]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27960375</guid>
<pubDate>Wed, 30 Jan 2013 00:09:27 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27959639</link>
<description><![CDATA[nosx posted : For SSH its simpler to avoid scans by using the rotary feature to move ssh to a new port other than 22.<br><br>Additional security through obscurity is available by using a "knock" rotary configuration for your router. You have to "knock"/authenticate on a given TCP port, and then you can initiate a new SSH session for the next say 60 seconds (dynamic ACL knock entry). This is useful to prevent scan / attack of hosts behind your router that you may want to NAT to ssh/rdp/vnc/whatever to.<br><br>ip ssh port 2222 rotary 1<br>username knock secret 5 $1$whatever<br>username knock autocommand access-enable host timeout 1<br>ip access-list extended ACL_PROTECT_WAN_IN<br> dynamic knock permit tcp any any eq 3389 22 log-input<br> deny   ip any any]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27959639</guid>
<pubDate>Tue, 29 Jan 2013 19:42:03 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27958243</link>
<description><![CDATA[jh2010 posted : If you leave SSH open to the Internet, then it is possible to get dos'ed if all lines are kept open. You will not be able to login(except via the console).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27958243</guid>
<pubDate>Tue, 29 Jan 2013 12:42:01 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27957063</link>
<description><![CDATA[HELLFIRE posted : I do.  Control Plane Policing gets alot of the ones set to connect at too high a rate, thought I should probably<br>retune my thresholds lower now.<br><br>Are you logging your SSH attempts?  Ones that just don't get the hint I nullroute to the bit bucket (and<br>their subnet too) for a very permanent solution.  Sending emails to their ISP's abuse email is the highlight<br>of the day.<br><br>@cramer<br>I'll have to try your idea as well and see how it goes.<br><br>Regards]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27957063</guid>
<pubDate>Tue, 29 Jan 2013 00:00:02 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27954670</link>
<description><![CDATA[TomS_ posted : Im thinking the same thing. My FreeBSD box is constantly being "attacked" from all over the place. This could be quite amusing. :-)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27954670</guid>
<pubDate>Mon, 28 Jan 2013 11:48:25 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27954254</link>
<description><![CDATA[Network Guy posted : <div class="bquote"><said>said by <a href="/profile/1452065" onClick="this.blur(); return popup(event,'/uidpop?ajh=1&uid=1452065');">cramer</a>:</said><p> I do when I'm bored. :-)  And I create a priv level 0 user named "root" with password "root"... sit back and watch their scripts fail.  None of these idiots know what to do when they find something that's not tHe LiNuX.<br><br>(generally, NEVER leave port 22 open to the internet.  Even if it's not an SSH server.)<br> </p></div>I should do this for kicks. My 1841 at home isn't all that busy as it is. :D]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27954254</guid>
<pubDate>Mon, 28 Jan 2013 09:45:24 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953535</link>
<description><![CDATA[DaSneaky1D posted : Nothing wrong with leaving it open to the world. Just have to keep a proper access list.<br><br>It'll be much safer if you only allow a specific range of IPs access to the router(s).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953535</guid>
<pubDate>Sun, 27 Jan 2013 23:40:08 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953477</link>
<description><![CDATA[cramer posted : I do when I'm bored. :-)  And I create a priv level 0 user named "root" with password "root"... sit back and watch their scripts fail.  None of these idiots know what to do when they find something that's not tHe LiNuX.<br><br>(generally, NEVER leave port 22 open to the internet.  Even if it's not an SSH server.)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953477</guid>
<pubDate>Sun, 27 Jan 2013 23:03:59 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953378</link>
<description><![CDATA[Network Guy posted : Doh! I checked the VTY lines. I created the ACL but forgot to set it to the lines.<br><br>The script kiddie from China is no longer in my NAT statistics table. :D]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953378</guid>
<pubDate>Sun, 27 Jan 2013 22:25:10 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953346</link>
<description><![CDATA[Network Guy posted : Yes. I only allow local internal subnet and one IP address from my job to access all VTY lines.<br><br>The only thing that worries me is that in order to get the ACL to work I had to allow to any that equals 22 and apply it inbound to the VTY lines. I wanted to specify an IP address in the destination but as far as I know, you can't set an IP address to a VTY line.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953346</guid>
<pubDate>Sun, 27 Jan 2013 22:16:02 EDT</pubDate>
</item>

<item>
<title>Re: Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953334</link>
<description><![CDATA[state posted : No access lists?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Re-Who-keeps-their-routers-SSH-port-open-27953334</guid>
<pubDate>Sun, 27 Jan 2013 22:11:56 EDT</pubDate>
</item>

<item>
<title>Who keeps their router&#x27;s SSH port open?</title>
<link>http://www.dslreports.com/forum/Who-keeps-their-routers-SSH-port-open-27953313</link>
<description><![CDATA[Network Guy posted : My 1841 is apparently falling victim to a dictionary attack via SSH. I happened to check the NAT statistics and see there's an IP address from China making a large number of inbound connections to my router via SSH.<br><br>Yes, I have SSH open for my convenience. Apparently, I probably should only SSH into my router via VPN.<br><br>Who keeps their router's SSH port open to the world?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/Who-keeps-their-routers-SSH-port-open-27953313</guid>
<pubDate>Sun, 27 Jan 2013 22:05:21 EDT</pubDate>
</item>

</channel>
</rss>
