Open qTox then go to Advanced and scroll down to connection settings → Then disable “Enable IPv6” & “Enable UDP” , change Proxy Type to SOCKS5 , Address to 127.0.0.1 , Port to 9101 (or isolated port for it connection)
Ricochet & Onionshare has an Onion grater issue in “Extend onion-grater Whitelist” instruction step mentioned in the wiki.
CoyIM has an issue of freezing up and not connecting (need to kill it in order to close it) upstream ticket:
Yes since it modifies root owned files. Abolishing user/root separation
(on gateway only) would be a separate discussion.
Applications Test results:
qTox better privacy/Tor compatibility Tips:
Open qTox then go to Advanced and scroll down to connection settings → Then disable “Enable IPv6” & “Enable UDP” , change Proxy Type to SOCKS5 , Address to 127.0.0.1 , Port to 9101 (or isolated port for it connection)
Add Workspace Switcher by default because if you open TBB and then open file manager and then press/hold the file manager top bar and go left of the screen then TBB page will disappear. it didnt disappear actually but the file manager window went to a new workspace. and in order to see all the work spaces you need to add workspace switcher plugin to the taskbar by default.
right click on the taskbar -> go to Panel -> Add New Items -> Workspace Switcher
then move the workspace switcher near to the browser icon (left) for better control.
I just used it normally and clicked register account and it works as expected. Just did it again now.
The hanging connection to the server you saw might be a network connectivity problem at the exit node, or a request throttling done to prevent spammers from that exit’s IP.
EDIT:
Let’s try to connect with coyIM too because there was a bug in the version in Stretch which kept making coy forget added contacts.
First thing I notice is both Gateway and Workstation have a GUI whonixcheck error right after first-run wizards finish:
WARNING: Debian Package Update Check Result: Could not check for software updates! (Timeout reached.) (apt-get code: 124)
Please manually check:
(Open a terminal, Start Menu → System → Terminal.)
Manual apt update / dist-upgrade commands work fine in terminal though.
BTW, should we move from apt-get to apt?
I read last week that the Debian world is moving in the direction of suggesting apt by default and that best practice is such that apt-get should only be used if necessary for a function that apt itself can’t provide (similar to aptitude does over apt-get). It would be neater and less daunting for the user to work with.
I read last week that the Debian world is moving in the direction of suggesting apt by default and that best practice is such that apt-get should only be used if necessary for a function that apt itself can’t provide (similar to aptitude does over apt-get). It would be neater and less daunting for the user to work with.
Citation would be useful. We can consider this after Whonix 15 stable
release.
Yeah I couldn’t find it that time, but found it now. It was this article:
So it seems apt is a little more user-friendly (in general) and is in Debian by default.
It shows in a table that apt-get dist-upgrade → becomes → apt full-upgrade.
Annoying that apt, apt-get and aptitude are all slightly different with different pros vs. cons, but at least we have choice for different situations. I had to use the deluxe aptitude to install a particularly difficult-to-install package that required sid repo dependencies on a Tails Debian the other week.
