[tor-bugs] #9264 [BridgeDB]: Problem with transport lines in BridgeDB's bridge pool assignment files
Tor Bug Tracker & Wiki
blackhole at torproject.org
Sun Jan 26 03:32:55 UTC 2014
#9264: Problem with transport lines in BridgeDB's bridge pool assignment files
--------------------------+-------------------------------
Reporter: karsten | Owner: isis
Type: defect | Status: needs_information
Priority: major | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
--------------------------+-------------------------------
Comment (by sysrqb):
Replying to [comment:23 karsten]:
> Replying to [comment:22 sysrqb]:
> > So, next stop bridge auth.
>
> This is expected behavior by the bridge authority. It simply sends you
its local descriptor caches, and those may contain older descriptors.
This isn't something to fix, it's supposed to be like that.
>
> Here's how you'd filter out the latest descriptors of currently running
bridges:
>
I missed the fact that you posted this. I was about to say exactly the
same thing - I realize this while working on #10680. This should be fixed
in the next release, if possible.
> Does BridgeDB already use stem? This is something where stem would be
pretty helpful.
Not yet, maybe someday soon but the bridge parsers that are scattered
around need to be integrated into it before bridgedb can use it.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9264#comment:24>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list