#26970: Privcount: plan the modules and components -------------------------------------------------+------------------------- Reporter: teor | Owner: teor Type: task | Status: | assigned Priority: Medium | Milestone: Tor: | 0.3.5.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: privcount, 035-roadmap-master, 035 | Actual Points: -triaged-in-20180711, rust | Parent ID: #25669 | Points: Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by chelseakomlo): Ok, here are a few questions/clarifications: 1. Tor main codebase will include: - The Rust "Data Collector" module - Tools for creating/validating configuration. Question: Will the configuration management tooling also be in Rust? Or will this be part of tor's existing configuration validation/etc? Will this configuration management be the same as for the Tally Reporter? 2. A separate pure-Rust binary - This will be the "Tally Reporter" Question: Will this binary be a sidecar to Tor relays, or will this be stand-alone (like a bwauth)? How will this communicate with the Rust module in core tor? Maybe the first step is to separate out these components (if they aren't already, apologies if I missed that)? The pure-Rust binary will be much easier, and reviewing it will be different than reviewing components that will integrate with C (for example, logging will be different, etc). Maybe then the second step is to work on integrating the Rust "Data Collector" into core tor, and there we can do a review for the FFI layer, etc? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26970#comment:1> 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