On 2 February 2017 at 21:07, teor teor2345@gmail.com wrote:
On 2 Feb 2017, at 14:02, Iain R. Learmonth irl@torproject.org wrote:
Hi,
On Tue, Jan 31, 2017 at 10:09:33AM -0600, Tom Ritter wrote:
I think that's fine. I'm happy to be the primary POC and have you in the wings to help with your respective specialties and manage the calendar so things work out =)
This sounds good to me. I'm irl in IRC if you need details from me. Let me know if I'll need to sign up in the Google dashboard thingy.
I could spend an hour or two on this some weeks, to comment on some parts of the project. Please see my comments below.
- Draft (and implement) a core-tor a proposal to expose bwauth vote
documents on DirAuths (Proposal, C)
The bandwidths are already in the votes. Does this mean exposing the entire bwauth document at a DirPort URL?
Yes.... Exposing this document (https://bwauth.ritter.vg/bwauth/bwscan.V3BandwidthsFile) at a URL like (http://171.25.193.9:443/tor/status-vote/current/authority)
- Draft a plan to enable detection of relays falling between scanners
in torflow (Proposal)
- Enhance torflow to expose scanner information for relays (which
scanner the relay ran on and similar information) (Python)
- Implement the analysis tools to detect when relays do fall between
scanners (Python?)
I could comment on draft interfaces, but don't know enough to help with the implementation on:
- Enhance Collector to download and archive these documents (Java)
- Enhance OnionOO to expose bwauth data (Java)
- Enhance Atlas to expose bwauth voting information per-relay to show
historical measurements and scanning status (HTML/JavaScript/CSS)
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-project mailing list tor-project@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-project