397352 - Asstd Files

Status: RESOLVED INVALID

(Firefox :: Security, defect)

Description

[Blazer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7

Unfortunately, I cannot paste a screen print of the files but I have been uncovering .MOZ files in my C:\RECYCLER\NPROTECT folder....they are reflected in my spyware/malware scans and I am concerned as to how they got there......there are tens of thousands of them intermixed with some .sql and .txt files but most are .moz files......are these in any way related to your processes?
I am running Mozilla Firefox and am completely up to date......
Thanks for your efforts,
Blazer

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Jo Hermans]

The *.moz files just cookies, and have nothing with Firefox. Your anti-spyware product (ewido ???) just stored them in files with that extension, after they have been found in the cookies.txt file in your firefox profile. I don't know where the *.sql and *.txt files are coming from.

Firefox is not the spyware product, we're just the browser where the cookies downloaded in. And they're sent by the website. If you don't want them, turn them off in Tools->Options->privacy.

Personally, I strongly disagree that cookies are spyware (they can be used for spying, but that's not the same thing), and those anti-spyware products are screaming bloody murder for nothing, except for their self-promotion. But that's just me.

Comment 2

[Blazer]

Okay Jo,
I understand the usage of cookies for passwords etc....glad you outlined the origin of the other types, especially the ones that AVG compiles.....I've been manually deleting them from the Recycle Bin and Norton's Protected Folder, in that order and now am only running across a hundred or so, which are not those found in Firefox's privacy container, which I've found address the password etc.....
Thanks for your response and assistance......
Blazer

Comment 3

[Dave Townsend [:mossop]]

Not a Firefox bug - INVALID is the appropriate resolution