Opened 2 months ago

Last modified 4 weeks ago

#27100 assigned enhancement

report connection to PT SOCKS proxy separately from OR connection

Reported by: catalyst Owned by: catalyst
Priority: Medium Milestone: Tor: 0.3.6.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 035-roadmap-subtask, 035-triaged-in-20180711, socks, pt, s8-bootstrap
Cc: catalyst, mcs, brade, intrigeri, rl1987 Actual Points:
Parent ID: #25502 Points:
Reviewer: Sponsor: Sponsor8


Right now when acting as a PT client, we don't distinguish between connecting to the SOCKS port of a PT proxy and connecting to the OR that's behind the proxy. This means that we lose some intermediate progress reporting that can help users understand what might be going wrong.

Child Tickets

Change History (7)

comment:1 Changed 2 months ago by intrigeri

Cc: intrigeri added

comment:2 Changed 7 weeks ago by catalyst

It looks like we might be able to hook in near connection_or_finished_connecting() or connection_proxy_connect(). Right now we call control_event_bootstrap(BOOTSTRAP_STATUS_HANDSHAKE, 0) near the top of connection_or_finished_connecting() before we have begun to talk to the proxy, if any.

comment:3 Changed 7 weeks ago by rl1987

Cc: rl1987 added

comment:4 Changed 7 weeks ago by rl1987

Keywords: socks pt added

comment:5 Changed 7 weeks ago by catalyst

Keywords: s8-bootstrap added
Sponsor: Sponsor8

comment:6 Changed 7 weeks ago by catalyst

Type: defectenhancement

comment:7 Changed 4 weeks ago by catalyst

Milestone: Tor: 0.3.5.x-finalTor: 0.3.6.x-final

Move my post-freeze 0.3.5 items to 0.3.6.

Note: See TracTickets for help on using tickets.