[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21493 [Core Tor/Tor]: When reachable addresses change, mark connections using those addresses
#21493: When reachable addresses change, mark connections using those addresses
--------------------------+------------------------------------
Reporter: teor | Owner:
Type: defect | Status: closed
Priority: Medium | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution: fixed
Keywords: ipv6 | Actual Points: 0
Parent ID: | Points: 1
Reviewer: | Sponsor:
--------------------------+------------------------------------
Comment (by cypherpunks):
Replying to [comment:8 teor]:
> Replying to [comment:7 cypherpunks]:
> > In any codebase, subtle changes, like this, being practically
undocumented, and evidently hidden from both users and developers, is a
source of confusion and a hindrance to future debugging.
>
> There are a lot of subtle changes when a subsystem is rewritten.
> That's just how it works.
>
> This change was implemented in a recent alpha:
> "to better support unreliable networks and restrictive sets of entry
nodes"
>
https://gitweb.torproject.org/tor.git/tree/ChangeLog?id=ac04fcd2e758c2258cbde8c8f31586695cb5d666#n12
That entry makes no reference to this change.
>
> And it was fully documented in proposal 271:
> https://gitweb.torproject.org/torspec.git/tree/proposals/271-another-
guard-selection.txt#n648
> https://gitweb.torproject.org/torspec.git/tree/proposals/271-another-
guard-selection.txt#n114
That is no explicit documentation, and was not enough for a user or system
integrator, or a developer, to decode and guess that the change had taken
place.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21493#comment:9>
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