Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-16T01:10:32Zhttps://gitlab.torproject.org/legacy/trac/-/issues/32870Bump version of pion webrtc in Tor Browser2020-06-16T01:10:32ZCecylia BocovichBump version of pion webrtc in Tor BrowserIt's time to update the pion webrtc library used by Snowflake. There have been some security updates since `v2.1.3`, and we suspect this will solve some issues on windows.
We'll have to use the method outlined by dcf in #28942 since we ...It's time to update the pion webrtc library used by Snowflake. There have been some security updates since `v2.1.3`, and we suspect this will solve some issues on windows.
We'll have to use the method outlined by dcf in #28942 since we don't have go module support yet in rbm.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/legacy/trac/-/issues/22148prop140: conformance to proposal, unhandled corner cases2020-06-13T15:08:29ZNick Mathewsonprop140: conformance to proposal, unhandled corner casesThere 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 fail...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.Tor: 0.3.1.x-finalNick MathewsonNick Mathewson