i suspect you are just not looking at the right file (auth log vs. a daemon log) and are only looking at the authentication requests that get passed down to your authentication library (pam?).
Re:SSH server 0-day exploit
by tedunangst on Tuesday July 07, 2009 @08:11PM
(#692927)
If the IP is spoofed, how are your reply packets getting back to it?
Re:SSH server 0-day exploit
by jlangenauer on Tuesday July 07, 2009 @09:06PM
(#692993)
Spoofed is probably the wrong word - through an irrelevant IP address is a better way to put it(perhaps someone's compromised computer on a botnet acting as a proxy).
However, after it's done that repeatedly (presumably doing some sort of sniffing to work out exactly which version of sshd is running), it then attempts to login. Here's the interesting bit: when it tries to login with a user than doesn't exist, instead of just generating the
sshd also outputs another log entry, directly afterwards: which I haven't seen before. I'm not particularly au fait with the internals of sshd, but I would suspect that this new (well, if it is new) script has found an exploit in the part of SSHD which (logically) checks if a user exists first, but the login is being rejected deeper in sshd, when it tries to do the actual authentication.(All the above is speculation, however: I'm no expert on SSH)