sshd logs on fedora

[benjeeeboy]

I am having some trouble logging in as anything other than root through ssh in fedora core 3 and was wondering where I could find the ssh logs.

I haven't been able to find any mention of any log name other than 'sshd.log' and slocate doesnt find that.

Edited January 23, 2005 by benjeeeboy

[markwolfe Veteran]

Run system-logviewer, and your "Security Log" will show your ssh logins. However, if you have been compromised by a skilled cracker, your logs will likely be altered. :(

Do you have a strong password? Have you applied your updates? (the basic questions) :)

Finally, what problems are you having, exactly, with your normal user account?

You can reset your password on there, if there is a login problem that way. Also try logging in at a console (CTRL+ALT+F2) and see if your login is successful there.

[hornett]

Perhaps you've set something wrong in /etc/ssh/sshd_config.

I think perhaps you need to add a line with "AllowUsers <your username>".

[markwolfe Veteran]

Perhaps you've set something wrong in /etc/ssh/sshd_config.

I think perhaps you need to add a line with "AllowUsers <your username>".

585339795[/snapback]

Hah! I was just coming back to make a recommendation to secure or shutdown sshd (if it wasn't used by the original poster).

You got it covered, though. :D

[ootput]

sshd_config should be the first place that you check.

If you're implementing pam, make sure you also check /etc/pam.d/sshd (or similar location.)

[benjeeeboy]

My sshd_config looks fine, I allow the users that I want to.

I don't know much about the pam configurations though.

#%PAM-1.0
auth       required     pam_stack.so service=system-auth
auth       required     pam_nologin.so
account    required     pam_stack.so service=system-auth
password   required     pam_stack.so service=system-auth
session    required     pam_stack.so service=system-auth

The pam_nologin.so thingy looks like it should probably be something different, but what would I change it to?

P.S. I'm not running x so i can't use system-logviewer, since it seems to be graphical.