sadly, its pretty common - one of the "common currency" ssh haxxor scripts uses that disconnect string, and usually tries to log in as guest/guest or test/test before trying a brute force attack.
Each entry should *also* have a number in square brackets, which is the process ID - once you see the byebye, you can use that number with grep to locate any other records in the log for the same process ID - its also worth grepping on the IP address given, to see if there are any other threads that share that IP.
problematic lines will be something like "failed password" - showing attempts to log in.
Main Topics
Browse All Topics





by: tl121000Posted on 2009-04-11 at 07:57:25ID: 24122235
These as you know are hacking attempts, since SSH is a well known port (22).
you can tighten your firewall to allow only valid users
or
check this out...
http://www.it-slav.n et/blogs/? p=183