{"id":2867,"date":"2022-07-20T06:27:06","date_gmt":"2022-07-20T05:27:06","guid":{"rendered":"https:\/\/www.torbox.ch\/?p=2867"},"modified":"2023-01-06T06:45:38","modified_gmt":"2023-01-06T05:45:38","slug":"torbox-v-0-5-1-released-smashing-bugs","status":"publish","type":"post","link":"https:\/\/www.torbox.ch\/?p=2867","title":{"rendered":"TorBox v.0.5.1 released \u2014 smashing Bugs"},"content":{"rendered":"\n<p>Honestly, TorBox v.0.5.0 was not one of our finest. When I started to fix some known problems and bugs almost a month ago, I found so much more. It was time to go into details and especially to fix to code added with version 0.5.0 &#8211; row by row. This version should run more reliable and stable than the versions before. Nevertheless, we also added and updated some of the features. However, once again, it shows also the importance of user feedback. Please report to us your problems and found bugs. We also need to know what you would like to see next and which features you request? With the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\" target=\"_blank\">TorBox GitHub repository<\/a>, it is straightforward for everyone to&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\/issues\" target=\"_blank\">report issues<\/a>&nbsp;or change the code and propose it in a&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\/pulls\" target=\"_blank\">pull request<\/a>.&nbsp;<\/p>\n\n\n\n<p><strong>TorBox Image<\/strong> (about 1 GB):&nbsp;<a href=\"https:\/\/www.torbox.ch\/data\/torbox-20220719-v051.gz\">v.0.5.1 (19.07.2022)<\/a>&nbsp;\u2013&nbsp;<a href=\"https:\/\/www.torbox.ch\/?page_id=1128\">SHA-256 values<\/a><br><strong>TorBox Menu only:<\/strong>&nbsp;<a href=\"https:\/\/www.torbox.ch\/data\/torbox051-20220719.zip\">v.0.5.1 (19.07.2022)<\/a>&nbsp;\u2013&nbsp;<a href=\"https:\/\/www.torbox.ch\/?page_id=1128\">SHA-256 values<\/a><\/p>\n\n\n\n<p>Since we had to install additional software packages and update the configuration files,&nbsp;<strong>it is necessary to use the new image<\/strong>&nbsp;or reinstall TorBox using&nbsp;<a href=\"https:\/\/www.torbox.ch\/?page_id=1168\">one of our installation scripts<\/a>.<\/p>\n\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large is-resized\"><a href=\"https:\/\/www.torbox.ch\/wp-content\/uploads\/2022\/07\/main_menu_TorBox051-e1658260547242.png\"><img decoding=\"async\" src=\"https:\/\/www.torbox.ch\/wp-content\/uploads\/2022\/07\/main_menu_TorBox051-1024x681.png\" alt=\"Main Menu TorBox v.0.5.1\" class=\"wp-image-2871\" width=\"760\"\/><\/a><figcaption class=\"wp-element-caption\">Main Menu TorBox v.0.5.1<\/figcaption><\/figure>\n<\/div>\n\n\n\n\n<h5 class=\"wp-block-heading\"><strong>Changelog: v.0.5.0<\/strong>&nbsp;<strong>\u2013&gt; v.0.5.1 (19.07.2022)<\/strong><\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Update:<\/strong>&nbsp;The system is based on&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/www.raspberrypi.org\/software\/operating-systems\/\" target=\"_blank\">Raspberry Pi OS &#8220;Bullseye&#8221; lite (64 bit)<\/a>&nbsp;with&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/kernelnewbies.org\/Linux_5.15\" target=\"_blank\">Linux Kernel 5.15.32<\/a>&nbsp;and&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/gitweb.torproject.org\/tor.git\/plain\/ChangeLog?id=tor-0.4.7.8\" target=\"_blank\">Tor version 0.4.7.8.<\/a>&nbsp;This version fixes several bug fixes, including a high severity security issue categorised as a Denial of Service. Everyone running an earlier version should upgrade to this version. Also, congestion control should improve traffic speed and stability on the network once most exit nodes upgrade. You can find more details about it in&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/gitlab.torproject.org\/tpo\/core\/torspec\/-\/blob\/1a6d9795390da0f1556c554e8b0209b966c88767\/proposals\/324-rtt-congestion-control.txt\" target=\"_blank\">proposal 324 in the torspec.git repository<\/a>. All installation scripts are updated to work with Raspberry Pi OS &#8220;Bullseye&#8221;,&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/www.torbox.ch\/?page_id=1168#others\" target=\"_blank\">Debian 11 and Ubuntu Server 22.04 LTS<\/a>. Additionally, we also updated TorBox&#8217;s internal list of&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/2019.www.torproject.org\/docs\/pluggable-transports.html\" target=\"_blank\">OBFS4 bridges<\/a>.<\/li>\n\n\n\n<li><strong>Update<\/strong>: The installation script for Raspberry Pi OS had to be updated to work with the new Raspberry Pi OS images released in April. Also, starting with this version,&nbsp;<strong>TorBox will be only tested on the 64 bit version of the respective OS (Raspberry Pi OS, Debian and Ubuntu)<\/strong>.<\/li>\n\n\n\n<li><strong>Update<\/strong>: <code>vitor<\/code> from&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/nyxnor\/onionwash\" target=\"_blank\">nyxnor&#8217;s onionwash repository<\/a>.&nbsp;<\/li>\n\n\n\n<li><strong>Update<\/strong>: the additional network driver so that they work with the new Linux kernel (unfortunately,&nbsp;<a rel=\"noreferrer noopener\" href=\"http:\/\/downloads.fars-robotics.net\/wifi-drivers\/\" target=\"_blank\">Fars-Robotics<\/a>&nbsp;didn&#8217;t update their network driver since October 2021).<\/li>\n\n\n\n<li><strong>New<\/strong>: <code>webssh<\/code> replaces&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/shellinabox\/shellinabox\" target=\"_blank\"><code>shellinabox<\/code><\/a>, which seems it is not maintained anymore. With <code>webssh<\/code>, users don&#8217;t need a ssh client because every web browser can now jump in as a ssh client. A user on a wifi-client can type&nbsp;<a rel=\"noreferrer noopener\" href=\"http:\/\/192.168.42.1\" target=\"_blank\">192.168.42.1<\/a>, someone on a cable-client&nbsp;<a rel=\"noreferrer noopener\" href=\"http:\/\/192.168.43.1\" target=\"_blank\">192.168.43.1<\/a>. This functionality comes with a certain risk because <code>webssh<\/code> is not encrypted (this would need a self-signed certificate, which the browser doesn&#8217;t support easily). However, this shouldn&#8217;t cause any problems because the TorBox AP and its wlan or the connection cable should be controlled by you. By default, <code>webssh<\/code> cannot be accessed from the Internet. If you seek maximum security, you still can keep using an ssh client and even deactivate the <code>webssh<\/code> functionality in the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/www.torbox.ch\/?page_id=875\" target=\"_blank\">Configuration sub-menu<\/a>&nbsp;(entry 11).&nbsp;<\/li>\n\n\n\n<li><strong>New<\/strong>: There is a new way to pass through&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/en.wikipedia.org\/wiki\/Captive_portal\" target=\"_blank\">captive portals<\/a>&nbsp;by SPOOFING the MAC address of a device that passed the captive portal successfully. Tests showed that some captive portals could be better overcome with the old method (TUNNELLING), some function better with SPOOFING and some need combined both ways. See&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/www.torbox.ch\/?page_id=2666\" target=\"_blank\">here<\/a>&nbsp;for more information.<\/li>\n\n\n\n<li><strong>New<\/strong>: Starting with this version, TorBox randomises the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/en.wikipedia.org\/wiki\/MAC_address\" target=\"_blank\">MAC addresses<\/a>&nbsp;on  <code>wlan0<\/code>, <code>wlan1<\/code>, <code>eth0<\/code> and <code>eth1<\/code> by default. You can change that behaviour and set your own MAC address in the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/www.torbox.ch\/?page_id=875\" target=\"_blank\">Configuration sub-menu<\/a>&nbsp;(entry 8).<\/li>\n\n\n\n<li><strong>Fixed<\/strong>: TorBox will not try to back up the OBFS4 Bridge Relay configuration if there is no such configuration.<\/li>\n\n\n\n<li><strong>Fixed<\/strong>: It is impossible to simultaneously run the countermeasure against tightly configured firewalls and Snowflake, Meek and the OBFS4 Bridge Relay. This fix will prevent such a setting.<\/li>\n\n\n\n<li><strong>Fixed<\/strong>: A bug broke the functionality on <code>ppp0<\/code> and usb0. Also, before executing <code>pon<\/code>, TorBox will check if <code>pppd<\/code> is already working and shut it down.<\/li>\n\n\n\n<li><strong>Fixed<\/strong>: Due to a little bug in the script, The menu entry, which should only activate OBFS4 bridges, which are ONLINE, fails to activate the OBFS4 mode properly. This bug prevents TorBox from deactivating the OBFS4 lines in the tor configuration file. Both are fixed.<\/li>\n\n\n\n<li><strong>Fixed<\/strong>: Onion Service name bug (<a href=\"https:\/\/github.com\/radio24\/TorBox\/issues\/146\">fixed by nyxnor<\/a>).<\/li>\n\n\n\n<li><strong>Improved<\/strong>: To prevent future bugs in the releases, <a href=\"https:\/\/github.com\/ludeeus\/action-shellcheck\">a shellcheck Github action<\/a> will be triggered <a href=\"https:\/\/github.com\/radio24\/TorBox\/actions\">with every pushed commit on the master repository<\/a>.<\/li>\n\n\n\n<li><s><strong>Improved<\/strong>: Local DNS resolution will be solely resolved through tor. This means that TorBox will not be able to resolve DNS requests from the local terminal if tor is not running. However, some functions, like Snowflake, Meek and time synchronisation, need clearnet DNS resolution to work without a running tor, but in this case, clearnet DNS resolution is explicitly activated for that purpose, and the user is asked or informed beforehand. DNS resolution from clients will always be made through tor, regardless of the settings. With the following commands in the terminal, local clearnet resolution can be set on\/off (we will add that later in a &#8220;toxic &#8220;menu):<\/s><\/li>\n<\/ul>\n\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\n# Turn local clearnet DNS resolution on\nsudo iptables -t nat -D OUTPUT -p udp --dport 53 -j DNAT --to 127.0.0.1:9053\nsudo iptables -t nat -D OUTPUT -p tcp --dport 53 -j DNAT --to 127.0.0.1:9053\nsudo systemctl restart dnsmasq\n<\/pre><\/div>\n\n<div class=\"wp-block-syntaxhighlighter-code \"><pre class=\"brush: bash; title: ; notranslate\" title=\"\">\n# Turn local clearnet DNS resolution off\nsudo systemctl stop dnsmasq\nsudo iptables -t nat -A OUTPUT -p udp --dport 53 -j DNAT --to 127.0.0.1:9053\nsudo iptables -t nat -A OUTPUT -p tcp --dport 53 -j DNAT --to 127.0.0.1:9053\n<\/pre><\/div>\n\n\n<p><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Improved<\/strong>: The use of Onion Services, sharing folder and TFS. For example, the sharing folder functionality and TFS can use every folder inside <code>\/var\/www <\/code>regardless of the name of the Onion Service. This gives the possibility that an Onion domain named <code>x.onion<\/code> can share the folder <code>\/var\/www\/to_be_shared<\/code>, and at the same time, TFS can control up- and\/or downloads to\/from the same folder using the Onion domain <code>y.onion<\/code>.<\/li>\n\n\n\n<li><strong>Improved<\/strong>: TFS can be started multiple times with different Onion domains. The file list is now alphabetically sorted. The message below the top banner can now display multiple lines (separated by a <code>\\n<\/code>). You can go into a sub-folder if you click on them, and if you start an upload in such a sub-folder, the uploaded files are placed there. Selecting multiple files and folders is now supported &#8211; they will be downloaded and compressed in a <code>.zip<\/code> file to the local client.<\/li>\n\n\n\n<li><strong>Improved<\/strong>: Resetting Tor and enforcing a change of the permanent entry node in the update and maintenance sub-menu doesn&#8217;t deactivate the bridge and bridge relay mode anymore.<\/li>\n\n\n\n<li><strong>Improved<\/strong>: Turning <code>systemd-journald.service<\/code> off by default to further reduce the logs.<\/li>\n\n\n\n<li><\/li>\n<\/ul>\n\n\n\n<h1 class=\"has-text-align-center wp-block-heading\">\u2022 \u2022 \u2022<\/h1>\n\n\n\n<h5 class=\"wp-block-heading\">We need your feedback!!<\/h5>\n\n\n\n<p>We hope this version pleases you. However, we are dependent on feedback. It is not just about fixing bugs and improving usability, but also about supporting additional interfaces and hardware in future releases:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What do you like?<\/li>\n\n\n\n<li>What should be improved (why and how)?<\/li>\n\n\n\n<li>What would you like to see next? Which features do you request?<\/li>\n<\/ul>\n\n\n\n<p>With the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\" target=\"_blank\">TorBox GitHub repository<\/a>, it is straightforward for everyone to&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\/issues\" target=\"_blank\">report issues<\/a>&nbsp;or change the code and propose it in a&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\/pulls\" target=\"_blank\">pull request<\/a>.&nbsp;Because we continue to travel around, it sometimes needs more time to address the issues and proposals.&nbsp;<\/p>\n\n\n\n<p>For future versions, it is essential that we know what you need and want to see from the Onion Services implementation. Please feel free to use the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/github.com\/radio24\/TorBox\/discussions\" target=\"_blank\">discussion forum<\/a>&nbsp;to tell us your needs.<\/p>\n\n\n\n<h1 class=\"has-text-align-center wp-block-heading\">\u2022 \u2022 \u2022<\/h1>\n\n\n\n<h5 class=\"wp-block-heading\">Known problems and bugs<\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>BUG<\/strong>: TorBox will not automatically add a bridge when that option is chosen in the <a href=\"https:\/\/www.torbox.ch\/?page_id=797\">Countermeasure sub-menu<\/a>. There are two reasons: <br>.\n<ul class=\"wp-block-list\">\n<li>It seems that version 0.4.8 of mechanize will not be correctly installed &#8211;&gt; we had to switch back to version 0.4.7<br>You can fix that bug manually with the following commands:<br><code>sudo pip3 uninstall mechanize<br>sudo pip3 install mechanize==0.4.7<\/code><br><\/li>\n\n\n\n<li>The script&nbsp;<code>bridges_get.py<\/code>&nbsp;started to fail because the HTML generated by&nbsp;<a href=\"https:\/\/bridges.torproject.org\/bridges?transport=obfs4\">https:\/\/bridges.torproject.org\/bridges?transport=obfs4<\/a>&nbsp;has changed &#8211;&gt; we added the patch from lockcda (see <a href=\"https:\/\/github.com\/radio24\/TorBox\/issues\/173\">issue #173<\/a> on GitHub). You can replace the old script with the patched one by<strong> <\/strong>updating the TorBox&nbsp;menu with the <a href=\"https:\/\/www.torbox.ch\/?page_id=1410\">Update and Maintenance sub-menu<\/a>. <strong><strong>BUG FIXED<\/strong>\u2714\ufe0e<\/strong><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PROBLEM<\/strong>:&nbsp;Installing TorBox using one of the installation scripts or updating tor using the <a href=\"https:\/\/www.torbox.ch\/?page_id=1410\">Update and Maintenance sub-menu<\/a> fails or installs an older version of tor. The problem lies in how GitHub reports to the script&#8217;s question about which versions of tor are available. We changed all affected scripts. New installations with the installation scripts are not affected by this problem anymore. For updating tor on a running system, please fix the problem by updating the TorBox&nbsp;menu with the <a href=\"https:\/\/www.torbox.ch\/?page_id=1410\">Update and Maintenance sub-menu<\/a>. <strong>BUG FIXED<\/strong>\u2714\ufe0e<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Honestly, TorBox v.0.5.0 was not one of our finest. When I started to fix some known problems and bugs almost a month ago, I found so much more. It was time to go into details and especially to fix to code added with version 0.5.0 &#8211; row by row. This version should run more reliable &hellip; <a href=\"https:\/\/www.torbox.ch\/?p=2867\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;TorBox v.0.5.1 released \u2014 smashing Bugs&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","footnotes":""},"categories":[3],"tags":[],"class_list":["post-2867","post","type-post","status-publish","format-standard","hentry","category-blog"],"uagb_featured_image_src":{"full":false,"thumbnail":false,"medium":false,"medium_large":false,"large":false,"1536x1536":false,"2048x2048":false,"post-thumbnail":false},"uagb_author_info":{"display_name":"John Doe","author_link":"https:\/\/www.torbox.ch\/?author=2"},"uagb_comment_info":0,"uagb_excerpt":"Honestly, TorBox v.0.5.0 was not one of our finest. When I started to fix some known problems and bugs almost a month ago, I found so much more. It was time to go into details and especially to fix to code added with version 0.5.0 &#8211; row by row. This version should run more reliable&hellip;","_links":{"self":[{"href":"https:\/\/www.torbox.ch\/index.php?rest_route=\/wp\/v2\/posts\/2867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.torbox.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.torbox.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.torbox.ch\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.torbox.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2867"}],"version-history":[{"count":25,"href":"https:\/\/www.torbox.ch\/index.php?rest_route=\/wp\/v2\/posts\/2867\/revisions"}],"predecessor-version":[{"id":3052,"href":"https:\/\/www.torbox.ch\/index.php?rest_route=\/wp\/v2\/posts\/2867\/revisions\/3052"}],"wp:attachment":[{"href":"https:\/\/www.torbox.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.torbox.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.torbox.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}