is ${PATH} in pam_env.conf supposed to see PATH set by login.defs?

["Daniel B." <dsb@smart.net>]

In /etc/security/pam_env.conf, is ${PATH} supposed to "see" the value
of PATH set by /etc/login.defs?

If I set PATH in login.defs (using ENV_PATH=xxx) and set PATH=${PATH}:yyy
in pam_env.conf, the setting from login.defs doesn't show up (PATH gets
set to ":yyy").

If I remember correctly (I looked at the code a while ago), login reads
login.defs first and calls PAM second, but when it calls PAM, it doesn't 
pass to PAM the settings from login.defs, so when PAM evaluates ${PATH}, 
it apparently doesn't find any value.  (It doesn't see any inherited 
value, but I assume that's intentional, for security.)


Is that behavior (${PATH} in pam_env.conf not "seeing" a value set by
login.defs) correct or is it a bug?

(This is in woody, with libpam-modules version 0.72-35 and 
login version 20000902-12.)


Thanks,
Daniel
-- 
Daniel Barclay
dsb@smart.net