[clamav-users] Still getting this:

[Dennis Peterson]

Write a local whitelist record?

dp

On 11/18/15 11:32 PM, Al Varnell wrote:
> I just submitted my FP to them 48 hours ago and have not received confirmation on it’s acceptance yet.  Not terribly unusual, but given that it impacts Adobe apps, I did expect to have some feedback by now.
>
> -Al-
>
> On Wed, Nov 18, 2015 at 10:07 PM, Gene Heskett wrote:
>> /home/gene/.cache/chromium/Default/Cache/f_000445:
>> Swf.Exploit.CVE_2015_5548 FOUND
>> /home/gene/.cache/chromium/Default/Cache/f_000031:
>> Swf.Exploit.CVE_2015_5548 FOUND
>> /home/gene/.cache/chromium/Default/Cache/f_000200:
>> Swf.Exploit.CVE_2015_5548 FOUND
>> /home/gene/.cache/chromium/Default/Cache/f_0001fb:
>> Swf.Exploit.CVE_2015_5548 FOUND
>> /home/gene/.cache/chromium/Default/Cache/f_000202:
>> Swf.Exploit.CVE_2015_5548 FOUND
>>
>> A sudo freshclam says everything is up to date.
>> gene at coyote:~$ sudo freshclam
>> [sudo] password for gene:
>> ClamAV update process started at Thu Nov 19 01:01:56 2015
>> main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder:
>> neo)
>> daily.cld is up to date (version: 21069, sigs: 1691987, f-level: 63,
>> builder: neo)
>> bytecode.cld is up to date (version: 270, sigs: 46, f-level: 63, builder:
>> shurley)
>>
>> Should this not be fixed by now, or is it real?  Since its in the browser
>> cache, I am just nuking them.
>>
>> Debian  wheezy here, up to date as of about 2 hours ago.
>>
>> Cheers, Gene Heskett
>>
>>
>> _______________________________________________
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>>
>> http://www.clamav.net/contact.html#ml