Bug 331773

Summary: Needs full implementation of SOCKS5 proxy for tracker, peer connections, DHT etc to stop IP leaks
Product: [Applications] ktorrent Reporter: rainmakerraw
Component: generalAssignee: Joris Guisson <joris.guisson>
Status: REPORTED ---    
Severity: wishlist    
Priority: NOR    
Version First Reported In: 4.3.1   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

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.