Tor-ctrl signal NEWNYM does not work on an updated version of Whonix

Issue- tor-ctrl signal NEWNYM does not work on an updated version of Whonix

Here is some terminal output.

user@host:~$tor-ctrl signal NEWNYM
/usr/bin/tor-ctrl: line 560: tor_control_socket_filesystem: unbound variable

In order to attempt self-support, here is some documentation I looked at- http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/wiki/Tor_Controller#tor-ctrl

tor-ctrl

is installed by default.

For example, to get a new circuit, run:

tor-ctrl signal NEWNYM

The output should show:

250 OK

Repeat this command each time a new circuit is desired.

See also:

man tor-ctrl 

This documentation has not changed for the latest update, so I do not see any evidence that I am supposed to run a different command.

I am using Whonix in Virtualbox, so I am putting this here. Whonix is fully updated, with the exception of one held-back package in whonix-workstation.

Host: ZorinOS 18.1
Virtualbox version: 7.0.16-dfsg-2ubuntu1.3+zorin2
Whonix version-

~$ systemcheck --verbose --function show_versions
[INFO] [systemcheck] Whonix build version[1]: 18.0.8.7

Links:
[1] https://www.whonix.org/wiki/Systemcheck#Build_Version
[INFO] [systemcheck] dist-general-cli: 37.8-1
[INFO] [systemcheck] derivative_major_release_version /etc/whonix_version: 18
~$ systemcheck
[ERROR] [systemcheck] systemd critical journal messages check result (previous boot): Possible system issue detected. Some unusual entries were found in the kernel log.

There is no need to panic. This is not a serious security issue. However, it may affect other system checks. These messages might indicate hardware or software problems.

Detected messages:
Oct 10 00:19:31 host kloak[2377]: libinput error: client bug: timer event2 debounce: scheduled expiry is in the past (-267ms), your system is too slow
Oct 10 00:19:31 host kloak[2377]: libinput error: client bug: timer event2 debounce short: scheduled expiry is in the past (-280ms), your system is too slow

If you know what you are doing, feel free to disable this check.
Create a file /etc/systemcheck.d/50_user.conf and add:
systemcheck_skip_functions+=" check_journal "
[INFO] [systemcheck] Connected to Tor.
[WARNING] [systemcheck] Whonix Unwanted Packages Test Result: 1 unwanted package(s) installed. It is recommended that you remove them from this machine.
1. Open a terminal. (Start Menu - System - Terminal)
2. Purge. sudo apt-get purge python3-pip 
See also: https://www.whonix.org/wiki/Debian_Packages
If you know what you are doing, feel free to disable this check.
Create a file /etc/systemcheck.d/50_user.conf and add:
systemcheck_skip_functions+=" check_unwanted_packages "
[INFO] [systemcheck] Whonix[1] is produced independently of, with no guarantee from, The Tor Project. Whonix is a research project.

Links:
[1] https://www.whonix.org
[INFO] [systemcheck] user-sysmaint-split installation check[1]: Installed 

Links:
[1] https://www.kicksecure.com/wiki/sysmaint
[INFO] [systemcheck] user-sysmaint-split session detection result: USER Session.
[INFO] [systemcheck] Kernel Command-Line Hardening: Present 
[INFO] [systemcheck] Whonix Login[1] Security Check (Colors[2])
:
+----------+--------------------------------------+
| Users    | Password               GUI Autologin |
+----------+--------------------------------------+
| root     | Locked (Present)       Disabled      |
| user     | Absent                 Enabled       |
| sysmaint | Absent                 Enabled       |
+----------+--------------------------------------+

You can adjust these settings using "Manage Passwords" and "Manage GUI Autologin"
in the System Maintenance Panel.
See also: Physical Security[3].

Links:
[1] https://www.kicksecure.com/wiki/Login
[2] https://www.kicksecure.com/wiki/Systemcheck#Login_Security_Check_-_Meaning_of_Colors
[3] https://www.kicksecure.com/wiki/Systemcheck#Physical_Security_Check
[INFO] [systemcheck] Secure Boot[1]: Disabled 

Links:
[1] https://www.kicksecure.com/wiki/Secure_Boot
[INFO] [systemcheck] tirdad - TCP ISN CPU Information Leak Protection[1]: Enabled 

Links:
[1] https://github.com/Kicksecure/tirdad
[INFO] [systemcheck] Whonix APT Repository: Enabled.
When the Whonix team releases TRIXIE updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please read https://www.whonix.org/wiki/Trust to understand the risk. 
If you want to change this, use:
    sudo repository-dist
[INFO] [systemcheck] Debian Package Update Check: Checking for software updates via apt-get... ( Documentation: https://www.whonix.org/wiki/Update )
[INFO] [systemcheck] Debian Package Update[1] Check Result: No updates found via apt-get.

Links:
[1] https://www.whonix.org/wiki/Update
[INFO] [systemcheck] Please donate!
   See: https://www.whonix.org/wiki/Donate

How do I fix this? Thank you.

Looks like a bug in tor-ctrl that wasn’t caught during testing. You likely don’t have Tor configured to create a UNIX control socket (at, for instance, /run/tor/control), and the fallback mechanism in tor-ctrl is currently not working correctly.

As a stop gap, you can undo any configuration changes you made to Tor that resulted in a UNIX control socket not being created.

1 Like

Fix created, pending review and merge:

You could edit /usr/bin/tor-ctrl in sysmajnt mode (or in your Whonix-Gateway template if using Qubes) and add this change manually if you’d like to test the fix out early.

1 Like

I changed that file in both whonix gateway and whonix workstation. I now get the following output.

tor-ctrl: [notice] attempting to connect to fallback socket 127.0.0.1:9051
Connection to 127.0.0.1 9051 port [tcp/*] succeeded!
tor-ctrl: [notice] connecting to socket with command: nc 127.0.0.1 9051
250 OK
250 OK
250 closing connection

Thank you.

2 Likes

Will be part of over next release. I.e. probably

= 18.2.4.3 and above.

1 Like