Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
3 Show appreciation through votes. Thanks not necessary on SO/SX http://meta.stackoverflow.com/a/3021/186664
source | link

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

2 delete thanks
source | link

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

thanks.

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

thanks.

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

1
source | link

DenyHosts and no-ip.com

I recently installed DenyHosts and after a few remote logins I noticed that sshd: 8.23.224.110 had been added to the host.deny file after /var/log/auth.log showed a few sshd: Did not receive identification string from 8.23.224.110. This appears to be no-ip.com.

I use ddclient to dynamically update my ip-address to point to my hostname at no-ip.com; something like myhostname@no-ip.org so that instead of having to ssh to a dynamic ip I can always just connect to the above host.

I don't understand why 8.23.224.110 would be trying to connect to my ssh service however, can anyone shed some light on this? Is it some kind of by product of me ssh'ing to the no-ip hosted hostname? Is it likely to be problematic now DenyHosts has banned it?

thanks.