Opened 4 years ago

Closed 2 years ago

#18202 closed defect (wontfix)

Notify user if bridge has changed to regular node

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: brade, mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If a bridge was to change from a bridge to regular (guard) node, would Tor Browser know that it has changed and notify user (error message) or will users be still using it under the false impression that it is still a bridge?

Child Tickets

Change History (11)

comment:1 Changed 4 years ago by teor

Component: Tor BrowserTor
Milestone: Tor: 0.2.9.x-final

I'm not sure we have space for this in 0.2.8

comment:2 Changed 4 years ago by mcs

Cc: brade mcs added

teor, do you know what tor's current behavior is? Will tor complain if a regular node is used in a Bridge line or is there no real distinction?

comment:3 in reply to:  2 ; Changed 4 years ago by teor

Replying to mcs:

teor, do you know what tor's current behavior is? Will tor complain if a regular node is used in a Bridge line or is there no real distinction?

No, there is no real distinction. As far as the bridge client is concerned, relays and bridges are equivalent.

In fact, our IPv6 relay wiki page recommends using relays as bridges to test them. (It's easier than configuring EntryNodes.)

comment:4 in reply to:  3 ; Changed 4 years ago by mcs

Replying to teor:

No, there is no real distinction. As far as the bridge client is concerned, relays and bridges are equivalent.

OK; thanks for the info. Maybe there is a way for Tor Browser/Tor Launcher to determine whether a configured bridge is now listed as a public relay? On the other hand, it sounds like using regular relays as bridges is also a feature some people may legitimately use (at least for testing).

Also, is there a default Trac owner for tor tickets like this one? It probably does not make sense to leave this assigned to tbb-team.

comment:5 in reply to:  4 Changed 4 years ago by teor

Owner: tbb-team deleted
Status: newassigned

Replying to mcs:

Replying to teor:

No, there is no real distinction. As far as the bridge client is concerned, relays and bridges are equivalent.

OK; thanks for the info. Maybe there is a way for Tor Browser/Tor Launcher to determine whether a configured bridge is now listed as a public relay? On the other hand, it sounds like using regular relays as bridges is also a feature some people may legitimately use (at least for testing).

If the relay is in the public consensus, it's not a bridge.

Also, is there a default Trac owner for tor tickets like this one? It probably does not make sense to leave this assigned to tbb-team.

Removed the owner.

comment:6 Changed 3 years ago by isabela

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

tickets market to be removed from milestone 029

comment:7 Changed 3 years ago by teor

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

Milestone renamed

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

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:10 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:11 Changed 2 years ago by nickm

Resolution: wontfix
Status: newclosed

I don't believe there's any plan to do this, or any good way to do this within the current network model.

Note: See TracTickets for help on using tickets.