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.
Trac: Username: hsn
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
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 (moved)).
Trac: Owner: N/Ato asn Cc: N/Ato isis, yawning Component: Tor to Pluggable transport