Mon, Feb 18
Other imporvements in this thread such as functioning SMTP gateways are also part of this ticket:
Sat, Feb 2
Middle of the range solution. How does this sound? Confirmed it falls within the private address CIDR:
Thu, Jan 31
Dec 9 2018
Dec 5 2018
My advice is to use a private address range reserved for this purpose by IANA. These will never be used in the future by anyone. Sine we use 10.x.x.x and moved away from 192.x.x.x, this leaves 172.x.x.x
Nov 28 2018
Removed for now.
Mar 7 2018
Feb 21 2017
One mistake fixed.
This unfortunately has quite a chance to have messed up an argument an introduce a regression.
Jan 18 2017
Aug 5 2016
Apr 26 2016
Apr 21 2016
Apr 11 2016
deb.torproject.org: merge obfs4proxy apt repository into regular deb.torproject.org repositories:
Apr 8 2016
Dec 9 2015
xdg desktop specification feature request:
desktop entry to maximize terminal TerminalMaximized=true
Nov 26 2015
Nov 24 2015
Nov 23 2015
redirect tinyproxy traffic to 127.0.0.1 instead to qubes-netvm-gateway
Nov 19 2015
Aug 19 2015
fixed obfsproxy AppArmor issue "OSError: [Errno 13] Permission denied: '/rw/usrlocal/lib/python2.7/dist-packages'" using superior /etc/apparmor.d/tunables/home.d/qubes-whonix-anondist solution - https://phabricator.whonix.org/T396:
Aug 15 2015
Actually, that's a much better solution.
Got another answer.
Aug 14 2015
AppArmor upstream feature request - symlink support:
A real fix would require having an AppArmor option to follow symlinks.
Jul 29 2015
Anything left to do here? Besides testing as soon as a new test image is released?
Jul 11 2015
It would be confusing if users wanted to restore their old folder before they start. But nevermind. It's a non-issue. The postinst will have /var/lib/tor created already.
I'm not sure. Its not a problem f it doesn't fail hard with a confusing error message. The time between enabling Tor and using the folder will be small enough that it won't inconvenience anyone.