-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tor broken by ntp #129
Comments
A quick way to provide a user-friendly way to do that, could be add a new menu category (eg: services) and add something like: "tor restart" (that basically execute: "sudo /etc/init.d/tor restart") |
We investigated a bit, and probably the "right" way to do it, is adding boyska |
Paskao will do this |
in ff66f67 it works for me. I did the following test: date -s "2 days ago"
service tor restart
curl -i ifconfig.me
service ntp restart
curl -i ifconfig.me Notice that:
|
@paskao : while I know that the bug you report is true and is grave and should be fixed, there seems to be no clear way to reproduce it. Can you help us in reproducing it? |
See be59f6e at boyska/129-fix-tor-ntp |
I removed the testing-needed label, as it can be confusing. That's the current situation:
|
I managed to reproduce it! It is documented in https://we.riseup.net/freepto-wiki/tor-ntp . The script that make tor fails is http://paste.debian.net/125967/ |
Postponed to v1.1, as v1.0 is already too late |
When ntp update the time can broke the tor circuits connections, and tor must be restarted. But we havent a user-friendly way to do that.
This is what is output in the tor log:
root@freepto # tail -n 2 /var/log/tor/log
Jun 14 20:05:55.000 [warn] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 15; recommendation warn)
Jun 14 18:06:21.000 [notice] Your system clock just jumped 7199 seconds backward; assuming established circuits no longer work.
The text was updated successfully, but these errors were encountered: