Re: ukash hijacked iceweasel
On Sun, 13 Oct 2013 23:54:41 +0200
Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
> >
> > Disable javascript, reload offending tab (optional), close offending
> > tab, enable javascript.
> > I mean, why bother with complex solutions if there are simple ones?
>
> I never tried it that way, because I couldn't find where to disable it
> and I had no time to do research when this issue happened. Just for fun
> I tried to find where it can be disabled for Firefox 24.0 right now, but
> I couldn't find it ;).
>
> https://support.mozilla.org/en-US/kb/javascript-settings-for-interactive-web-pages
This is outdated page indeed. Apparently Mozilla Foundation decided
that it will be more user-friendly to double-click on
'javascript.enabled' at about:config page :)
OT: Curiously, they decided that certain checkbox is 'killing their
product':
https://bugzilla.mozilla.org/show_bug.cgi?id=851698
Clearly they've never got into accound an evil JavaScript that renders
browser unusable with no simple way to disable it.
> I've got Ghostery installed, I'm using Ghostery to detect trackers, but
> I can't find how to use it to disable scripts.
>
> IOW disabling javascript is much more work, assumed you won't install
> many add-ons. I'm only using 2 add-ons, Ghostery and Anonymox.
Probably because none of this extensions are designed to disable
Javascript the way it should be done (i.e. whitelist for enabling JS
on specific domains). As a NoScript user I don't find enabling and
disabling Javascript that hard.
> My Firefox ERS 17.0.9 (Vidalia/TOR) provides to disable javascript by
> Edit > Preferences > Content, but I usually don't use the TOR browser or
> outdated versions of Firefox.
Good for you, I guess, but John (thread starter) uses stock Debian
Iceweasel (judging from his MUA version), so Mozilla's KnowledgeBase
solution should work for him.
Reco
Reply to: