[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23506 [Core Tor/Tor]: clock_skew_warning should be a bootstrap event
#23506: clock_skew_warning should be a bootstrap event
------------------------------------+--------------------------
Reporter: catalyst | Owner: catalyst
Type: defect | Status: assigned
Priority: High | Milestone:
Component: Core Tor/Tor | Version:
Severity: Major | Resolution:
Keywords: bootstrap usability ux | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
------------------------------------+--------------------------
Changes (by mcs):
* cc: brade, mcs (added)
Comment:
Replying to [comment:2 catalyst]:
> That's one possibility, but the Tor Launcher devs have rejected that
before for various reasons, and this is the best way to get a substantial
usability improvement with the existing Tor Launcher.
Hmm. I don't think we rejected that idea. When Kathy and I experimented
with it, we found that in our testing it did not solve the problem.
Specifically, a CLOCK_SKEW event was generated before Tor Launcher had
established its control port connection, so Tor Launcher did not see it.
But as I write this I wonder if our testing was flawed, because if we
start tor with DisableNetwork=1, then connect to the control port, then
monitor STATUS_GENERAL events, it seems like we would see the first
CLOCK_SKEW event (but I know very little about tor internals).
Anyway, somewhere I have experimental code that monitors CLOCK_SKEW
events... so if that is the Right Thing To Do we can add it to Tor
Launcher.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23506#comment:3>
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