Bug 12376

Summary:	telepathy-idle: ability to use a socks/other proxy
Product:	Telepathy	Reporter:	Sjoerd Simons <sjoerd>
Component:	idle	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED MOVED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	nicolas, om26er
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	37145
Bug Blocks:

Description Sjoerd Simons 2007-09-10 00:38:20 UTC

The following bug report was filled on Debian's BTS as bug #441389. Please see http://bugs.debian.org/441389 for more information.

Am Sonntag, den 09.09.2007, 15:56 +0200 schrieb Sjoerd Simons:
> On Sun, Sep 09, 2007 at 01:41:18PM +0200, Jelmer Vernooij wrote:
> > Package: telepathy-idle
> > Version: 0.1.1-1
> > Severity: wishlist
> > 
> > It'd be useful if there was an option to specify a proxy for IRC
> > connections so a bouncer / irc proxy can be used. This usually would be
> > a different proxy from the globally set proxy used for http, ssh, etc.
> 
> Both me and upstream are a bit confused by this bug report. Afaik to use an IRC
> proxy/bouncer you just specify the proxy as the server instead of your normal
> irc server? So that should work with the current -idle.
> 
> I suppose you want support for socks proxy and things like that ?
Yep, that's the sort of thing I mean. There's several bouncers that
support socks or by addition of a custom command "CONNECT" in the IRC
protocol that is used for selecting the target network that should be
used.

Cheers,

Jelmer

Comment 1 Omer Akram 2010-08-30 22:22:45 UTC

Is this bug by any change fixed already?

Comment 2 Olli Salli 2010-08-31 02:24:00 UTC

Dropping myself from the bug, I haven't done any tp-idle dev in a long time.

As for the state of the bug, I don't think it's fixed. The real fix would probably be making idle use glib's GSocketClient to leverage the recently added transparent proxy capabilities: http://ndufresne.ca/2010/06/transparent-proxy-for-glib-applications/.

That would probably also fix quite a few other issues as when I originally wrote the idle network code almost five years ago I didn't really know a socket from a pipe, or from my arse for that matter. Especially the IdleSSLServerConnection (or whatever it was) code is probably a can of worms, I wrote it in like 1 day with no prior experience of the OpenSSL API at all...

Comment 3 Simon McVittie 2013-04-24 15:23:55 UTC

(In reply to comment #2)
> The real fix would
> probably be making idle use glib's GSocketClient to leverage the recently
> added transparent proxy capabilities

This should now work (since 0.1.11), but that wasn't what was requested:

(In reply to comment #0)
> There's several bouncers that
> support socks or by addition of a custom command "CONNECT" in the IRC
> protocol that is used for selecting the target network that should be
> used.

Support for these would require use of a non-system-wide proxy.

Comment 4 Simon McVittie 2013-10-10 14:58:52 UTC

(In reply to comment #3)
> (In reply to comment #0)
> > There's several bouncers that
> > support socks or by addition of a custom command "CONNECT" in the IRC
> > protocol that is used for selecting the target network that should be
> > used.
> 
> Support for these would require use of a non-system-wide proxy.

For the SOCKS case, Bug #70333 outlines one possible way to achieve that. I don't think any of the Telepathy maintainers are likely to implement that any time soon, but I'd review patches.

Comment 5 GitLab Migration User 2019-12-03 19:24:08 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-idle/issues/1.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.