Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Tipton on August 23, 2004, 06:33:03 AM
-
Has anyone noticed Ad-Aware skin files that can not be scanned by Avast, because they are password protected? I am running the new SE version of Ad-Aware, and just did a full system scan with Avast. Afterwards, there was a list of Ad-Aware skin files that could not be scanned because they are password protected. Has anyone else seen this?
Thanks
Douglas
-
Heres a snip it from the list.
Douglas
-
Yeap, that's been happening to me too (only in SE).
-
Yeap, that's been happening to me too (only in SE).
Yeah, I never got this with the older version of Ad-Aware. I wonder why they are password protected?
Douglas
-
What surprises you, that they are password protected or that avast doesn't scan them? Avast also doesn't scan password protected .zip files. Otherwise we couldn't email viruses home to avast.
-
What surprises you, that they are password protected or that avast doesn't scan them? Avast also doesn't scan password protected .zip files. Otherwise we couldn't email viruses home to avast.
That a simple skin file for Ad-Aware is password protected.
Douglas
-
Tipton
Maybe it houses a state secret??? ;D
-
Tipton
Maybe it houses a state secret??? ;D
Or maybe the key to the fountain of youth.
Douglas
-
Or maybe the key to the fountain of youth.
If that's the case, I need to find out where I can buy it.......... ;D
-
Bob
Me too! Me Too! Me Too! ;D
-
Yeap, that's been happening to me too (only in SE).
For me, the same, this is the first time Ad-aware has password protected files...
Strange ::) It should be only the skins... ::)
-
I haven't any skins other than the default skin and I don't appear to have that problem. There is only one file in my skins folder the default and no additional bmp files.
Perhaps I didn't have the sensitivity of the scan set high enough to trigger this ???
Update:
Having set my Standard Scanner to High and scan archives, I ran the Standard Scan again, I too get this listing. Since my last scan was a boot scan, and my default scan was set not to scan archives, this may be why this was not picked up.
An explorer (right click ashquick.exe) doesn't pick it up either because it is not unpacking the 'ad-aware SE default.ask' file in the skins folder.
It would appear that the 'ad-aware SE default.ask' file is some form of archive file, whose contents are password protected.
The strange thing is how does it display a list of .bmp files within the 'ad-aware SE default.ask' file if it is password protected. As some have mentioned, why would ad-aware want to password protect a skin file ???
-
Ok, I asked this same question in the Lavasoft forum. The only reply I got, was from another forum member that scanned their system with their non-Avast AV. They did not get the list of un-scannable password protected files that we do when using Avast. But then again, maybe their AV of choice is not scanning as deeply as Avast is. I have Avast set to thorough scan/scan archives.
Douglas
-
Anyway, this seems to be a false positive >:( >:(
-
Anyway, this seems to be a false positive >:( >:(
False positive? I would say Avast is doing its job just fine. Like another poster says, Avast does not scan password protected files. The question, is why are skin files password protected in Ad-Aware SE.
Heres a link to the thread I have going in the Lavasoft forum.
http://www.lavasoftsupport.com/index.php?showtopic=43191
Douglas
-
Sorry, Tipton, you're fully right... :-[
I couldn't be a false positive as avast is detecting it's passworded :-[
Sorry...
-
I think what you're running into is related to SE's new ability to scan for all users with a single installation, rather than requiring a separate installation for each one.
One of the features of SE is that it now restricts the ability of non-admin users to "play" with a number of settings, such as the ignore list, so that they stay as originally set by the admin. Why the skin(s) is/are included in this security feature, I frankly haven't got a clue.
-
Anyway, this seems to be a false positive >:( >:(
I wouldn't say false positive, avast isn't reporting a virus, simply a list of files weren't scanned and the reason.
The only concern would be if that file is not password protected (this would be falsely repprting a password protected archive), as some other AV don't pick up on it; they may however either not check the archive or not report files that aren't checked during a scan.
-
I wouldn't say false positive.
I though my apologize was enough :'(
-
I wouldn't say false positive.
I though my apologize was enough :'(
Absolutly, just my slow typing (and not refreshing before my post), so I didn't see your reply as I was typing my comments ;D
-
David,
(and not refreshing before my post)
That seems to be a common occurance lately. This is about the 4th post I've run into the same problem. In one post, the problem was resolved but because there were about 4 posts one after the other , the part that solved the post was lost on a prior page.
I always go back on a post to either my last post in that subject or to the last post I remember reading and then go forward from there.
-
its because there are alot more people now and alot more come on these days.
--lee