[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1839 [BridgeDB]: Rotate available bridges over time
#1839: Rotate available bridges over time
-----------------------------+-------------------------------------------
Reporter: arma | Owner: isis
Type: enhancement | Status: new
Priority: major | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords: bridgedb-dist, bridgedb-0.3.2
Actual Points: | Parent ID:
Points: |
-----------------------------+-------------------------------------------
Changes (by isis):
* status: needs_review => new
* priority: blocker => major
Comment:
Okay, I merged
[https://trac.torproject.org/projects/tor/ticket/1839#comment:9 the
changes mentioned above] for bridgedb-0.3.2. This at least fixes the
issues with getting #4771 deployed. I'm decreasing the priority, because
it's no longer blocking.
However, I think we still want separated hashrings, were only one
subhashring of a hashring is available per period. This ''sounds'' like a
good idea. I'm not sure how compatible it will be with running BridgeDB's
distributors on separate machines (#12506), since in that model, each
distributor will pretty much get assigned a chunk of bridges and be able
to do whatever it wants with them. However, if we have generalised
hashring classes that can be easily configured to do this subhashring
rotation behaviour (see #12505 for hashring refactoring), this can be
easily used by distributor implementations who wish to better protect
their bridges from any attack enabling rapid bridge enumeration.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1839#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs