[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #20828 [Core Tor/Tor]: Should we provide a migration method from the old guard logic to the new one?

Subject: Re: [tor-bugs] #20828 [Core Tor/Tor]: Should we provide a migration method from the old guard logic to the new one?
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Mon, 12 Dec 2016 04:46:53 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sun, 11 Dec 2016 23:47:02 -0500
In-reply-to: <045.4edd35f33161afe663c5e0a9daaeb4bd@torproject.org>
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
References: <045.4edd35f33161afe663c5e0a9daaeb4bd@torproject.org>
Reply-to: no-reply@xxxxxxxxxxxxxx, tor-assistants@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#20828: Should we provide a migration method from the old guard logic to the new
one?
--------------------------+------------------------------------
 Reporter:  nickm         |          Owner:
     Type:  defect        |         Status:  new
 Priority:  High          |      Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tor-guard     |  Actual Points:
Parent ID:  #20822        |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by teor):

 This provides a client upgrade distinguisher: when a client suddenly
 starts trying N new IP addresses, it has upgraded to 0.3.0.

 Fortunately, we plan on adding ~130 new fallback directory mirrors in
 0.2.9 and 0.3.0 (#18828), so the new guards would be somewhat hidden, at
 least every time the client consensus expires.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20828#comment:2>
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

Prev by Author: Re: [tor-bugs] #20941 [Applications/Tor Browser]: Tor browser will resize it self after the dock is enabled and the browser is dragged to a new location
Next by Author: Re: [tor-bugs] #20809 [Applications/Tor Browser]: Use non-/html search engine URL for DuckDuckGo search plugins
Previous by thread: Re: [tor-bugs] #20950 [Core Tor/Tor]: Design guard algorithm tweaks to be more tolerant when picking directory guard.
Next by thread: Re: [tor-bugs] #20828 [Core Tor/Tor]: Should we provide a migration method from the old guard logic to the new one?
Index(es):
- Author
- Thread