[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7144 [Core Tor/Tor]: Implement Bridge Guards and other anti-enumeration defenses
#7144: Implement Bridge Guards and other anti-enumeration defenses
-------------------------------------------------+-------------------------
Reporter: karsten | Owner: isis
Type: project | Status:
Priority: High | needs_revision
Component: Core Tor/Tor | Milestone: Tor:
Severity: Normal | 0.2.9.x-final
Keywords: SponsorZ, tor-bridge, | Version:
027-triaged-1-out, 028-triage, 028-triaged, | Resolution:
isis201604, isis201605, TorCoreTeam201605, | Actual Points:
TorCoreTeam-postponed-201604 | Points: 3
Parent ID: | Sponsor:
Reviewer: | SponsorS-can
-------------------------------------------------+-------------------------
Comment (by teor):
The code is great - it's well-structured and a joy to read.
But I wonder about the code copied from the base OR code:
* have the changes to the OR code in 0.2.8 also been made in the copied
code? (T7)
(I wonder if this could be causing subtle breakage. But I have no evidence
either way.)
OK, now I'm done reading, time to debug:
Once this patch is applied, chutney clients never download a microdesc
consensus, even though the authorities have one. (But this works ok in
maint-0.2.8.) I need to look into the code that's executed when a client
asks an authority for a consensus for the first time. And I need to look
at the code that this patch adds to existing tor OR code.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7144#comment:41>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs