Ticket #271 (closed feature-request: invalid)

Opened 5 years ago

Last modified 15 months ago

Support socks4a, socks4, socks5 protocols leak dns requests

Reported by: anonymous Owned by: markybob
Priority: minor Milestone:
Component: libtorrent Version:
Keywords: Cc:

Description

Deluge presently supports the socks4 and socks5 protocols for proxies. These do not support dns requests. The socks4a protocol takes dns requests. Supporting socks4a would mean users using tor would not have their dns requests leaked.

Deluge 0.5.8.9

Change History

Changed 5 years ago by markybob

  • status changed from new to closed
  • resolution set to wontfix

All 0.5 tickets are being closed. The branch is dead and won't be maintained any further.

Changed 2 years ago by balaton

  • status changed from closed to reopened
  • resolution wontfix deleted
  • version changed from 0.5.9.1 to 1.3.0_dev
  • component changed from 0.5.x to libtorrent

I reopen this bug as I believe it is still valid.

Changed 2 years ago by Cas

  • priority changed from major to minor
  • version 1.3.0_dev deleted
  • type changed from bug to feature-request
  • summary changed from request to support socks4a, socks4, socks5 protocols leak dns requests to Support socks4a, socks4, socks5 protocols leak dns requests

I assume that this is actually a libtorrent request. If so please post here:  http://code.google.com/p/libtorrent/issues/list

Changed 15 months ago by Cas

  • status changed from reopened to closed
  • resolution set to invalid
Note: See TracTickets for help on using tickets.