[Bugs] #3070 UNSP: Having sugarized proxy setting UI

[Sugar Labs Bugs]

#3070: Having sugarized proxy setting UI
------------------------------------------+---------------------------------
    Reporter:  alsroot                    |          Owner:  alsroot                    
        Type:  enhancement                |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar                      |        Version:  Unspecified                
    Severity:  Unspecified                |       Keywords:                             
Distribution:  Unspecified                |   Status_field:  Unconfirmed                
------------------------------------------+---------------------------------

Comment(by sascha_silbe):

 The proxy settings should be managed by NetworkManager since they are
 needed to provide connectivity and will also differ between different
 connections. There has been talk upstream about adding proxy support
 directly to NetworkManager, but
 [https://bugzilla.gnome.org/show_bug.cgi?id=621767 no implementation so
 far]. A web search turned up the following (partial) solutions:

 * A third-party add-on package called
 [http://marin.jb.free.fr/proxydriver/ proxydriver] distributes proxy
 settings to logged-in users, using custom config files in each users home
 directory to store the proxy settings for each connection.
 * Use a NetworkManager hook to update an additional gconf source file in
 the users home directory. The mail threads
 ([http://mail.gnome.org/archives/networkmanager-
 list/2010-September/thread.html#00033 thread 1],
 [http://mail.gnome.org/archives/networkmanager-
 list/2010-September/thread.html#00084 thread 2]) don't address where the
 proxy settings come from, only how the users GConf settings get updated.
 * Running a minimal local proxy and [http://linuxbasement.com/content
 /automatically-switching-between-work-proxy-and-no-proxy configuring it to
 use different upstream proxies] based on the current connection. The
 (upstream) proxy settings are stored in system config files.
 * [http://code.google.com/p/libproxy/ libproxy] has a plugin that triggers
 wpad / PAC (i.e. automatic proxy settings) updates after NetworkManager
 has brought up a new connection.

 For automatic setups, something like libproxy, maybe combined with a local
 forwarding proxy, is probably the way to go. No user intervention
 required, it just works. We can achieve a similar result by setting the
 gconf proxy settings to automatic, but I doubt the automatic update on
 connection change would be done in that case.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/3070#comment:1>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system