Re: [tor-bugs] #4026 [BridgeDB]: let us choose the bridge pool assignment for a set of bridges by fingerprint

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#4026: let us choose the bridge pool assignment for a set of bridges by
fingerprint
-----------------------------+----------------------
     Reporter:  arma         |      Owner:  isis
         Type:  enhancement  |     Status:  assigned
     Priority:  normal       |  Milestone:
    Component:  BridgeDB     |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+----------------------
Changes (by isis):

 * status:  new => assigned
 * cc: isis (added)
 * owner:   => isis


Comment:

 This would be rather difficult to implement, as it would require BridgeDB
 to look up each bridge in the databases, hashrings, subhashrings, and
 caches, rip out the bridge, and then reassign it (and re-commit the
 transaction) to its new place in all those structures. It wouldn't be
 pretty.

 Other than that, I am concerned about the maintainability of such a
 feature. How does the bridge operator get this list of fingerprints to me?
 Likely case, they would have to Pond it to me, or GPG-encrypt and email it
 to me, and then I'd have to manually SCP it to ponticum. And we'd have to
 do this dance every time someone's list changes. Unless someone can
 recommend a better way to do this?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4026#comment:1>
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