Opened 2 years ago

Last modified 2 years ago

#26339 new defect

Use same traffic path if destination is the same but the protocol is different.

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Many people use Tor to proxify their non-Tor software such as Bitcoin, BitMessage. And some of them are using SOCKS4.

SocksPort Y

  1. User's software query DNS via DNSPort:
  2. Tor will create a path to to resolve its IP
  3. Tor return is
  4. User's software connect to via SocksPort, using Socks4.

In step 4, Tor will use step 2's path to connect because Tor know may be

In step 4, Tor create a new path to connect to, thus's server admin will see 2 incoming connection;
1) DNS request from (step2's exit ip)
2) WWW request from (step4's exit ip)

Child Tickets

Change History (1)

comment:1 Changed 2 years ago by dgoulet

Component: Core TorCore Tor/Tor
Milestone: Tor: unspecified
Note: See TracTickets for help on using tickets.