#29480: Expose bridge pool assignments again ------------------------------------+-------------------------- Reporter: irl | Owner: phw Type: defect | Status: assigned Priority: Medium | Milestone: Component: Circumvention/BridgeDB | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------------+--------------------------
Comment (by phw): Replying to [comment:5 phw]: > I agree. I'm happy to flip the switch and have BridgeDB expose the assignments again. Is there anything else that's needed from the metrics side? [[br]] It looks like BridgeDB [https://gitweb.torproject.org/bridgedb.git/commit/?id=f4d559197e06bc4b2e783634d6e79232a440025f changed a bit] since metrics last archived these files. What file format were you dealing with? And how did you get access to the assignments file? What BridgeDB currently has is an assignments.log file that is structured as follows: {{{ bridge-pool-assignment 2019-07-24 00:00:10 C042E360BB0139ABA8C115A61CAC4F5A65D86A9B moat ip=4 ring=2 7A95FB316A8D6FE64F24F1742DE066EEBF04A930 moat ip=4,6 ring=2 flag=stable transport=websocket,fte,obfs3,scramblesuit,obfs4 6CC4EC0313D2D823EC2AEF5F5179579F09CB48B0 moat ip=4 ring=2 transport=obfs4 ... }}} -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29480#comment:6> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs