Re: problem with PAM and login.defs in shadow-4.0.9

On Mon, 27 Jun 2005, Andreas Haumer wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi!
>
> I just tried shadow-4.0.9 and found a problem with the way
> login handles /etc/login.defs when PAM support is enabled.
>
> I noticed that def_table in file getdef.c now has many options
> removed if USE_PAM is defined. Function def_find() gives an
> error if it is called with an option which is not present in
> def_table and so any "pam" option in /etc/login.defs produces
> an error message. This is fine, as these options ought to be
> handled by corresponding pam modules, anyway.
>
> But: The login program itself unconditionally tries to lookup
> some of the "pam" options, namely
>
> in login.c:main()
> ULIMIT
> ENV_TZ
> ENV_HZ
> in setupenv.c:setupenv()
> ENV_SUPATH
> ENV_PATH
> QMAIL_DIR
> MAIL_DIR
> MAIL_FILE
>
> All these lookups are done via a call to the def_find()
> function and so also print an ugly error messages if pam is
> used.

Seems you are right and this must be fixed in next version (by move to 
PAM dependent part) because setting limits and all enviroment varables 
this is task for PAM modules.
If you want help on fix this .. be my guest.

kloczek
-- 
-----------------------------------------------------------
*Ludzie nie majÂą problemĂłw, tylko sobie sami je stwarzajÂą*
-----------------------------------------------------------
Tomasz KÂłoczko, sys adm @zie.pg.gda.pl|*e-mail: [email protected]*