I've seen those 'failures' for quite some time...long before the current SSH update. The initial process attempts to log in the user via some passwordless method (like publickey)...when that fails, it logs that failure, and then goes on to the password option. It's normal operation...might as well leave it be. On Fri, 1 Aug 2003, Steve Snyder wrote: > Since updating to the new OpenSSH RPMs a few days ago, I get authentication errors on login. It looks like this: > > Aug 1 06:19:39 helios sshd(pam_unix)[1632]: authentication failure; logname= uid=0 euid=0 tty=NODEVssh ruser= rhost=mercury.snydernet.lan user=root > Aug 1 06:19:50 helios sshd(pam_unix)[1632]: session opened for user root by (uid=0) > > What I now see when attempting to log in is a very brief delay (during which the authentication fails, and the failure logged), then a successful login. > > (BTW, this behavior is also seen on RHL v7.3 with the updates RPMs released for it.) > > Is there a way to pacify the new OpenSSH code to avoid these bogus failures? If so, what do I need to change? > > Thanks. > > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@xxxxxxxxxxxxxxxxx with a message of: subscribe -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
