Opened 6 years ago

Last modified 3 months ago

#9125 new enhancement

Allow reporting different obfs ports to bridge db

Reported by: hsn Owned by:
Priority: Medium Milestone:
Component: Circumvention/Pluggable transport Version: Tor: 0.2.4.14-alpha
Severity: Normal Keywords: tor-relay, tor-pt
Cc: isis, yawning Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

ServerTransportListenAddr needs to be extended to allow listen on one port and announce to bridge database another because in most cases tor can not listen on low ports.

Something like NoAdvertise and NoListen ORPort flags.

Child Tickets

Change History (9)

comment:1 Changed 6 years ago by nickm

Keywords: tor-relay tor-pt added
Milestone: Tor: 0.2.5.x-final

comment:2 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:3 Changed 4 years ago by isis

Cc: isis yawning added
Component: TorPluggable transport
Owner: set to asn

If the goal is simply to make it easier to run PTs on low ports like 80 and 443, then that's a problem with a particular PT implementation. (Changing the Trac Component to "Pluggable Transports".)

Otherwise, I'm not entirely sure why someone would want to advertise their Bridge's ORPort to BridgeDB, and yet not distribute the PT locations via BridgeDB… If the reasoning is that the Bridge operator still wants to support statistics, but not allow BridgeDB to distribute the addresses to Bridge users, then there are other, simpler proposed features (see #13727).

comment:4 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 2 years ago by nickm

Milestone: Tor: unspecified
Severity: Normal

comment:8 Changed 4 months ago by teor

Owner: asn deleted
Status: newassigned

asn does not need to own any obfuscation tickets any more. Default owners are trouble.

comment:9 Changed 3 months ago by cohosh

Status: assignednew

tickets were assigned to asn, setting them as unassigned (new) again.

Note: See TracTickets for help on using tickets.