Comment 6 for bug 1084851

Revision history for this message
Joshua Lock (incandescant) wrote :

Of that I'm not really certain. I filed this report because as a user the behaviour surprised me that some things would be able to access the network and others wouldn't.

Having dug into the problem a little it's apparent that it's not trivial to solve - that doesn't mean that it's not worth solving, though.

Perhaps Ubuntu could integrate the PACRunner project[1], or something similar, and teach the various network dependant tools to talk to that rather than relying on environment variables?

Or perhaps the tools can be taught to use libproxy[2]?

At the very least maybe we should alert the user that the automatic settings will result in various things, such as software installation, possibly not working.

I suppose which resolution is chosen depends on how much of a priority seamless networking on proxied connections is for Ubuntu and the engineers involved.

1. http://git.kernel.org/cgit/network/connman/pacrunner.git
2. https://code.google.com/p/libproxy/