I get the same result as Kristian Erik Hermansen above, namely that login is rejected by pam_securetty. However, I do not quite see why pam_securetty should be run.
So, if I am not mistaken, pam_securetty should only be run for the "login" service, not for gdm.
Also, /usr/share/doc/libpam-doc/html/pam-6.html#ss6.23 states for the pam_securetty module: "Provides standard Unix securetty checking, which causes authentication for root to fail unless PAM_TTY is set to a string listed in the /etc/securetty file. For all other users, it succeeds."
So pam_securetty should not be run at all, and it should certainly not fail.
Isn't this a PAM bug?
I get the same result as Kristian Erik Hermansen above, namely that login is rejected by pam_securetty. However, I do not quite see why pam_securetty should be run.
> grep -r pam_securetty /etc/pam.d d/login: auth requisite pam_securetty.so
/etc/pam.
So, if I am not mistaken, pam_securetty should only be run for the "login" service, not for gdm. doc/libpam- doc/html/ pam-6.html# ss6.23 states for the pam_securetty module: "Provides standard Unix securetty checking, which causes authentication for root to fail unless PAM_TTY is set to a string listed in the /etc/securetty file. For all other users, it succeeds."
Also, /usr/share/
So pam_securetty should not be run at all, and it should certainly not fail.