-
Notifications
You must be signed in to change notification settings - Fork 27
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
signaling newnym and reloading torrc #62
Comments
Restart should still be a menu entry, but give option to just HUP helps too. # restarting_tor(<source script> <force>)
# Used predefined variables: RED, NOCOLOR
# This function restarts Tor if required with 'force', else it will just sighup.
restarting_tor()
{
SOURCE_SCRIPT=$1
ACTION=$2
if [ "${ACTION}" == "force" ]; then
echo -e "${RED}[+] Restarting tor!${NOCOLOR}"
sudo systemctl restart tor &
echo -e "${RED}[+] DONE! Checking progress - please be patient!${NOCOLOR}"
echo -e " Ignore any error messages, just wait..."
echo -e " At the end, you should see \"Bootstrapped 100%: Done\"."
else
echo -e "${RED}[+] Sending HUP signal to tor!${NOCOLOR}"
sudo pkill -sighup tor &
echo -e "${RED}[+] DONE! Checking progress - please be patient!${NOCOLOR}"
echo -e " Ignore any error messages, just wait..."
fi
echo -e " You can leave the progress report with CTRL-C."
echo ""
sleep 2
trap "bash $SOURCE_SCRIPT; exit 0" SIGINT
sudo tail -f -n 0 /var/log/tor/notices.log
} |
With commit dbd551c, the new_ident script is replaced by |
Regarding the proposal to implement to HUP tor instead of restarting it, I did a few tests during the last few days. So far, I don't see a significant advantage to distingue between a "real" restart and a "reload" of the configuration. On the contrary, the HUP variant gives less information about reloading. Also, I think that with restarting tor, I'm on the safer side, even if it needs more time on some occasions. |
Did you test with bridges? With bridges it has significant difference cause they take more time to bootstrap when restarting and no need to do so when reloading.
It gives then necesssaary info of what it does, reading the config files and data dir
Also, to be on the safer side there is
|
Yes, I tested it with OBFS4 bridges but ran into problems. It didn't seem to work, but I couldn't follow the log because of the reduced log entries. When I restarted tor with the same configuration, I had no problem, and I could follow the log entries if the bridge is used correctly. So, I thought that maybe HUP will not work with OBFS4 bridges. |
There is many ways to signal newnym
new_ident.sh requires password, this can be cut off (using stem will ask for a password, using tor-prompt won't AFAIK, even though I find this strange, my tests resulted this way)
NEWNYM
-i 9051
does not need to be mentioned if using the default port.Also possible to call using stem
HUP
Also, restaring tor just because of editing torrc should not be done for sake of time. There should be an option to restart Tor of course, but just when necessary.
or (this option below does not let you choose ControlPort)
Also possible to call using stem
Source:
The text was updated successfully, but these errors were encountered: