http://blfs-bugs.linuxfromscratch.org/show_bug.cgi?id=1491
Summary: Shadow and PAM
Product: Beyond LinuxFromScratch
Version: a-SVN
Platform: PC
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: BOOK
AssignedTo: blfs-book@linuxfromscratch.org
ReportedBy: [EMAIL PROTECTED]
QAContact: blfs-book@linuxfromscratch.org
I have found one situation where it doesn't work as it did. su used to get its
PATH from /etc/login.defs using ENV_PATH and ENV_SUPATH. These are no longer
available and according to the mailing list, are pam's responsibility. So the
path after su or su <user> is "/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:."
(default path coded in Bash source). This does not affect "su -" as that
sources /etc/profile. The PATH can be set by the pam_env.so module by editing
/etc/security/pam_env.conf:
PATH DEFAULT=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin \
OVERRIDE=${PATH}
and adding pam_env.conf to the auth section of /etc/pam.d/su.
I have not found a way to drop in a default PATH for root when su is used.
Under these conditions, "su -" is the only sure way to get a root path.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
