InformAction Forums

I am not sure if this is a bug or glitch. But even since I installed NoScript I always added a couple sites to the whitelist, due to the frequent need to go to said sites.

So I am using Firefox 24 with NoScript 2.6.8.3, and the site in question was creighton.edu. I installed NoScript 3 months ago due to a computer upgrade. I have NoScript configured to display the Status Bar if there are blocked scripts. Yesterday I updated to 2.6.8.3, and when I went to a site with the domain creighton.edu, there was no Status Bar because the site was allowed.

Today I went on the same site, but the Status Bar appeared and when I checked my Whitelist, creighton.edu was missing. I re-added the site and closed my browser using File -> Exit due to a bug with Firefox 24 not closing the session correctly if we use the Close Window button. The site was still there.

I had the site added to the Whitelist for 3 months and only after upgrading yesterday did such a weird thing happen. The other site I added along with creighton.edu was still there today and wasn't removed. The site was fafsa.

The other thing I should note is that yesterday after I was done with creighton.edu, I cleared my browsing history and closed Firefox with the Close Window button. When I started Firefox today it prompted me to restore my last session. Normally, I would have used File -> Exit, but I forgot.

Should I be worried that a site I added 3 months ago magically disappeared from my Whitelist? Could it be someone tampered with the prefs.js file?

Guest wrote:Should I be worried that a site I added 3 months ago magically disappeared from my Whitelist?

Not sure. I don't think I've heard of this happening previously. If it happens again, let us know (otherwise it's pretty hard to investigate).

Could it be someone tampered with the prefs.js file?

Well, only you can answer that, really (I don't know who might have access to your machine). The technical answer is yes, someone could remove something from your whitelist by tampering with your Firefox preferences, but I can't see why someone would achieve that level of access to your system and then decide to simply remove something from your NoScript whitelist. Except maybe the black-hat guy.

I will keep an eye on it to see if any sites disappear. My whitelist only has about 15 sites, so I remember them all.

As for the access to my machine, it should only be me since I was the only one using it amd after I was done with creighton.edu on Firefox. I shutdown my computer

As for the hacking thing, thats was just curiousity but I doubt it as I only check my university email and write word documents on that machine. So possiblity of visiting dangerous sites are zero.

Some information I believe may help with this problem.

After I was done with creighton.edu, I cleared my browsing history and closed Firefox with the Close Window button. I have Firefox set to remember my history so I clear it when I close Firefox. When I started Firefox today it prompted me to restore my last session because it didn't end properly (Bug in Firefox, where I need to use File -> Exit to properly close Firefox) . Normally, I would have used File -> Exit, but I forgot to.

I don't know if this problem will ever occur again or not, since I tried visiting creighton.edu and exiting the browser with the Close button to recreate the problem. But I was unsuccessful and that seemed to be the likely cause. Also the other site I visited after updating was gmail (google.com, googleapis.com) are still on the whitelist. Only creighton.edu (last site visited before closing Firefox "incorrectly") was missing.

Come to think of it, I've seen this problem before, but unfortunately I am not the primary user of that computer - and the primary user being such a non-techie, I had dismissed it as clicking "Forbid homefinder.org" without knowing what it meant (homefinder dot org was the website in question), but it's happened a few times on that machine with various websites, and now seeing this, I'm not so sure... I'll keep an eye out, but I do know that the issue has been around before NoScript 2.6.8.3 and that Firefox (probably 18.0.2) shut down properly there.