On Sat, 11 Sep 1999, Jon Lewis wrote: > I broke one of my 5.2 systems at home today to debug this. What I found > is that pam support seems to have been added into Xwrapper, and that it > comes with an /etc/pam.d/xserver file that by default only allows root to > start X...and AFAICT, no instructions for changing that behavior. I > messed around with /etc/pam.d/xserver and got it to allow anyone to start > X, but I'm not happy with the way I did it. I don't feel like tracking > down the pam docs (/usr/doc/pam-0.64/ is awfully barren) right now, so > I'll probably look at this more tonight. Looked at this a little more, and now I think it's definitely a bug. When Red Hat released XFree86-3.3.5 for 5.2 and 6.0, they included (in both releases) pam support in Xwrapper that's been standard on 6.0 but was new to 5.2. 6.0 does come with some documentation on console.apps and pam_console.so in /usr/doc/rhl-install-guide-en-6.0/manual/doc087.html. However, 5.2 knows nothing of this. 5.2 (and pam-0.64-4 which is the latest pam update for 5.2) don't have /lib/security/pam_console.so, so the /etc/pam.d/xserver file that comes in XFree86-3.3.5-0.5.2.i386.rpm is broken.
*** This bug has been marked as a duplicate of 5001 ***