Red Hat Bugzilla – Bug 498493
New pam stack configuration requires *much* better documentation
Last modified: 2010-06-28 08:17:55 EDT
Description of problem:
The new pam stack layout is quite different from previous ones, quite notably changing system-auth does not make you able to login via gdm if you added a custom pam module. That's because gdm, does not even look into what was once the "common" pam stack.
I suggest that system-auth/system-auth-ac includes a *prominent* notice in the very first few lines that point to a README file installed by default in the system and that explain carefully:
a) how the new pam stacks are laid out
b) how to add your own custom pam module if you need to do so
total confusion by any admin used to add a custom pam module up to F10
at least documentation pointed by system-auth (the place any admin would look into as the first thing
I think this should be a blocker for F11
Just to add some context.
This bug came out after a long discussion with Ray on system-auth vs password-auth
Today was SSSD test day and I was trying to test pam_sss/nss_sss to login also via GDM.
It wasn't immediately evident why my changes to system-auth were not seen by GDm and a lot of confusion arise trying to understand why.
Personally I would have left system-auth as the central password-only pam stack so that admins (and installation tools of third party apps) that were familiar with changing system-auth to add their custom pam modules wouldn't get utterly confused.
However, given we are quire late in the development process, I understand that it may be difficult to change what we have for F11 GA.
However, at the very least we should make it easy for an admin that is confused about why something doesn't work to understand what's going on.
The first thing an admin familiar with Fedora/Red Hat distributions does to manually check the pam stack is a vim /etc/pam.d/system-auth
That's why I think system-auth should carry a prominent notice that redirect to a README that explain all the changes in F11 (possibly why we made them) and how to cope with them.
There should certainly be something in the release notes...
I actually added it to the release notes here:
a few minutes ago and came to this bug to point that out only to see comment 2.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.