Re: How to re-enable ssh logins

["Robert G. (Doc) Savage" <dsavage@peaknet.net>]

On Mon, 2013-10-21 at 23:03 -0400, Sarah Harvey wrote:
> Have you looked through /var/log/auth.log to see what the specific
> error is?
> 
> 
> (sudo tail /var/log/auth.log -n 20)
> 
> 
> I'm not sure how your user authentication system is set up, but it
> could also be a pam issue. Check /etc/pam.d/ssh to see if the relevant
> authentication system is set (pam_unix.so for /etc/{passwd,shadow},
> pam_ldap.so for LDAPs, etc.)
> 
> 
> Without more details, not sure where else to point you towards.
> Generally auth.log would be a good start to see what error is being
> thrown.
> 
> 
> How were you logging in before?

Sarah,

Welcome to my frustration. There is no /var/log/auth.log -- either on
the pod's CentOS 6.4 built by Protocase or on my CentOS 6.4 workstation.

Neither has an /etc/pam.d/ssh. Both have the same /etc/pam.d/sshd:

        # cat /etc/pam.d/sshd
        #%PAM-1.0
        auth	   required	pam_sepermit.so
        auth       include      password-auth
        account    required     pam_nologin.so
        account    include      password-auth
        password   include      password-auth
        # pam_selinux.so close should be the first session rule
        session    required     pam_selinux.so close
        session    required     pam_loginuid.so
        # pam_selinux.so open should only be followed by sessions to be executed in the user context
        session    required     pam_selinux.so open env_params
        session    optional     pam_keyinit.so force revoke
        session    include      password-auth

How was I logging in before? The pod is a brand new Backblaze box just
shipped in from the manufacturer (in Newfoundland!). It came with CentOS
6.4 pre-installed. As I said in my first e-mail, I originally hoped to
connect only power and Ethernet to this box and set it up headless using
ssh. Plan B adds an old PS/2 keyboard, USB mouse, VGA monitor balanced
precariously on top of this 68lb monster. Quite frankly, it's been a
PITB reconfiguring it this way.

--Doc




-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.