I found this bug when in the same circumstance of /etc/environment proxy settings not applying to sudo sessions.
I understand the rationale for "wontfix"-ing the previously suggested fix of changing /etc/sudoers. However, Ubuntu have been carrying a patch for the past 12 years which addresses the issue in a different, potentially more acceptable way, and I haven't been able to find any evidence in bug trackers of forwarding that diff back to Debian being discussed, so I'm bringing it up here: ``` diff --git a/debian/etc/pam.d/sudo b/debian/etc/pam.d/sudo index 96e8906a..7819ab18 100644 --- a/debian/etc/pam.d/sudo +++ b/debian/etc/pam.d/sudo @@ -3,6 +3,9 @@ # Set up user limits from /etc/security/limits.conf. session required pam_limits.so +session required pam_env.so readenv=1 user_readenv=0 +session required pam_env.so readenv=1 envfile=/etc/default/locale user_readenv=0 + @include common-auth @include common-account @include common-session-noninteractive diff --git a/debian/etc/pam.d/sudo-i b/debian/etc/pam.d/sudo-i index d6385222..584b2d8e 100644 --- a/debian/etc/pam.d/sudo-i +++ b/debian/etc/pam.d/sudo-i @@ -3,6 +3,9 @@ # Set up user limits from /etc/security/limits.conf. session required pam_limits.so +session required pam_env.so readenv=1 user_readenv=0 +session required pam_env.so readenv=1 envfile=/etc/default/locale user_readenv=0 + @include common-auth @include common-account @include common-session ``` Including pam_env.so in sudo's PAM configuration would apply system-wide environment settings to sudo sessions, in a way which is generally consistent with the existing Debian PAM configurations for cron, login, sshd, and su. The Ubuntu bug in which these changes were originally made 12 years ago was https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/982684, and proxy settings are cited as motivation there as well.
