Opened 17 years ago
Closed 13 years ago
#271 closed feature-request (Invalid)
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 (4)
comment:1 by , 17 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
| Component: | 0.5.x → libtorrent |
|---|---|
| Resolution: | wontfix |
| Status: | closed → reopened |
| Version: | 0.5.9.1 → 1.3.0_dev |
I reopen this bug as I believe it is still valid.
comment:3 by , 14 years ago
| Priority: | major → minor |
|---|---|
| Summary: | request to support socks4a, socks4, socks5 protocols leak dns requests → Support socks4a, socks4, socks5 protocols leak dns requests |
| Type: | bug → feature-request |
| Version: | 1.3.0_dev |
I assume that this is actually a libtorrent request. If so please post here: http://code.google.com/p/libtorrent/issues/list
comment:4 by , 13 years ago
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
All 0.5 tickets are being closed. The branch is dead and won't be maintained any further.