Whonix VirtualBox 15.0.0.0.7 - Debian buster based - Testers Wanted!

Patrick · April 14, 2019, 1:07pm

qtox:

IPv6 might even work. (See IPv6 tests in Tor Browser.)

(Above commit works for new builds only because it is in /etc/skel.)

Proxy settings cannot be applied by default. Related bugs:

github.com/qTox/qTox

[Feature request] Launch options/flags for connection settings

opened 04:08PM - 12 Apr 18 UTC

rdroimfd

proposal M-ui C-feature-request

##### Brief Description OS: Fedora 27 qTox version: (version numbers in menu… `Settings → About`) Commit hash: https://github.com/qTox/qTox/commit/5d0f9509a8d5fac940f402237efe4a8a6ab7e27b toxcore: 0.2.1 ##### Observed Behavior At first I thought I had a bug that deleted settings, because I checked my advanced settings after updating and noticed my connection wasn't set to go through tor and had a random port instead of 9050. I eventually realized it was because I made a new account a few months ago and never set the same connection settings, and connection settings are saved on a per account basis. I thought about ways this might be able to be changed, and the best one I could think of are launch options/cli flag settings to set connection settings, like proxy type/IP/UDP settings etc on launch. Not only would this allow you to easily share this setting between accounts if you choose (such as changing your qTox shortcut to include them thus making any profile load those connection settings), but it would allow you to easily use your chosen settings on newly created accounts without ever having to connect to tox over a connection you don't want to. What I mean is even if I had known I would need to set the connection options again after making a new account, when I first load into the new account, it would attempt to connect to the tox network over my default IP address until I go and manually change things (unless I disable my internet, load into the new profile, change to tor, and then reenable internet). Edit: Was just reading over [this page](https://wiki.tox.chat/users/tox_over_tor_tot) and saw the example for doing it with toxic - " toxic –force-tcp –SOCKS5-proxy 127.0.0.1 9050"

We also cannot use torsocks, bug reported:

github.com/qTox/qTox

torsocks qtox results in segfault

opened 12:58PM - 14 Apr 19 UTC

closed 06:34AM - 27 Jun 19 UTC

adrelanos

U-low C-crash

##### Brief Description * OS: debian buster * qTox version v1.16.3-2-debian.… * Commit hash: build without git * toxcore version: 0.2.9 * Qt version: 5.11.3 ``` dpkg -l | grep qtox ii qtox 1.16.3-2 ``` * Reproducible: Always ##### Steps to reproduce Debian buster sudo apt-get install torsocks qtox torsocks qtox ##### Observed Behavior ``` [12:50:33.070 UTC] persistence/settings.cpp:129 : Debug: No settings file found, using defaults [12:50:33.070 UTC] persistence/settings.cpp:133 : Debug: "Loading settings from :/conf/qtox.ini" [12:50:33.077 UTC] ipc.cpp:61 : Debug: Our global IPC ID is 15713412508552978184 [12:50:33.078 UTC] main.cpp:251 : Debug: commit: build without git [12:50:40.685 UTC] persistence/settings.cpp:2411 : Debug: Creating new profile settings in "/home/user/.config/tox//aaaaaa.ini" [12:50:40.712 UTC] persistence/settings.cpp:462 : Debug: "Saving global settings at /home/user/.config/tox/qtox.ini" [12:50:40.755 UTC] persistence/settings.cpp:335 : Debug: Loading personal settings from "/home/user/.config/tox/aaaaaa.ini" [12:50:40.756 UTC] nexus.cpp:87 : Debug: Starting up [12:50:40.970 UTC] core/core.cpp:197 : Debug: Creating a new profile [12:50:40.970 UTC] core/toxoptions.cpp:63 : Debug: Core starting with IPv6 enabled [12:50:40.971 UTC] core/toxlogger.cpp:57 : Warning: "ERROR:network.c:new_networking_ex:764: Failed to get a socket?! 1, Operation not permitted" [12:50:40.971 UTC] core/toxlogger.cpp:57 : Warning: "ERROR:network.c:new_networking_ex:764: Failed to get a socket?! 1, Operation not permitted" [12:50:40.971 UTC] core/core.cpp:152 : Critical: can't to bind the port [12:50:41.843 UTC] widget/systemtrayicon.cpp:83 : Debug: Using the Qt backend Segmentation fault ``` journal: ``` Apr 14 12:48:02 host kernel: qTox Core[4416]: segfault at 0 ip 00007f3acac88cd0 sp 00007f3aa4b69ff0 error 4 in libtoxcore.so.2.9.0[7f3acac61000+31000] ``` ##### Expected Behavior qtox functional.