Renuka Deshmukh renud1988 at
Thu Mar 25 06:44:17 GMT 2010

@anirudh ...

about git and ssh ..... there is a workaround for git:// for proxy ....
changing the url from git://repo/directory.git  to
http://repo/directory.gitand then
git clone http://repo/directory.git ... works fine .... i am actually using
this temporary workaround right now for downloading some sources ....

though i am still unsuccessful with ssh ... !!

about apt ... it doesnot have a separate proxy configuration ... but it
invokes the environment variable values of http_proxy .... which is used by
bash and can be configured in .bashrc in /home or bash.rc in /etc !!

and about other applications like firefox and opera .... they have a static
file(by static i mean the file is not re-written everytime the os is
rebooted) ...which stores the proxy variable and i am sure that can be
accomplished for various other applications as well ...

though ... the http_proxy variable works well and fine for almost all the
applications .... the only problem i encountered is with git:// for which i
found a workaround ... and ssh ...

there is a second solution as well ... creating a transparent proxy server
... as specified in the idea description ....which will automatically
authenticate on the proxy server .. ! in short ... using a transparent proxy
server to handle requests for forced proxy requests !!

On Thu, Mar 25, 2010 at 11:25 AM, Anirudh Sanjeev <
anirudh at> wrote:

> Hi,
> I'm not an expert, let alone a mentor here. You should get a second opinion
> before taking this advice:
> I don't think there can be a "truly" system wide proxy. While
> gnome-network-properties sets the proxy, and sets it in gconf2 and the
> environment variable, there's nothing that can be done to ensure that the
> application that is using a network connection respects the http_proxy env
> config.
> In other words, any application developer has to manually add proxy
> support. For example, ssh and git:// does not support http_proxy (or
> didn't, last time I checked), and so you need to go through hoops to make
> them work behind a network proxy.
> The only work that can be done for a "truly system wide proxy" would be to
> ensure all the shells - zsh, bash, etc recieve the appropriate http_proxy
> and other env variables, and to emit these changes to all the shells, when
> changes are made. The second portion will be more challenging.
> To make matters worse, apt has a separate proxy configuration and many
> other applications think it's a great idea to set their own individual
> proxy server.
> tl;dr - Unless you force all outgoing connections to tunnel through a proxy
> emulating a direct connection, and do this during the intial stages of
> application loading, there'll be no such thing as a "global http proxy".
> Anirudh
> --
> Senior Undergraduate Student, Indian Institute of Technology, Kharagpur
> Start something!
> --
> ubuntu-soc mailing list
> ubuntu-soc at
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the ubuntu-soc mailing list