#22148: prop140: conformance to proposal, unhandled corner cases ------------------------------+-------------------------------- Reporter: nickm | Owner: nickm Type: defect | Status: new Priority: Medium | Milestone: Tor: 0.3.1.x-final Component: Core Tor/Tor | Version: Severity: Normal | Keywords: Actual Points: | Parent ID: #13339 Points: .5 | Reviewer: Sponsor: Sponsor4 | ------------------------------+-------------------------------- There are some remaining issues in my prop140_complete branch.
We should allocated a protover for directories that support these new requests. Right now, we treat failures to apply a consensus diff as if the consensus download had failed. Is this what we should be doing? The proposal specifies a method for downloading diffs without using the X -Or-Diff-From-Consensus syntax. We should implement that on the server side. Our proposal specifies networkstatus parameters, but the code doesn't implement them. The proposal says that sha3 digests may be truncated in requests: I propose we do not implement that, and revise the proposal to match. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22148> 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