This forum has been archived. All content is frozen. Please use KDE Discuss instead.

proxy config wish

Tags: None
(comma "," separated)
J. Frank Parnell
Registered Member
Posts
7
Karma
0

proxy config wish

Mon Dec 11, 2006 12:49 am
I would like to be able to configure ktorrent (2.1beta1) to use a different http proxy (for connecting to trackers) than the proxies (in .kde/share/config/kioslaverc) I have configured for when I browse the web with konqueror.

I'd be grateful for any suggestions.
George
Moderator
Posts
5421
Karma
1

Mon Dec 11, 2006 5:33 pm
This is currently not possible, why do you want to do this ?
J. Frank Parnell
Registered Member
Posts
7
Karma
0

Mon Dec 11, 2006 7:27 pm
I was afraid you'd ask why. I'll try to make it short.

Normally, I surf via a tor/privoxy http proxy which hides my true IP address. Note that tor (http://tor.eff.org/) will change my IP address from time to time. Configuring konqueror to use this proxy is what puts this proxy into kioslaverc.

Now a particular "ratio-based" tracker I visit requires that the IP I use when my bittorrent client accesses their tracker be the same as the IP I used when accessing their website, to download the .torrent file, for instance.

Since tor can change my IP, I normally download all .torrent files directly, bypassing the tor proxy. This means that for the IP sensitive tracker I need to have my client send requests from my real IP. However, now that the proxy definition is in kioslaverc, that is what ktorrent uses, and this tracker rejects me. (Another reason for not wanting to use tor for bittorrent is that it is already a somewhat slow and overused service. I do not wish to abuse it by adding any bittorrent load to it).

Yes, the tracker is daft, but unfortunately I can't change that.

So anyway, that's the situation. I want to be able to surf with tor, and bittorrent without it. From my point of view, web surfing and bittorrent downloading are different in kind, and while it may be appropriate in some cases for ktorrent and konqueror to use the same proxy, there are certainly some cases where it is not desireable.

So my wish is that ktorrent have a configuration option to override the "global" proxy setting in kioslaverc.

I don't know if you'll find that much of a compelling explanation ... maybe this situation will affect too few users. But anyway, it's a big problem for me. Thanks for your time.
George
Moderator
Posts
5421
Karma
1

Tue Dec 12, 2006 6:13 pm
I will have to see if it is possible to change the proxy for specific KIO http jobs. If it is, it's probably not much work to add this.
George
Moderator
Posts
5421
Karma
1

Thu Dec 14, 2006 5:52 pm
After some investigation and a small test, it seems to be possible.
George
Moderator
Posts
5421
Karma
1

Thu Dec 14, 2006 6:11 pm
OK, I have added it, you can now configure this in the advanced settings page.
J. Frank Parnell
Registered Member
Posts
7
Karma
0

Sat Dec 16, 2006 2:51 am
Terrific! Thanks for your hard work.
Thehound
Registered Member
Posts
11
Karma
0

Tue Dec 19, 2006 6:17 am
This is pretty easy to get around in Kubuntu. Manually specify the proxy settings to your tor proxy, then underneath you should see exceptions. List those torrent site domains as well as the tracker url(if it's different). Apply it all and Konquerer should use tor but for the urls in the list. It will also create a global exception, causing ktorrent to announce directly to the tracker. If you need 2 different proxies for some reason, listing these exceptions and using proxychains to redirect to the other proxy could be an option, but I see no reason to not connect to the tracker directly, as you do want it to see your real IP so peers can initiate incoming connections to you. Note: ktorrent's custom IP override DOES NOT work with all trackers. I tested this with an anonymous proxy and only a few trackers showed me as connectable. I tested this with utorrent previously with even worse results months ago, so it does show that situation is improving with trackers.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar