TorBox's automatic counteractions (updated 02/08/2021)

[radio24]

With TorBox v.0.4.2, automatic counteractions to avoid downtime and improve user experience with lower bandwidth are introduced. The idea behind this feature is that a routine constantly monitors the tor log file and automatically initiate counteractions if necessary. This feature is especially interesting in places with unstable networks and poor bandwidth. Tor is working very efficiently on a stable network with good bandwidth, but in places with poor Internet connectivity, tor tends to be "stuck". For example, it is starting to (re-)build circuits that take away CPU power and block clients from using the tor network. Usually, a manual restart helps in such a situation.

Currently, TorBox's automatic counteractions handle 4 situations:

1. Protection against entry guard failing and overloaded tor network
2. Protection against interrupted WiFi (wlan0/wlan1) connection with the Internet
3. Protection against an excessive number of failing tor circuits (40 failures in 2 minutes)
4. Protection against excessive connection failing with tor circuits (100 failures in 2 minutes)

The features are divided into three parts:

• log_check.py: monitors the tor log file
• log_check_config.py: configuration file in which a certain amount of log patterns in a specific time triggers an automatic counteraction
• automat: this script defines the counteraction run if triggered

What do we need to know before we could deploy TorBox's automatic counteractions by default?

• Are the pattern looking for in the tor log file good enough, and are there other/better patterns to include?
• Are the amount of counted pattern in a specific time appropriate chosen. We don't want to interfere too often with counteractions, but the feature should be effective. These counteractions should avoid the downtime of the connection to the tor network and give a better user experience, especially on connections with lower bandwidth.
• Are the defined counteractions effective, or are there other/better alternatives?
• How can we combine TorBox's automatic counteractions with Vanguards?

You can help us with answering these questions by activating TorBox's automatic counteractions with entry 12 in the Countermeasure sub-menu. Experts can play around with the settings in the files mentioned above. Please give us feedback about your findings! What is your opinion? Should we activate this feature in its final state as a default with an option to deactivate it, or should we leave the activation of that feature entirely to the users?

[radio24]

Implemented with TorBox version 0.4.2!
However, the topic is not done yet.
Hopefully, we can add some more improvements in the TorBox version 0.4.3 and activate the feature as default.