Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#5437 closed defect (fixed)

man page: IsolateClientProtocol needs clarification?

Reported by: cypherpunks Owned by:
Priority: Low Milestone: Tor: 0.2.3.x-final
Component: Core Tor/Tor Version: Tor: 0.2.3.12-alpha
Severity: Keywords: documentation tor-client
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

IsolateClientProtocol says

"Don't share circuits with streams using a different protocol. (... TransPort connections, NATDPort connections and DNSPort requests are all considered to be different protocols.)"

But further down: "By default, streams received on different ports are always isolated from one another.)"

Isn't the first one redundant then? It still applies to SOCKS v4 vs v5 but not really to different ports.

Child Tickets

Change History (8)

comment:1 Changed 8 years ago by nickm

By default, streams received on different ports are isolated from one another. The SessionGroup option overrides this behavior.

comment:2 Changed 8 years ago by cypherpunks

thanks, makes sense from a dev point of view. For a user it still seems redundant, why would anyone add a sessiongroup id to a non-socksport only to disable the grouping with IsolateClientProtocol again?

comment:3 in reply to:  2 ; Changed 8 years ago by rransom

Replying to cypherpunks:

thanks, makes sense from a dev point of view. For a user it still seems redundant, why would anyone add a sessiongroup id to a non-socksport only to disable the grouping with IsolateClientProtocol again?

The IsolateClientProtocol option is on by default. It exists as an option so that users can turn it off.

comment:4 in reply to:  3 Changed 8 years ago by rransom

Replying to rransom:

Replying to cypherpunks:

thanks, makes sense from a dev point of view. For a user it still seems redundant, why would anyone add a sessiongroup id to a non-socksport only to disable the grouping with IsolateClientProtocol again?

The IsolateClientProtocol option is on by default. It exists as an option so that users can turn it off.

Oops -- I was looking at the wrong option. It is off by default.

comment:5 Changed 8 years ago by nickm

Keywords: documentation added
Milestone: Tor: 0.2.3.x-final

comment:6 Changed 8 years ago by nickm

Resolution: fixed
Status: newclosed

Fixed in dfbe779a450c089

comment:7 Changed 7 years ago by nickm

Keywords: tor-client added

comment:8 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.