[tor-bugs] #12254 [Tor]: Tonga should sign its bridge networkstatus doc? Or maybe change format to v3-style vote?
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Jun 10 14:39:28 UTC 2014
#12254: Tonga should sign its bridge networkstatus doc? Or maybe change format to
v3-style vote?
-------------------------+-------------------------------------------------
Reporter: arma | Owner:
Type: | Status: new
enhancement | Milestone: Tor: unspecified
Priority: normal | Version:
Component: Tor | Keywords: bridgedb-parsers, metrics-db,
Resolution: | bridgeauth,
Actual Points: | Parent ID:
Points: |
-------------------------+-------------------------------------------------
Changes (by isis):
* keywords: => bridgedb-parsers, metrics-db, bridgeauth,
Comment:
I'm willing to write a patch for this one.
Before I write a patch, I'd prefer to first hear some feedback on whether
doing '''2b''' is worth the extra effort:
'''1. Is this desirable?'''
I mostly just want the BridgeAuth's (tonga's) signature on the
`networkstatus-bridges` file before BridgeDB parses, since BridgeDB's
parsers are taking the BridgeAuth's word as gold... to the extent that
`@type bridge-server-descriptors` are thrown out entirely if the
BridgeAuth didn't include them in the `networkstatus-bridges` file.
'''2. Which patch do you want?'''
'''2a. Make the BridgeAuth sign''', or,
So far, I only care about this one.
'''2b. Make the `networkstatus-bridges` file analogous to V3
networkstatus files'''
Someone should outline what these are, and probably what
benefits/drawbacks they provide. It would be interesting to know how
difficult it would be to reuse the functions which create `@type network-
status-microdesc-consensus-3` documents to also create `@type bridge-
network-status` documents.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12254#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list