Update your TorBox

We have good and bad news…

Bad News
The next TorBox release (v.0.3.3 or v.0.4.0) will probably not be published before the end of March 2021. The reason is that, currently, we travel around and test TorBox in real-world use. The drawn lessons learned will be implemented in the next releases. At the same time, as bandwidth spoiled freaks, we realized that in some places in the world the Internet connections are suicidally slow. This makes a release during our trip pretty much impossible.

Good News
If you have TorBox 0.3.2, you don’t need to wait to update the base system or the Tor version on your TorBox. First, choose entry 1 in the Update and Reset submenu to update your base system (to Linux Kernel 5.4.83). However, this will not update Tor because, for whatever reason, the Tor Project repository doesn’t support armhf anymore. To update Tor, choose entry 3 in the Update and Reset submenu. This will update Tor to the version This version has an improved guard selection algorithms, adds v3 onion balance support and includes fixes for TROVE-2020-005.

The status message seen under entry 3 in the Update and Reset submenu after the update to the newest Tor version.

Travelling around, we expired in some countries a wrong DNS resolution regarding torproject.org. Probably, this is a kind of cheap censorship mechanism. This is why we added to our update script a set of open name servers. In other words, if entry 3 in the Update and Reset submenu produce an error and refuse to update Tor, try first entry 4, leave the Update and Reset submenu (it has to be reloaded) and try entry 3 again. In the next TorBox version, these set of open name servers will be installed as default. Important: these open name servers are only used for the DNS requests directly from the command prompt of the TorBox (during installations, updates, administrative work etc.), but not by the clients. Clients DNS requests are resolved through Tor.

We are working hard to replace wicd with our own lightweight wireless manager for TorBox v.0.4.0. The main reason is that it seems that wicd is not developed further. Several attempts to contact the developers went unanswered. The current version of wicd doesn’t support Python version 3, which produces some headaches under Ubuntu. At the same time, however, it is also an opportunity to significantly simplify the handling of wireless networks in TorBox.

Test version of the new TorBox Wireless Manager, which is replacing wicd in the next major release of TorBox.

One thought on “Update your TorBox”

  1. Thanks for field-testing TorBox! Are you visiting Egypt? Connecting from there has proven to be challenging.

    The described update worked fine on my RPi3B+ with TorBox 0.3.2. The following was performed:

    “13 Go to the update and reset sub-menu”
    “Entry 1: Update the base system (reboot recommended!)”
    Update to Linux 5.4.83-v7+
    Completed successfully in ~5 min
    Reboot performed

    Reconnected, and:
    “Entry 3: Update to the newest version of Tor”
    “13 Go to the update and reset sub-menu”
    Update to tor- (from
    Loads of the “Please check that your locale settings [..] are supported and installed on your system” and “/bin/bash: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)” messages appeared. While updating, client stayed connected to the Tor network. Update completed successfully in ~20 min
    Reboot performed

    Reconnected, and
    “1 Tor statistics” showed everything’s running smoothly on the new kernel and updated tor.

Leave a Reply