Member Avatar for kaninelupus

Now if you've heard of FilterFox, you'll know it is an add-on for Firefox that allows the main user to block those sites they don't want any shared users to access. Now up till V6.0, one could password protect access to FilterFox, disallowing others from simply disabling filters, or even uninstalling the add-on. Unfortunately the devs have gotten greedy with v7.0, deciding to charge the end-user to lock the filter down (not bad when you consider it is an add-on for a FREE and OPEN-SOURCE browser!!).

So, I managed to locate a version of FilterFox 6.0, installed with Nightly Tester Tools (had to DL and install locally by dragging file onto Add-ons manager), and what do you know.... it works perfectly!

Have since cracked open the xpi file with WinRAR and modified the "install.rdf" so as will happily install without the Nightly Tester Tools, and uploaded for others to make good use of. When given open to open or save, select open and choose Firefox as app to handle the file - will install directly :)

Now before I get told off, the plugin otherwise remains unaltered, just simply making things easier for those not familiar with Nightly Tester Tools and its usage :S

  • 1 Contributor
  • 1 Reply
  • 311 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by kaninelupus

Dani AI

Generated

Quick expert summary and safety-first suggestions (building on 's find).

Older Firefox builds and legacy add-ons can appear to solve compatibility problems, but running them is risky: versions like Firefox 3.5 are long unsupported and no longer receive security fixes. (mozilla.org)

Browsers and the add-on ecosystem changed since 2009. Firefox moved to the WebExtensions model (so many legacy XPI-style add-ons stopped loading in modern releases), and Mozilla now requires most add-ons to be digitally signed for release/beta builds — modified or unsigned packages will be blocked or disabled. Advanced testers can use Developer/Nightly or unbranded builds to relax those checks, but that reduces security and is only appropriate for isolated testing. (blog.mozilla.org)

Safer, longer-term approaches to restrict sites for shared users:

  • Network-level filtering (DNS/router) — e.g., a Family or content-filtering DNS provider can block domains for every device on the network. This is durable and harder for casual users to bypass. ()
  • OS/Account controls — use separate standard (non-admin) user accounts and built‑in parental controls (Microsoft Family Safety on Windows) to block sites or require permission for changes. This prevents everyday users from uninstalling protections. (support.microsoft.com)

If an older extension must be evaluated: do it in a disposable VM or isolated test profile, keep the test machine offline when installing, and inspect the package before use (open the XPI as a zip and scan for unexpected update URLs, obfuscated code, or remote install behavior). Prefer signed WebExtensions from Mozilla Add‑ons (AMO) or modern equivalents when possible. These steps reduce the risk that a helpful tweak becomes a lasting security problem.

Member Avatar for kaninelupus

Just a link change. Can be DL'ed from

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.