Christian Kurz
2000-Dec-27 20:08 UTC
Problems with reading pam_env and setting enviroment variables
Hi guys, here's another nasty bug in openssh that I also noticed. Has this already been fixed or would someone please take care of this? Thanks.> If I enable the line:> auth required pam_env.so> to the ssh pam file, with the following line in > /etc/security/pam_env.conf > file:> PATH DEFAULT=/usr/local/bin:/bin:/usr/bin:/usr/bin/X11:/usr/games> then when I login with ssh, I get garbage for a path:> ?Cr/t?l@??Cca?>l@?'@/bi?????>n@?'@4????\&@lg&@?\&@??????:@?????Cr/t?l@??Cca?>l@?'@/bi?????>n@?'@4????\&@lgg&@?\&@??????:@????> Disableing pam_env.so in the ssh pam file fixes this. Also, putting PATH > in /etc/environment and excluding it from pam_env.conf works. I'd > normally think this is a pam bug, but I've only seen this with ssh.Ciao Christian -- Debian Developer and Quality Assurance Team Member 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 242 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20001227/d02dc374/attachment.bin
Apparently Analagous Threads
- patch to support hurd-i386.
- sshd and pam_env both read /etc/environment, but assume different syntax
- COMPATIBILITY: AllowHosts/DenyHosts/SilentDeny not supported
- Error in sshd's manpage
- Might want to allow different host keys for different ports on same host