Opened 21 months ago

Last modified 19 months ago

#29331 new defect

A bridge's new identity is not actually ignored although we say so

Reported by: cypherpunks2 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor:
Severity: Major Keywords: 041-proposed
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I have got a bunch of these warnings recently since my bridge had a full reinstallation.

entry_guard_learned_bridge_identity(): Bug: We 'learned' an identity [redacted] for a bridge at [redacted], but we already knew a different one ([redacted]). Ignoring the new info as possibly bogus. (on Tor 81f1b89efc94723f)

But it is not actually ignored: Tor bootstraps as usual, builds circuits using its new descriptor and writes circuit building state under its new identity. This could create an MiTM possibility, or maybe we need to elaborate a bit more on this.

Child Tickets

Change History (1)

comment:1 Changed 19 months ago by nickm

Keywords: 041-proposed added
Milestone: Tor: unspecified
Note: See TracTickets for help on using tickets.