Bug 89001 – Default pam_env.conf contains X centric entries that cause errors on servers without X

• Status: RESOLVED DUPLICATE of bug 88379
• Product: Gentoo Linux

[Description Kirk 2005-04-13 12:17:30 UTC]

The default pam_env.conf contains the following entries:
REMOTEHOST      DEFAULT= OVERRIDE=@{PAM_RHOST}
DISPLAY         DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}
XAUTHORITY     DEFAULT= OVERRIDE=@{XAUTHORITY}

These entries are created even if X is not installed.  This causes numerous errors to appear in the server logs:

Apr 13 12:54:24 hostname sudo: PAM pam_putenv: delete non-existent entry; R
EMOTEHOST
Apr 13 12:56:22 hostname PAM-env[22521]: Unknown PAM_ITEM: <DISPLAY> 
Apr 13 12:56:22 hostname sshd[22521]: PAM pam_putenv: delete non-existent entry; DISPLAY 
Apr  6 00:00:15 hostname PAM-env[20124]: Unknown PAM_ITEM: <XAUTHORITY>
Apr  6 00:00:15 hostname sshd[20124]: PAM pam_putenv: delete non-existent entry; XAUTHORITY



Reproducible: Always
Steps to Reproduce:
1. Install system with -X flag set.
2. Look at /etc/security/pam_env.conf



Expected Results:  
Default configurations should not result in errors about missing X, if the -X
flag is set.

This is a pretty annoying default for servers that don't use X.

[Comment 1 Jakub Moc (RETIRED) 2005-04-13 12:25:37 UTC]

This workaround works for me. 

REMOTEHOST      DEFAULT=localhost OVERRIDE=@{PAM_RHOST}
DISPLAY         DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}

*** This bug has been marked as a duplicate of 70585 ***

[Comment 2 Jakub Moc (RETIRED) 2005-04-13 12:45:03 UTC]

Uhm, sorry. Wrong bug number.

[Comment 3 Jakub Moc (RETIRED) 2005-04-13 12:45:56 UTC]

*** This bug has been marked as a duplicate of 88379 ***