Comments on: ssh_exchange_identification: Connection closed by remote host http://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/ baking cakes with CakePHP Tue, 29 Sep 2009 06:55:31 +0000 http://wordpress.com/ hourly 1 By: cakebaker http://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1790 cakebaker Wed, 27 Sep 2006 12:55:40 +0000 https://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1790 @Strider: Thanks for the tips :) @Strider: Thanks for the tips :)

]]> By: Strider http://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1783 Strider Tue, 26 Sep 2006 16:40:35 +0000 https://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1783 You're better off looking at using DenyHosts (http://denyhosts.sourceforge.net/) as it will block known SSH boots. Also add your own IP to /etc/hosts.allow in the form of IP addr/Netmask. I also restrict password login in SSH and use shared keys. :) Avoids the problem with burte force password attacks. You’re better off looking at using DenyHosts (http://denyhosts.sourceforge.net/) as it will block known SSH boots.

Also add your own IP to /etc/hosts.allow in the form of IP addr/Netmask.

I also restrict password login in SSH and use shared keys. :) Avoids the problem with burte force password attacks.

]]> By: MJR/slef http://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1352 MJR/slef Wed, 16 Aug 2006 07:59:36 +0000 https://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1352 A NAT device can limit your checks: you can either allow or disallow connections which appear to be from the NAT device. Then again, most NAT devices I have seen can do firewalling too, so that's not a major problem. Just another place to set access control... A NAT device can limit your checks: you can either allow or disallow connections which appear to be from the NAT device. Then again, most NAT devices I have seen can do firewalling too, so that’s not a major problem. Just another place to set access control…

]]> By: cakebaker http://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1351 cakebaker Wed, 16 Aug 2006 06:57:14 +0000 https://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1351 @MJR/slef: Thanks for the warning, I changed it. Is it also an issue if a NAT device is used? @MJR/slef: Thanks for the warning, I changed it. Is it also an issue if a NAT device is used?

]]> By: MJR/slef http://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1343 MJR/slef Tue, 15 Aug 2006 16:11:26 +0000 https://cakebaker.wordpress.com/2006/08/15/ssh_exchange_identification-connection-closed-by-remote-host/#comment-1343 Warning: that line will allow SSH access from any IPv4 address and there are a lot of scanners out there (machines which just try to guess logins with brute force). If you can, only put hosts, domains or networks which you want to have SSH access in there. Warning: that line will allow SSH access from any IPv4 address and there are a lot of scanners out there (machines which just try to guess logins with brute force). If you can, only put hosts, domains or networks which you want to have SSH access in there.

]]>