cicku / libproxy

Automatically exported from code.google.com/p/libproxy
GNU Lesser General Public License v2.1
1 stars 0 forks source link

Allow chaining between config modules #165

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
In openSUSE, we used to have a hack that we used to synchronize the system 
proxy configuration with the gconf proxy configuration.

IMHO, this should be handled by libproxy directly.

The idea is that the user can choose between those settings:
 no proxy
 proxy configured system-wide
 my custom proxy configuration

If the user chooses "proxy configured system-wide", this means that the 
gsettings module in libproxy would then chain up to another module.

This makes it easier for sysadmin to control stuff.

Original issue reported on code.google.com by vincent....@gmail.com on 3 Aug 2011 at 11:16

GoogleCodeExporter commented 8 years ago
Fundamentally, passing proxy information from an unprivileged user to the root 
user is a security problem (the proxy could fake trusted data and use that data 
to gain root privileges). I know you aren't suggesting this, but I have to make 
it explicit so that no one posts this idea. :)

So basically you want a gconf option which will chain libproxy to 
config_sysconfig? This is certainly doable, patches welcome. :)

Original comment by nathan...@themccallums.org on 3 Aug 2011 at 1:56

GoogleCodeExporter commented 8 years ago
s/gconf/gsettings, but yeah, that's the idea. I'm kind of hoping that Dominique 
will do a patch ;-)

Original comment by vincent....@gmail.com on 3 Aug 2011 at 2:01