|Mike Leone on 21 Jul 2010 07:21:15 -0700|
On 7/21/2010 9:55 AM, Jason Harlow had this to say:
ssh -v on the client side can be ok, but not as helpful as you might want. It might also help to run a debug sshd on the server side (sshd -d -p 1234) , and try connecting to that (ssh -p 1234) and look at the log on the server side. It tends to give more information.
I don't see a syslog, or an auth.log. None of the stuff I am used to seeing on a Debian system ... I always disliked RedHat. :-) I do see from /etc/syslog.conf that it should be writing to /var/log/messages, but I see no messages in there from this morning at all. And SSH looks like it's logging as facility AUTHPRIV. I've set the level to INFO. But ssh doesn't seem to be logging anything - I see no entries in /var/log/messages at all (since restarting the syslog).
The only reference I can find in any file in /var/log, is an entry in the "audit.log" file:
type=USER_LOGIN msg=audit(1279720255.145:2192): user pid=17322 uid=0 auid=0 msg='acct="FileCollector": exe="/usr/sbin/sshd" (hostname=?, addr=192.168.1.2, terminal=sshd res=failed)'
Also, double check that these aren't set to No or something other than ~/.ssh/authorized_keys #RSAAuthentication yes #PubkeyAuthentication yes #AuthorizedKeysFile .ssh/authorized_keys
All are enabled, and set to YES.
(Above are the defaults, if they're not set to anything...at least in the openSSH I'm using on Solaris)
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug