Opened 2 weeks ago

Last modified 9 days ago

#24817 new defect

Recommend that tools ignore HSDir and Guard flags on bridges

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.3.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-auth-bridge, tor-bridge, tor-spec
Cc: isis Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Child Tickets

#24885newmetrics-teamHide the HSDir and Guard flags on bridgesMetrics/Onionoo
#24886closedirlHide the HSDir and Guard flags on bridges on Metrics BotMetrics/Bot

Change History (4)

comment:1 Changed 2 weeks ago by arma

Is there any harm in leaving it as-is?

The bridge authority networkstatus document doesn't get shipped around to clients or relays -- only to the metrics db.

Maintaining more special-case code in the consensus generation section is a minor downside for taking it out, but I don't see much upside for taking it out.

comment:2 Changed 2 weeks ago by teor

The downside is that it's confusing on Relay Search and metrics bot:

Maybe we could remove it from metrics bot, and remove it or change the note on Relay Search?

comment:3 Changed 9 days ago by arma

I'm still a fan of solving this one in the analysis or visualization or whatever tools, not in adding complexity to Tor itself to make external processes easier. :)

comment:4 Changed 9 days ago by teor

Keywords: tor-spec added
Summary: Should the bridge authority assign the HSDir flag to bridges?Recommend that tools ignore HSDir and Guard flags on bridges

Ok, then I think we should patch dir-spec to say that the HSDir flag is meaningless for bridges. (As is the Guard flag.)
I'll open child tickets for atlas and the bot.

There are a small number of bridges with the Exit flag, I think we want to keep being able to see these:

Note: See TracTickets for help on using tickets.