Live data from Hacker News

Tor Browser disabled NoScript, but can't update

lists.torproject.org

1–10 of 125 posts

Re: Tor Browser disabled NoScript, but can't update

#5
Somewhat related to this ongoing Mozilla plugin saga, are there any infamous stories I should look up that involve huge mistakes leading to unfixable clients? Ie. Imagine bricking your customer's devices with an irreversible buggy update. In Mozilla's case they were able to deploy a hotfix for many, and an update for others. But I imagine there's got to be some great stories about completely bricking countless devices.

Re: Tor Browser disabled NoScript, but can't update

#6
I can't improve upon this comment:

"Hey Mozilla - this is why people said that forcing addons to be signed with no way to disable was a bad idea. You didn't even make it a year without screwing it up.

Who could have seen this coming? Oh wait, pretty much everyone who argued against this policy."

Re: Tor Browser disabled NoScript, but can't update

#7
post #3

Has anyone read the article explaining Tor is a government honeypot? Its all funded by gov money

Even if it isn’t all funded by gov money the security apparatus of, at least, the big players are, without a doubt deep in to Tor.

We already know that some governments use drug money to pay for clandestine / black ops.

Re: Tor Browser disabled NoScript, but can't update

#8
I don't buy for 5 minutes that Tor Browser is secure regardless of configuration. TAILS maybe but Tor Browser you may as well let an FBI agent into your house.

A few years back the government starts busting all these dark web sites/users and will pull out of court cases rather then explain how. Gee I wonder.

Re: Tor Browser disabled NoScript, but can't update

#10
post #2

If Mozilla hadn't locked down Firefox so much, the fix could have been as simple as going into about:config and flipping a switch to allow unsigned plugins.

Apparently the switch to enable unsigned plugins does work in Tor Browser still - it just doesn't re-enable plugins that failed the signature check because the failure is cached somehow.
Post reply on HN