| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Mark Knecht wrote: |
| 5 |
> OK, knowing as you all do that I'm a non-admin sort of person these |
| 6 |
> sort of instructions - the |
| 7 |
> 2 paragraphs at the end - scare me. I hate having to guess what anyone means. |
| 8 |
> |
| 9 |
> lightning pam.d # qfile -o /etc/pam.d/* |
| 10 |
> /etc/pam.d/gdmconfig |
| 11 |
> /etc/pam.d/xdm |
| 12 |
> lightning pam.d # |
| 13 |
> |
| 14 |
|
| 15 |
I was having the same problems earlier in the week. The solution is |
| 16 |
actually pretty simple. The output above indicates that xdm and |
| 17 |
gdmconfig aren't being used any longer - they're orphans. I just moved |
| 18 |
the files elsewhere (for temporary safe-keeping), and upgraded PAM, and |
| 19 |
there were no issues. All the files that used the obsolete functions |
| 20 |
were upgraded some time ago apparently - but if you have a system that |
| 21 |
has been upgraded year-after-year apparently there are orphan files that |
| 22 |
date WAY back... |
| 23 |
|
| 24 |
However, I agree that PAM is one of those things that everybody depends |
| 25 |
on but otherwise seems to behave like black magic for most people. I've |
| 26 |
yet to see a guide on PAM that actually makes it easy to understand. |
| 27 |
(There are TONS of guides that ATTEMPT to make it easy to understand, |
| 28 |
but every one I've seen falls far short). I considered it a major |
| 29 |
accomplishment when I was able to hack my sshd PAM config to restrict |
| 30 |
logins to a list of particular accounts... |
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 33 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 34 |
|
| 35 |
iD8DBQFHLbS3G4/rWKZmVWkRArPOAJwPJuIUe8tJkacz5jmyzaImNFaTjgCdF8k/ |
| 36 |
++g0HXiS7/ZPaUOMk6YY+OA= |
| 37 |
=q/hy |
| 38 |
-----END PGP SIGNATURE----- |
Archives