[HOME] [DOWNLOAD] [DOCS] [BLOG] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

Tor-launcher - Better Circumvention User Interface


#21

I don’t know how helpful it is but here is a post about running application.ini standalone with xvfb, defining a window size for the addon (so it can be seen). Xulrunner is dead but the same can be done with “firefox -app”. We can wrap TBB on GW with another script that runs it under xvfb with window size 0:

http://techno-barje.fr/post/2009/09/30/Headless-xulrunner/

I’m not sure it will work because this presupposes that torlauncher has working standalone support but it doesn’t. I would be surprised if it works its too easy :slight_smile:


#22

xvfb would have to discriminate the browser window vs the tor-launcher window. Since tor-launcher is started by Tor Browser, starting Tor Browser hidden will never show the tor-launcher window. It doesn’t look like it has such a feature.

firefox / iceweasel --app has been discussed before in this thread.

No, tor-launcher has no working standalone support. If it had, we wouldn’t need xvfb.

This could be either implemented using javascript patches or xvfb.


#23
xvfb would have to discriminate the browser window vs the tor-launcher window. Since tor-launcher is started by Tor Browser, starting Tor Browser hidden will never show the tor-launcher window. It doesn't look like it has such a feature.

True.

I’ll discuss our choices and the tradeoffs we can make with the situation now in T118.


#24

headless, unattended TBB updates [by script]
https://trac.torproject.org/projects/tor/ticket/17136


#25

[tbb-dev] future of tor-launcher? - Firefox XPCOM / XUL based add-ons deprecation
https://lists.torproject.org/pipermail/tbb-dev/2017-January/000436.html

Investigate new WebExtensions API requirements for our extensions
https://trac.torproject.org/projects/tor/ticket/17248