Opened 11 months ago

Closed 8 months ago

Last modified 7 months ago

#29121 closed defect (fixed)

tor man page doesn't mention isolating between socksports

Reported by: arma Owned by:
Priority: Medium Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: doc, 040-backport
Cc: Actual Points: 0.1
Parent ID: #22619 Points: 0.1
Reviewer: catalyst Sponsor:

Description

If I set SocksPort 9050 and also SocksPort 9060, then if I understand correctly, Tor automatically isolates stream requests that come in on the different socksports.

But the man page doesn't mention this level of isolation. Maybe because there is no flag for influencing it?

It sure seems helpful to have a full sentence in the socksport intro stanza explaining what gets isolated by default, and what can be isolated by changing options. Or maybe there is a better place to put that than the socksport section?

Child Tickets

Change History (14)

comment:1 Changed 11 months ago by nickm

Here's the documentation:

    **SessionGroup=**__INT__;;
        If no other isolation rules would prevent it, allow streams
        on this port to share circuits with streams from every other
        port with the same session group.  (By default, streams received
        on different SocksPorts, TransPorts, etc are always isolated from one
        another. This option overrides that behavior.)

comment:2 Changed 11 months ago by nickm

Milestone: Tor: unspecified

(It might not be obvious enough, but it is there. I'd love a patch to make it make more sense.)

comment:3 Changed 9 months ago by rl1987

Status: newneeds_review

comment:4 Changed 9 months ago by asn

Reviewer: mikeperry

comment:5 Changed 9 months ago by teor

Reviewer: mikeperry

Remove Mike as reviewer, because he's overloaded.
We'll work out what to do with these tickets in the weekly meeting.

comment:6 Changed 9 months ago by teor

Keywords: doc added
Milestone: Tor: unspecifiedTor: 0.4.1.x-final

comment:7 Changed 8 months ago by asn

Reviewer: catalyst

comment:8 in reply to:  3 Changed 8 months ago by catalyst

Status: needs_reviewmerge_ready

Replying to rl1987:

https://github.com/torproject/tor/pull/841

Thanks! Looks good!

comment:9 Changed 8 months ago by cypherpunks

YES, Tor automatically isolates stream requests that come in on the different socksports.

well i was never able, to set the

SessionGroup=123

but this is another issue. Did you try anyway by assigning different SessionGroup per SocksPort?

comment:10 Changed 8 months ago by teor

Actual Points: 0.1
Keywords: 040-backport added
Milestone: Tor: 0.4.1.x-finalTor: 0.4.0.x-final
Points: 0.1

Documentation fixes go in the alpha series.

Cherry-picked to 0.4.0 and merged forward.

Merged #29121, #30004 to 0.4.0, and #29926, #28806 to master, then merged forward.

comment:11 Changed 8 months ago by teor

Resolution: fixed
Status: merge_readyclosed

comment:12 in reply to:  9 ; Changed 8 months ago by teor

Replying to cypherpunks:

YES, Tor automatically isolates stream requests that come in on the different socksports.

well i was never able, to set the

SessionGroup=123

but this is another issue. Did you try anyway by assigning different SessionGroup per SocksPort?

I'm sorry, I'm not sure what you mean.
Would you like to open another ticket?
We try to handle one issue per ticket, otherwise they get lost.

comment:13 in reply to:  12 Changed 7 months ago by cypherpunks

Replying to teor:

Replying to cypherpunks:

YES, Tor automatically isolates stream requests that come in on the different socksports.

well i was never able, to set the

SessionGroup=123

but this is another issue. Did you try anyway by assigning different SessionGroup per SocksPort?

I'm sorry, I'm not sure what you mean.
Would you like to open another ticket?
We try to handle one issue per ticket, otherwise they get lost.

Yes, the Problem discovered years ago, is described in this issue #22619

comment:14 Changed 7 months ago by teor

Parent ID: #22619

Thanks, we will deal with it in that ticket.

Note: See TracTickets for help on using tickets.