#25544: Complete vanguard specification -------------------------------------------------+------------------------- Reporter: asn | Owner: (none) Type: defect | Status: | needs_review Priority: Medium | Milestone: Tor: | 0.3.4.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-guard, torspec, guard- | Actual Points: discovery, 034-roadmap-master, | 034-triage-20180328, 034-included-20180328 | Parent ID: | Points: Reviewer: asn | Sponsor: | SponsorV -------------------------------------------------+-------------------------
Comment (by asn): Replying to [comment:6 mikeperry]: > After sitting down to work on this, I decided we should supersede proposal 247 with a new proposal for mesh-based vanguards, so we can keep the old proposal text around. > > https://gitweb.torproject.org/user/mikeperry/torspec.git/tree/proposals /xxx-mesh-vanguards.txt?h=mesh- vanguards&id=d588585d1cb37d5f8f0002692ba6dcb0bd0f552e > > I based that branch off of some notes I took from mailinglist discussion on prop247 that never got merged. Figure why not keep that for the archives, too. Good stuff. I agree with the new proposal idea. I was not sure where to comment, so I started a new PR and commented within: https://github.com/torproject/torspec/pull/9/files Things look pretty good and as expected. I was mainly surprised about the introduction of the max(X,X) distribution which was not discussed in the past months. I wonder what it offers. To better investigate it, I added a new commit to the vanguard simulator that implements max(X,X). -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25544#comment:7> 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