Opened 3 years ago

Last modified 2 years ago

#20531 new defect

rewrite_node_address_for_bridge and networkstatus_set_current_consensus can conflict

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: bridge-client, bridge-bypass tor-client tor-pt
Cc: Actual Points:
Parent ID: #22739 Points: 1
Reviewer: Sponsor:

Description

When a relay is configured as a bridge, both rewrite_node_address_for_bridge and networkstatus_set_current_consensus update that relay's node, as do any descriptor downloads.

This can be problematic if the details they use differ.

One user reports this can lead to direct connections being made to the relay/bridge, even when a pluggable transport is configured. We have been unable to confirm this.

https://lists.torproject.org/pipermail/tor-dev/2016-November/011618.html

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by teor

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

Milestone renamed

comment:2 Changed 3 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:3 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:4 Changed 2 years ago by nickm

Keywords: tor-client tor-pt added
Parent ID: #22739

#22739 would either solve this, or help a lot.

Note: See TracTickets for help on using tickets.