Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 228133 - app-admin/sudo-1.6.8_p13 ignores RSYNC_PROXY env variable, regression
Summary: app-admin/sudo-1.6.8_p13 ignores RSYNC_PROXY env variable, regression
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Diego Elio Pettenò (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-18 18:40 UTC by Tiago Marques
Modified: 2008-06-19 00:36 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tiago Marques 2008-06-18 18:40:41 UTC
In my university I must connect through a proxy to have rsync, so portage can be synced.

I used: "RSYNC_PROXY=proxy.ua.pt:3128 sudo emerge --sync"
Recently though, only this works:

"sudo -s" 
"RSYNC_PROXY=proxy.ua.pt:3128 emerge --sync"

This is happening with versions of sudo >=app-admin/sudo-1.6.9_p13, the version app-admin/sudo-1.6.8_p12-r1 was the last that worked well, as it is now.

Reproducible: Always

Steps to Reproduce:
1.update sudo to app-admin/sudo-1.6.9_p13 or more recent
2.RSYNC_PROXY=*Whatever* sudo emerge --sync
3.

Actual Results:  
rsync doesn't connect to the proxy

Expected Results:  
should connect to the proxy
Comment 1 Carsten Lohrke (RETIRED) gentoo-dev 2008-06-18 22:44:15 UTC
As hinted in red letters, "Gentoo Bugzilla" is not the correct product to file bugs regarding ebuilds. Please use "New -> Gentoo Linux -> Component: Ebuilds" in future.
Comment 2 Diego Elio Pettenò (RETIRED) gentoo-dev 2008-06-19 00:36:14 UTC
From sudo's CHANGES file:

594) The env_reset option is now enabled by default.  Commands run
     through sudo now receive a minimal environment with certain
     variables passed through and/or checked.  The list of variables
     allowed is configurable via the env_keep and env_check options
     in sudoers.

this is for 1.6.9p0 release.

The default behaviour that was used previously has been changed upstream, and I don't really want to get around that in the default configuration as I can easily wee why they chose this way.