Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 70764 - pam-0.77-r1 breaks environment when you login via sshd and su -l to root
Summary: pam-0.77-r1 breaks environment when you login via sshd and su -l to root
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: PAM Gentoo Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-11 03:07 UTC by Alexander Stoll
Modified: 2005-02-25 11:47 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Stoll 2004-11-11 03:07:50 UTC 
The changes in pam_env.conf for pam-0.77-r1 break environment when you log in via sshd as user and make "su -l" to root. A cd to $HOME fails because $HOME is no longer set...

Reproducible: Always
Steps to Reproduce:
1. log in as user via sshd
2. make su -l to become root
3. type "cd" into Terminal



Expected Results:  
set complete enviroment as former versions

as a workaround set $HOME in your .profile
Comment 1 ic+gentoo 2004-11-14 06:20:23 UTC 
I don't know if I need to report this as a new bug, but for the moment I will put the comment inhere. 
The changes to the /etc/security/pam_env.conf breaks also the X11 forwarding by setting the DISPLAY to the value host:0.0. A workaround is to comment the DISPLAY= ... line in the pam_env.conf. But this bug is very annoying since the X11 forwarding is VERY used.
Comment 2 J. Alexander Treuman 2004-11-26 16:53:35 UTC 
The problem noted in #1 is covered by bug 70585. As for the submitted bug itself, I can't seem to reproduce it, and there's nothing in pam_env.conf that should cause it. Did you modify it at all? Perhaps you supply more details about your setup.
Comment 3 Martin Schlemmer (RETIRED) gentoo-dev 2005-02-25 11:47:10 UTC 
This was a bug in shadow - please update to shadow-4.0.6 (i think) or even better
shadow-4.0.7.