[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #2372 [BridgeDB]: Export BridgeDB's pool assignments

#2372: Export BridgeDB's pool assignments
--------------------------+-------------------------------------------------
  Reporter:  karsten      |              Owner:       
      Type:  enhancement  |             Status:  new  
  Priority:  normal       |          Milestone:       
 Component:  BridgeDB     |            Version:       
  Keywords:               |             Parent:  #2537
    Points:               |   Actualpointsdone:       
Pointsdone:               |       Actualpoints:       
--------------------------+-------------------------------------------------

Comment(by karsten):

 Replying to [comment:11 kaner]:
 >> Thanks to kaner's "buckets" thing, there are some distributors that
 just mean that some "unallocated" bridges are written out to files.  These
 bridges (like other unallocated bridges) don't currently exist at all in-
 memory for bridgedb.  I'm starting to think that choice was iffy.
 >
 > They exist in the database. Is that not enough?

 From reading the code it seems that bucket assignment are made persistent
 in the database.  But I didn't play with BridgeDB enough to be sure.

 > Maybe I'm totally off, but I don't think you need any tweaks in BridgeDB
 for what Karsten wants to accomplish -- if I understood correctly. I think
 he could just call `TorBridgeDB --dump-bridges' and read bridge pool
 assignments from those files. Of course a script needs to run over those
 and sanitize them. But that's another discussion maybe.

 I don't think that `--dumpbridges` is doing what I want.  Doesn't that
 just write the file buckets to disk?  I want the assignments of bridges to
 the https/email distributors as well as the unallocated bridges.  Also, I
 want the assignment file to be updated whenever BridgeDB loads new network
 statuses and descriptors and refreshes its internal state.

 Note that sanitizing the output is not an issue here.  This can (and
 should) happen on the same machine that sanitizes bridge descriptors, so
 that we have a single place to change the sanitization process, if
 necessary.

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