The reason why I wanted to use a proxy is because some sites ban Tor IP at all cost. FoxyProxy was an easy approach that did just that but TBB is not accepting it now.
I’m not willing to use Ice Weasel or Firefox ESR + FoxyProxy because it was clearly documented in the wiki that they’re meant to be used in downloading TBB only.
May I recommend then, to try using Proxychains or some other alternative, as explained here: Combining Tunnels with Tor It sadly isn’t as simple though. In the meantime, I may look what setting in “about:config” they changed. If I can pinpoint it, it should be possible to reactivate the ability of using external plugins. Except obviously, if they compile FF without the necessary features now, which has happend before.
Hi,
Has anyone tried reproducing this with TBB 6.0.1 ?
I tried it today and Foxyproxy installs fine on TBB 6.0.1 (tested it on multiple VMs)
Maybe they changed it from 6.0 to 6.0.1 again ?
I think the about:config setting was : xpinstall.signatures.required
Instructions did not work anymore with Tor Browser 6.0.8 (based on Mozilla Firefox 45.6.0). Foxyproxy did not enable itself because Firefox now requires signed add-ons.
OK so I guess its now safe to recommend fetching the addon from Mozilla’s servers since they are now all signed. It will be as simple as pointing it to where the custom rules file is installed.
I wonder if TBB makes any attempt to check signatures though… I know for freedom reasons signed extension support is dropped out of the Tor fork. I may have to check that out.
Sure, will do. New build in process btw. There will be a new thread in the development sub forum.
Please move that into a separate thread.
Disabling that by default would be outrageous. I doubt that. Last time when I fixed the FoxyProxy template, I needed to disable it, because extensions installed as a deb package were ignored because of this.
I testet TBB hardened with foxyproxy and neither of the options seem to work , when i installed it via the Addon-manager it said i should restart TBB to enable it but after a restart it keeps saying this.
I never got a reply for my first post but sent an update with testing results.
Meanwhile I think the best solution is to recommend @goldstein’s work around of disabling sig verification to get the old unsigned version on Jessie to work until Stretch is released. I think by Stretch foxyproxy should include the Mozilla sig and this would no longer be needed.