#8117: Tor SOCKS handshake makes SOCKS circuit isolation non-functional for many
apps
----------------------------------+-----------------------------------------
Reporter: cypherpunks | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: Tor: 0.2.3.x-final
Component: Tor | Version: Tor: 0.2.3.25
Keywords: tor-client isolation | Parent:
Points: | Actualpoints:
----------------------------------+-----------------------------------------
Changes (by mikeperry):
* cc: ioerror (added)
Comment:
My opinion here is that it's actually good to break apps that are doing
SOCKS u+p wrong, so long as we don't also break those apps when SOCKS u+p
is not set. We really shouldn't tell users "Hey, use SOCKS u+p to isolate
your apps!" and then not actually isolate anything because our handshake
silently tells the app not to use u+p.
Also, if there are actually bugs in Pidgin/whatever's SOCKS u+p support,
it's unlikely those will ever get fixed if our handshake always tells
Pidgin not to use SOCKS u+p.
Adding ioerror to Cc because I think he's worked improving on Pidgin's
SOCKS implementation for Tor in the past.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8117#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online