Bug 331773 - Needs full implementation of SOCKS5 proxy for tracker, peer connections, DHT etc to stop IP leaks
Summary: Needs full implementation of SOCKS5 proxy for tracker, peer connections, DHT ...
Status: REPORTED
Alias: None
Product: ktorrent
Classification: Applications
Component: general (show other bugs)
Version: 4.3.1
Platform: Mint (Ubuntu based) Linux
: NOR wishlist
Target Milestone: ---
Assignee: Joris Guisson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-05 16:04 UTC by rainmakerraw
Modified: 2014-03-05 16:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rainmakerraw 2014-03-05 16:04:55 UTC 
KTorrent is the best torrent client I have tried to date. I actually switched DEs just to be able to use it natively. :) However, I was saddened to see that the SOCKS5 proxy support is incomplete to the point of being useless. Filling in my (paid-for) SOCKS5 proxy details still leaks the real WAN IP, as the proxy is not being used for all tracker, DHT and peer connections. Please can this be amended to a full implementation of proxying as seen in Deluge, for example? This topic pops up on the KDE forum regularly but there's never a resolution. Thanks for all your hard work. :)

Reproducible: Always

Steps to Reproduce:
1. Enter proxy details
2. Use checkmytorrentip.com or the checker at torguard.net etc
Actual Results:  
See that your real WAN IP address is being listed instead of that of the proxy.

Expected Results:  
The returned IP should be that of the proxy, else the proxy feature is useless/broken.