On Thu, 2003-03-06 at 18:17, Michael Wardle wrote: > On Fri, 2003-03-07 at 11:05, David Busby wrote: > > Run sshd and ssh in debug mode to see what the output is. > > It should notify you when its trying different auth mechanisms. > > Perhaps the auth_key you have to your server was erased when doing the > > replacement of the SSHD package? > > I've run both in debug mode, and nothing strikes me as wrong, but then > I've never found OpenSSH's debug output very useful. > > I removed the server's and the client's keys from my authorized_keys > then told SSH to add them when I next connected, so I think I've covered > that possibility. >
if you remove the public key from the servers authorized_keys file then key based authentication cannot take place. did you by chance regen a key on the client side? make sure that the client user has the correct public key in the server user's ~/.ssh/authorized_keys file. I have found that running the server with -dd usually gives me the information I need to figure out what is happening. Much more useful for in depth authentication debugging. more d's = more detailed debugging. One thing that will bite you that only debugging from the server will detect is permisions too loose on the .ssh dir and auth._keys file. let us know what you find. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
