ID: 29PHID: PHID-TASK-k64d7m7is7oa75lykalwAuthor: PatrickStatus at Migration Time: resolvedPriority at Migration Time: Normal
Always start Tor Browser with --allow-remote.
Otherwise there will be an error message:Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.
2014-12-12 01:27:10 UTC
2015-01-06 22:49:03 UTC
I am independently developing some Qubes software which will also benefit Whonix on the Qubes platform. And am in need of this --allow-remote functionality as a default for Whonix Qubes in upcoming months.
I see that T24 “wait for Debian jessie to become the new Debian stable release” is setup as a blocker for Whonix 10 and this is T29 is also tagged for Whonix 10.
Wondering if Whonix 10 and Debian Jessie stable will hold up this important --allow-remote functionality for Tor Browser for longer than 3 months or so? Could certainly use --allow-remote as default in the near future!
2015-01-06 23:46:08 UTC
I see that T24 “wait for Debian jessie to become the new Debian stable release” is setup as a blocker for Whonix 10 and this is T29 is also tagged for Whonix 10.
The tracker is not all that strict. Having jessie or not is not a strict blocker for Whonix 10. Gladly, the policy still man made and debatable.
If Whonix 10 will be based on jessie or wheezy depends on whether jessie will be blessed stable by then. It would be nice to have Whonix 10 ready to be upgraded from wheezy to jessie at least. Quite some systemd work TODO .
Wondering if Whonix 10 and Debian Jessie stable will hold up this important --allow-remote functionality for Tor Browser for longer than 3 months or so? Could certainly use --allow-remote as default in the near future!
If you need it just for private use, just install latest version of tb-startertb-starter/usr/bin/torbrowser at master · Kicksecure/tb-starter · GitHub - same effect.
Hope that helps. Otherwise please elaborate.
2015-01-07 23:52:20 UTC
Thanks Patrick! More an issue of the time to wait for --allow-remote becoming shipped in Whonix by default.
I have already implemented --allow-remote for myself, but am looking to have my new upcoming Qubes application utilize --allow-remote for Whonix on other people’s Whonix Qubes machines.
So just expressing timeframe desires for assuming --allow-remote as an upstream Whonix default.
2015-01-08 17:16:30 UTC