, Inc.
From: clamav-users on behalf of Ralf
Hildebrandt via clamav-users
Sent: Tuesday, May 16, 2023 1:08 AM
To: clamav-users@lists.clamav.net
Cc: Ralf Hildebrandt
Subject: [clamav-users] LibClamAV Warning: Don't know how to create filter for:
Win.Downloader.LNKAgent-10001628-0
cl
clamav-1.1.0-1:
===
May 16 10:00:23 de freshclam[864]: Tue May 16 10:00:23 2023 -> daily database
available for update (local version: 26907, remote version: 26908)
May 16 10:00:23 de freshclam[864]: WARNING: Tue May 16 10:00:23 2023 ->
*** RESULT 200, SIZE: 7213 ***
Why do
Andrew C Aitchison via clamav-users wrote:
On Mon, 12 Dec 2022, newcomer01 wrote:
Well on my PC I changed a lot because the naming was too messy for me.
I have "program" clam*d*scan for which I have a clam*d*.conf and a
"program" clamscan for which I have a clamscan.conf. And then the
normal
:34 (at 05:34 PM) +0100
Betreff / Subject: Re: [clamav-users] LibClamAV Warning: PNG: Unexpected early
end-of-file.
On Mon, 12 Dec 2022, newcomer01 wrote:
Well on my PC I changed a lot because the naming was too messy for me.
I have "program" clam*d*scan for which I have a clam*d*.conf a
ything!
Von / From: Andrew C Aitchison <mailto:and...@aitchison.me.uk>
An / To: Newcomer01 <mailto:newcome...@posteo.de>
Gesendet / Sent: Montag, Dezember 12, 2022 um 16:33 (at 04:33 PM) +0100
Betreff / Subject: Re: [clamav-users] LibClamAV Warning: PNG: Unexpected
early end-of-file.
On
On Mon, 12 Dec 2022, newcomer01 via clamav-users wrote:
can nobody explain, what this message exactly mean?
I Get the on lot of my E-mails
LibClamAV Warning: PNG: Unexpected early end-of-file.
That just means that the PNG file is either not a PNG for or is corrupted
- perhaps truncated.
Sh
can nobody explain, what this message exactly mean? I Get the on lot of my
E-mails
LibClamAV Warning: PNG: Unexpected early end-of-file. Should i change something
in my config for clamscan?
And mybe devs of clamav reas here to, it would be really nice, if you can add the optional
paramteter "-
, Inc.
From: clamav-users on behalf of Stephen
Scotter via clamav-users
Sent: Thursday, March 17, 2022 4:25 AM
To: ClamAV Users ML
Cc: Stephen Scotter
Subject: [clamav-users] LibClamAV Warning: fmap_readpage: pread fail
Hi,
I noticed Clamd has unexpectantly died on t
Hi there,
On Thu, 17 Mar 2022, Stephen Scotter via clamav-users wrote:
I noticed Clamd has unexpectantly died on two [VMs] ...
System1
Virtual Machine
CPU : 1 socket / 2 cores
RAM : 2GB Ram ...
OS : Debian 10 / buster
Clam : ClamAV 0.103.5/26484/Thu Mar 17 08:28:38 2022
Mar 13 13:14:27 Syste
I can't comment on this particular error but 2G of RAM is definitely
insufficient and I believe 4G would be as well when freshclam is
applying updates to the database as there would be 2 copies of it in RAM.
Dave.
On 2022-03-17 07:25, Stephen Scotter via clamav-users wrote:
> Hi,
>
> I noticed Cl
Hi,
I noticed Clamd has unexpectantly died on two of my virtual machines.
Investigating lead me to find similar errors in the logs on both hosts around
the times I know clamd died (I'm monitoring for the existence of a clamd
process with zabbix but only got around to investigating today due to
While verbose (-v) is helpful in some cases, you probably want to use the debug
option to get the large volume of LibClamAV messages. I find debug is far more
useful than verbose most times.
Maarten
Sent from a tiny keyboard
> On Apr 5, 2021, at 04:17, Vivek Patil via clamav-users
> wrote:
>
Oh yes, I have tried that too.
But only the warning line was printing.
The command was:
clamscan -v -i -r --cross-fs=no -f "$list_file"
On Mon, Apr 5, 2021 at 12:49 PM Eero Volotinen
wrote:
> Just add more verbose to your scanning parameters. I think it was -v, if I
> remember correctly.
>
> Ee
Just add more verbose to your scanning parameters. I think it was -v, if I
remember correctly.
Eero
On Mon, Apr 5, 2021 at 9:20 AM Vivek Patil
wrote:
> Eero,
>
> What more details do you want?
> I am scanning my system using "clamscan -i -r --cross-fs=no -f
> "$list_file"" using a shell script.
On 05/04/2021 16:20, Vivek Patil via clamav-users wrote:
Eero,
What more details do you want?
I am scanning my system using "clamscan -i -r --cross-fs=no -f
"$list_file"" using a shell script.
It giving only the warning message as follows:
LibClamAV Warning: PNG: Unexpected early end-of-file.
Hello Vivek,
I am scanning my system using "clamscan -i -r --cross-fs=no -f
"$list_file"" using a shell script.
Please remove "-i" :
"clamscan -r --cross-fs=no -f "$list_file""
... and you will get all files scanned, including the one that trigger
the warning
--
Cordialement / Best regard
Eero,
What more details do you want?
I am scanning my system using "clamscan -i -r --cross-fs=no -f
"$list_file"" using a shell script.
It giving only the warning message as follows:
LibClamAV Warning: PNG: Unexpected early end-of-file.
I just wanted to find the location/name of the file.
On Mo
Just add more verbose?
Eero
On Mon 5. Apr 2021 at 8.58, Vivek Patil via clamav-users <
clamav-users@lists.clamav.net> wrote:
> Hi Team,
>
> I am getting a warning message while scanning the system.
> I used *clamscan *command to scan.
>
> Details:
> Warning message: LibClamAV Warning: PNG: Unexp
Hi Team,
I am getting a warning message while scanning the system.
I used *clamscan *command to scan.
Details:
Warning message: LibClamAV Warning: PNG: Unexpected early end-of-file
ClamAV version: ClamAV 0.103.1
How can we find more details, which file has the issue?
--
Email Disclaimer: *http
Unsatisfying as it may seem, the problem went away as it came, without
any obvious reason.
For the record, we do have SELinux active on those systems, so it is
(was) very likely an SELinux issue.
Thanks,
Tilman
Am 16.07.2018 um 17:07 schrieb Micah Snyder (micasnyd):
> Hi Tilman,
>
> Sorry no on
Hi Tilman,
Sorry no one has responded to you yet. I hate seeing questions go unanswered,
but I truthfully don't know the answer.
Did you find a solution?
Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
On Jul 10, 2018, at 4:46 AM, Tilman Schmidt
mailto:tschm...@cardtech.de>> wrot
This morning, a bunch of RHEL6 systems greeted me with mails saying:
/etc/cron.daily/freshclam:
ERROR: During database load : LibClamAV Warning: RWX mapping denied:
Can't allocate RWX Memory: Permission denied
I found an old Red Hat Bugzilla entry (Bug 1172774) for Fedora 21 which
was closed as
Just to let you know:
The daily messages have become too annoying so I cleared my Java cache
to get rid of the offending file.
Consequently I won't be available for testing a fix anymore, at least
until the problem reappears on some other file.
Am 25.06.2018 um 11:12 schrieb Tilman Schmidt:
> The
The problem still exists. All the messages turn out to be triggered by
one single JAR file in the Java deployment cache:
~/.java/deployment/cache/6.0/6/41d72bc6-2cd5ef82: OK
~/.java/deployment/cache/6.0/6$ ls -l 41d72bc6-2cd5ef82
-rw-rw-r-- 1 tschmidt tschmidt 6300341 Jun 8 2017 41d72bc6-2cd5ef
The last nightly ClamAV scan on one of my machines emitted a series of
error messages I'm not familiar with:
LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
LibClamAV Warning: [Bytecode JIT]: recovered from error
LibClamAV Warning: [Bytecode JIT]: JITed code intercepted
It appears as though the antivirus signatures written in bytecode ran longer
than the default timeout. If you wanted to try again with a longer timeout,
that's an option.
To test with a longer bytecode timeout in clamscan, use the --bytecode-timeout
flag and pass in the desired timeout in mill
Hi altogether,
I wonder if you could help me with a particular warning-message I get
when scanning a certain pdf-file.
I downloaded a German-Russian study book as a pdf-file.
When scanning it I got the following output:
clamscan Russisch_bitte_von_BookFi.pdf
LibClamAV Warning: [Bytecode JIT]: By
Tilman,
Please attach here:
https://bugzilla.clamav.net/show_bug.cgi?id=12002
Thanks,
Steve
On Fri, Dec 22, 2017 at 9:35 AM, Steven Morgan
wrote:
> Tilman,
>
> Thanks for the notification, we will check out the code. I'll open a bug
> report where you can post your sample.
>
> Steve
>
>
Tilman,
Thanks for the notification, we will check out the code. I'll open a bug
report where you can post your sample.
Steve
On Fri, Dec 22, 2017 at 9:03 AM, Tilman Schmidt
wrote:
> ClamAV running on Ubuntu Xenial, package version
> 0.99.2+dfsg-0ubuntu0.16.04.2, emits the following warning me
ClamAV running on Ubuntu Xenial, package version
0.99.2+dfsg-0ubuntu0.16.04.2, emits the following warning message when
scanning one of my Thunderbird IMAP mail folders:
LibClamAV Warning: Unsupported message format `http' - if you believe
this file contains a virus, submit it to www.clamav.net
I
Hi,
Thanks for the report. Tracking the issue here:
https://bugzilla.clamav.net/show_bug.cgi?id=11930
Steve
On Tue, Oct 17, 2017 at 2:46 AM, Hajo Locke wrote:
> Hello,
>
> today i see a warning when starting a manuell clamscan:
>
> # clamscan -ir
> LibClamAV Warning: Don't know how to creat
Confirmed.
I see the same warnings just running freshclam when attempting to download and
process daily-23959.cdiff which contains that signature. It looks to be a
relatively complex logical signature that I suspect is malformed.
-Al-
On Mon, Oct 16, 2017 at 11:46 PM, Hajo Locke wrote:
> today
Hello,
today i see a warning when starting a manuell clamscan:
# clamscan -ir
LibClamAV Warning: Don't know how to create filter for:
Win.Trojan.Dovs-6343034-0
LibClamAV Warning: cli_ac_addpatt: cannot use filter for trie
Version is 0.99.2 included in Ubuntu 16.04
Thanks,
Hajo
The bytecode signature behind this runtime error has been removed.
On Sat, May 6, 2017 at 2:13 PM, Rudy Stebih wrote:
> As I didn't hear back from anyone, I placed an exclude statement for the
> file just so that I could finish the scan. These warnings are halting the
> scan!
>
> Turns out I got
As I didn't hear back from anyone, I placed an exclude statement for the
file just so that I could finish the scan. These warnings are halting the
scan!
Turns out I got a second LibClamAV warning after I excluded the first one:
Scanning C:\Program Files (x86)\InstallShield Installation
Informatio
I thought this was fixed.
--
Sent from my iPhone
> On May 6, 2017, at 14:01, Rudy Stebih wrote:
>
> I filed a bug report for this. Bug #11837
>
> Cheers,
> Rudy
>
>
>> On Wed, May 3, 2017 at 1:25 PM, David Raynor wrote:
>>
>> Bump for visibility. I figure someone from your team should g
I filed a bug report for this. Bug #11837
Cheers,
Rudy
On Wed, May 3, 2017 at 1:25 PM, David Raynor wrote:
> Bump for visibility. I figure someone from your team should get in touch
> with him, since it is not exactly an FP report. Maybe he can still submit
> it as FP. Don't know.
>
> Dave R.
Bump for visibility. I figure someone from your team should get in touch
with him, since it is not exactly an FP report. Maybe he can still submit
it as FP. Don't know.
Dave R.
On Tue, May 2, 2017 at 10:05 PM, Rudy Stebih wrote:
> Hi Folks,
>
> I've been getting the following error for a week o
Hi Folks,
I've been getting the following error for a week or so:
'LibClamAV Warning: Bytecode runtime error at line 1226, col 4'
I finally found the time to run ClamAV in verbose mode and believe this is
the culprit:
'Scanning C:\Program Files (x86)\Applian Director\ClearRegCode.exe'
At least
This is caused by a subset of the detection pattern used in the bytecode
signature BC.Win.Exploit.CVE_2017_0060-6099223-0. This is a warning and
doesn't impact detection of the bytecode in ClamAV. An updated version of
this signature was pushed out this morning in the latest bytecode CVD. You
may n
Hi,
I'm very new to Linux and have little technical knowledge.
I installed ClamAV and ran a scan (sudo clamscan). I received the following
warnings:
LibClamAV Warning: Don't know how to create filter for:
BC.Win.Exploit.CVE_2017_0060-6099223-0.{}
LibClamAV Warning: cli_ac_addpatt: cannot use
Thank you for the detailed answer; I am using the HEAD version from an
OSX Homebrew install; I recently changed from stable, and had not had
this warning before.
Cheers,
Rick
On 5/20/16 02:58, Kevin Lin wrote:
> This warning occurs in the new experimental pdf filter rework that is not
> part of a
This warning occurs in the new experimental pdf filter rework that is not
part of any existing ClamAV releases (as of 0.99.2). Thus as a disclaimer,
it must be stated that the version of ClamAV being used may be unstable or
incomplete especially with the experimental section that this warnings is
r
Hi,
Where can I find info on this warning when running clamscan?:
LibClamAV Warning: cli_pdf: unimplemented filter type [10] => DCTDECODE
I've been searching, but I can't find much on LibClamAV and filters,
much less cli_pdf or DCTDECODE.
Best regards,
Rick
--
Rick Valenzuela
Videojournalist
Hi,
Looking in the code, the file was truncated, as the warning message states.
The message is issued by the TNEF file parser. Returning CLEAN from the
parser tells the caller(the TNEF scanner) to scan all of the previously
extracted parts of the TNEF message for viruses.
Hope this helps,
Steve
_
Hello,
I would like to know what this clamd warn means:
"LibClamAV Warning: cli_tnef: file truncated, returning CLEAN"
I run
ClamAV 0.99.1/21486/Tue Apr 5 22:19:10 2016
on amavisd and clamav-milter.
In deep, I would like to know if this warning could be a issue
allowing some malwares to
On Dec 11, 2015, at 1:58 PM, Andreas van Ohlen
mailto:a.vanoh...@posteo.de>> wrote:
LibClamAV Warning: SWF: declared output length != inflated stream size, 486465
!= 795244
I am guessing that the Flash file being analyzed declared the length to be
795244 for a compressed section, however, wh
Hi Guys,
since the update to 0.99 on my Manjaro Linux System I get the warning
LibClamAV Warning: SWF: declared output length != inflated stream size,
486465 != 795244
when scanning with "clamscan -ri". What does this mean and how can I fix
it? Thanks!
__
Chamal,
Have a look at the --max-filesize parameter on the clamscan man page and
try using with a value that accommodates your file size.
Steve
On Fri, Sep 26, 2014 at 1:09 AM, chamal desilva wrote:
> Hi,
>
> OS: Ubuntu 14.04 64 bit
> ClamAv Version: ClamAV 0.98.1/19437/Fri Sep 26 04:06:13 201
Hi,
OS: Ubuntu 14.04 64 bit
ClamAv Version: ClamAV 0.98.1/19437/Fri Sep 26 04:06:13 2014
1. Download http://llvm.org/releases/3.5.0/cfe-3.5.0.src.tar.xz
2. Scan - clamscan cfe-3.5.0.src.tar.xz
3. Receive this warning and output.
LibClamAV Warning: cli_scanxz: decompress file size exceeds limi
This warning is related to file map handling. This message will appear when
ClamAV tried to unlock the wrong locked page of the file map. It is a
temporary issue, since the page will be unlocked when the file is closed
and map is unmapped anyway. There is one known issue that can lead to this
warni
hi!
scanning a samba share gives me this warning:
LibClamAV Warning: fmap_unneed: unneed on a unlocked page LibClamAV Warning:
fmap_unneed: unneed on a unlocked page
does anyone know what does it mean?
thanks in advance,
René
___
Help us build
On 11/20/2011 12:45 AM, Ben Stuyts wrote:
>
> On 19 nov. 2011, at 17:19, Ben Stuyts wrote:
>
>>
>> On 18 nov. 2011, at 21:20, René Bellora wrote:
>>
>>> hi!
>>>
>>> i'm getting some warnings when scanning a directory:
>>>
>>> LibClamAV Warning: Bytcode 4 failed to run: Error during bytecode execu
On 19 nov. 2011, at 17:19, Ben Stuyts wrote:
>
> On 18 nov. 2011, at 21:20, René Bellora wrote:
>
>> hi!
>>
>> i'm getting some warnings when scanning a directory:
>>
>> LibClamAV Warning: Bytcode 4 failed to run: Error during bytecode execution
>>
>> LibClamAV Warning: Bytecode run timed ou
On 18 nov. 2011, at 21:20, René Bellora wrote:
> hi!
>
> i'm getting some warnings when scanning a directory:
>
> LibClamAV Warning: Bytcode 4 failed to run: Error during bytecode execution
>
> LibClamAV Warning: Bytecode run timed out in interpreter after 221135000
> opcodes
>
> LibClamAV W
hi!
i'm getting some warnings when scanning a directory:
LibClamAV Warning: Bytcode 4 failed to run: Error during bytecode execution
LibClamAV Warning: Bytecode run timed out in interpreter after 221135000 opcodes
LibClamAV Warning: Bytcode 4 failed to run: Unknown error code
what are these?
On Fri, 03 Dec 2010 09:50:22 +
James Brown wrote:
> Török Edwin wrote:
> > On Sat, 27 Nov 2010 05:24:19 +
> > James Brown wrote:
> >
> >> When scanning, clamscan give me the above messages of errors.
> >> What could it mean?
> >
> > It probably means that the file changed its size whil
Török Edwin wrote:
> On Sat, 27 Nov 2010 05:24:19 +
> James Brown wrote:
>
>> When scanning, clamscan give me the above messages of errors.
>> What could it mean?
>
> It probably means that the file changed its size while you were
> scanning it, i.e. clamscan thought the file still had 4077
On Sat, 27 Nov 2010 05:24:19 +
James Brown wrote:
> When scanning, clamscan give me the above messages of errors.
> What could it mean?
It probably means that the file changed its size while you were
scanning it, i.e. clamscan thought the file still had 4077 more bytes,
but when trying to re
When scanning, clamscan give me the above messages of errors.
What could it mean?
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
Thank you much Tomasz.
Veselin
On Tue, Jul 08, 2008 at 07:09:31PM +0200, Tomasz Kojm wrote:
> On Tue, 8 Jul 2008 18:01:57 +0100
> Veselin Kantsev <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> > I get this in my daily scan reports:
> > "LibClamAV Warning: Bad compression in flate stream"
> >
> > Cou
On Tue, 8 Jul 2008 18:01:57 +0100
Veselin Kantsev <[EMAIL PROTECTED]> wrote:
> Hello,
> I get this in my daily scan reports:
> "LibClamAV Warning: Bad compression in flate stream"
>
> Could you please advise what is causing this?
>
>
> ClamAV 0.92.1
That's from the pdf handler, upgrade to 0.9
Hello,
I get this in my daily scan reports:
"LibClamAV Warning: Bad compression in flate stream"
Could you please advise what is causing this?
ClamAV 0.92.1
Debian Lenny 2.6.21-2-686
--
Regards,
Veselin Kantsev
[EMAIL PROTECTED]
Campbell-Lange Workshop
__
Török Edwin wrote:
> daz wrote:
>> Török Edwin wrote:
>>
>>> daz wrote:
>>>
Hello, Everyone.
We've recently updated our CentOS-5 machine to clamav-0.93.1
from clamav-0.93. We're using the rpms from the dag repo here:
http://apt.sw.be/redhat/el5/en/x86_64/RPMS.dag/
daz wrote:
> Török Edwin wrote:
>
>> daz wrote:
>>
>>> Hello, Everyone.
>>>
>>> We've recently updated our CentOS-5 machine to clamav-0.93.1
>>> from clamav-0.93. We're using the rpms from the dag repo here:
>>> http://apt.sw.be/redhat/el5/en/x86_64/RPMS.dag/
>>>
>>> We have a nightly cron
Török Edwin wrote:
> daz wrote:
>> Hello, Everyone.
>>
>> We've recently updated our CentOS-5 machine to clamav-0.93.1
>> from clamav-0.93. We're using the rpms from the dag repo here:
>> http://apt.sw.be/redhat/el5/en/x86_64/RPMS.dag/
>>
>> We have a nightly cron job on the machine that does this
daz wrote:
> Hello, Everyone.
>
> We've recently updated our CentOS-5 machine to clamav-0.93.1
> from clamav-0.93. We're using the rpms from the dag repo here:
> http://apt.sw.be/redhat/el5/en/x86_64/RPMS.dag/
>
> We have a nightly cron job on the machine that does this:
> clamscan -i -r /some/wh
Hello, Everyone.
We've recently updated our CentOS-5 machine to clamav-0.93.1
from clamav-0.93. We're using the rpms from the dag repo here:
http://apt.sw.be/redhat/el5/en/x86_64/RPMS.dag/
We have a nightly cron job on the machine that does this:
clamscan -i -r /some/where/
Since upgrading, we
>From: [EMAIL PROTECTED]
> I am no expert but if I had to guess I would say it means you scanned
> a file that was utf16 and also less then 2 bytes. I don't think this
> is a bug but just a special case when the length of a utf16 file to
> be converted to ascii is less than 2 bytes. This looks t
[EMAIL PROTECTED] wrote:
> Mishustin Alexey wrote:
>
>> Hello,
>>
>> what's about my question? (I wrote 23 March)
>>
>> After the full system scan I've got console reports as follows:
>>
>> LibClamAV Warning: cli_utf16toascii: length < 2
>>
>> What does it mean? Is this a bug? How to fix the pro
Mishustin Alexey wrote:
> Hello,
>
> what's about my question? (I wrote 23 March)
>
> After the full system scan I've got console reports as follows:
>
> LibClamAV Warning: cli_utf16toascii: length < 2
>
> What does it mean? Is this a bug? How to fix the problem?
I am no expert but if I had to
Hello,
what's about my question? (I wrote 23 March)
After the full system scan I've got console reports as follows:
LibClamAV Warning: cli_utf16toascii: length < 2
What does it mean? Is this a bug? How to fix the problem?
Clamav version: 0.92.1
LibClamAV version: 0.92.1~dfsg-1volatile1
OS: De
Hello,
after the full system scanning (with -i option) I've got many console
reports as follows:
LibClamAV Warning: cli_utf16toascii: length < 2
Please tell me what does it mean and what should I do to fix the
problem.
Clamav version: 0.92.1
LibClamAV version: 0.92.1~dfsg-1volatile1 (downloaded
Hello,
Before Debian users (and others ?) flood the mailing list with this message,
one possible solution is here :
http://www.securiteinfo.com/divers/Clamav_LibClamAV_Warning_RAR_code_not_compiled-in.shtml
--
Cordialement / Best regards,
Arnaud Jacques
Consultant Sécurité
SecuriteInfo.com
ht
> At 01:15 PM 7/12/2007, Jose Julian Buda wrote:
>> > At 10:35 AM 7/12/2007, Jose Julian Buda wrote:
>> >>Hi , i am new with this soft , i have installed
>> >>postfix+mailscanner+clamav on debian "sarge" server.
>> >>
>> >>I've installed ClamAV 0.91 from source, run freshclam and the virus
>> >>da
At 01:15 PM 7/12/2007, Jose Julian Buda wrote:
> > At 10:35 AM 7/12/2007, Jose Julian Buda wrote:
> >>Hi , i am new with this soft , i have installed
> >>postfix+mailscanner+clamav on debian "sarge" server.
> >>
> >>I've installed ClamAV 0.91 from source, run freshclam and the virus
> >>database i
> At 10:35 AM 7/12/2007, Jose Julian Buda wrote:
>>Hi , i am new with this soft , i have installed
>>postfix+mailscanner+clamav on debian "sarge" server.
>>
>>I've installed ClamAV 0.91 from source, run freshclam and the virus
>>database is updated.
>>
>>As you can see:
>>
>>serverna:~# clamscan
At 10:35 AM 7/12/2007, Jose Julian Buda wrote:
>Hi , i am new with this soft , i have installed
>postfix+mailscanner+clamav on debian "sarge" server.
>
>I've installed ClamAV 0.91 from source, run freshclam and the virus
>database is updated.
>
>As you can see:
>
>serverna:~# clamscan -V
>ClamAV
Hi , i am new with this soft , i have installed postfix+mailscanner+clamav on
debian "sarge" server.
I've installed ClamAV 0.91 from source, run freshclam and the virus database is
updated.
As you can see:
serverna:~# clamscan -V
ClamAV 0.91/955/Thu Jun 23 18:08:42 2005
serverna:~# freshclam
Hi , i am new with this soft , i have installed postfix+mailscanner+clamav on
debian "sarge" server.
I've installed ClamAV 0.91 from source, run freshclam and the virus database is
updated.
As you can see:
serverna:~# clamscan -V
ClamAV 0.91/955/Thu Jun 23 18:08:42 2005
serverna:~# freshclam
Hello together,
I am using ClamAv 0.9 on Debian Sarge.
:~# clamscan -r -i /home
LibClamAV Warning: pdf: after writing 0 bytes, got error
"invalid distance too far back" inflating PDF attachment
LibClamAV Warning: pdf: after writing 0 bytes, got error
"invalid distance too far back" inflating PDF
Hello clamav-users,
On my contribs.org SME version 7.0 I get the following log entries
every day.
I didn't find an answer in
http://www.clamav.net/doc/0.88.4/clamdoc.pdf, so can someone here
advise how I can configure the report to exclude these types of
warnings. Because without clam telling me
Noah wrote:
On Fri, 19 May 2006 11:54:43 -0400, Guillaume Vachon wrote
Noah wrote:
clamav-0.88.2_1
freeBSD-4.11
so I just upgraded to clamav-0.88.2_1
and find myself with the following error when starting clamd.
The last couple hundred times this came up the problem was the user
didn't c
On Fri, 19 May 2006 11:19:01 -0500 (CDT), C. Bensend wrote
> > Okay I did that and still the same warning message.
> >
> >
> > snip
> >
> > # cd /usr/local/share/clamav
> > # ls -l
> > total 4544
> > -rw-r--r-- 1 clamav clamav 641509 May 19 08:48 daily.cvd
> > -rw-r--r-- 1 clamav cl
> Okay I did that and still the same warning message.
>
>
> snip
>
> # cd /usr/local/share/clamav
> # ls -l
> total 4544
> -rw-r--r-- 1 clamav clamav 641509 May 19 08:48 daily.cvd
> -rw-r--r-- 1 clamav clamav 3950054 Apr 22 01:11 main.cvd
> # date
> Fri May 19 08:55:13 PDT 2006
>
Noah spake thusly on Fri, May 19, 2006 at 07:57:15AM -0800:
>
> Okay I did that and still the same warning message.
>
--- end quoted text ---
Delete the old databases and run freshclam again.
Regards,
Richard
--
Did this email or post help you? If so, please rate
me at affero: http://rate.aff
On Fri, 19 May 2006 11:54:43 -0400, Guillaume Vachon wrote
> Noah wrote:
> > clamav-0.88.2_1
> > freeBSD-4.11
> >
> >
> > so I just upgraded to clamav-0.88.2_1
> > and find myself with the following error when starting clamd.
> >
> >
> > ---s nip ---
> >
> > Starting clamav_clamd.
> > LibClamAV Wa
Noah wrote:
> clamav-0.88.2_1
> freeBSD-4.11
>
>
> so I just upgraded to clamav-0.88.2_1
> and find myself with the following error when starting clamd.
>
>
> ---s nip ---
>
> Starting clamav_clamd.
> LibClamAV Warning: **
> LibClamAV Warning: *** T
clamav-0.88.2_1
freeBSD-4.11
so I just upgraded to clamav-0.88.2_1
and find myself with the following error when starting clamd.
---s nip ---
Starting clamav_clamd.
LibClamAV Warning: **
LibClamAV Warning: *** The virus database is older than 7
When doing a clamscan I see this in the log:
LibClamAV Warning: Unknown VBA version signature 6c 0 0 1
LibClamAV Warning: Guessing little-endian
Should I be worried?
clamscan --version
ClamAV 0.87.1/1213/Mon Dec 19 14:48:34 2005
___
http://lurker.clama
Nigel Horne wrote:
I receive the following output from a daily clamscan:
/etc/cron.daily/clamscan:
LibClamAV Warning: Ignoring empty field in " charset="
LibClamAV Warning: Ignoring empty field in " charset="
--- SCAN SUMMARY ---
Known viruses: 41434
Engine version: 0.8
Chris Purves wrote:
I receive the following output from a daily clamscan:
/etc/cron.daily/clamscan:
LibClamAV Warning: Ignoring empty field in " charset="
LibClamAV Warning: Ignoring empty field in " charset="
--- SCAN SUMMARY ---
Known viruses: 41434
Engine version:
On Sat, December 10, 2005 2:49 pm, Nigel Horne said:
> Chris Purves wrote:
>
>>On Tue, December 6, 2005 11:15 am, Chris Purves said:
>>
>>
>>>I receive the following output from a daily clamscan:
>>>
>>> >>>
>>>/etc/cron.daily/clamscan:
>>>LibClamAV Warning: Ignoring empty field in " charset="
>>>L
Chris Purves wrote:
On Tue, December 6, 2005 11:15 am, Chris Purves said:
I receive the following output from a daily clamscan:
>>>
/etc/cron.daily/clamscan:
LibClamAV Warning: Ignoring empty field in " charset="
LibClamAV Warning: Ignoring empty field in " charset="
--- SCAN SUMMA
On Tue, December 6, 2005 11:15 am, Chris Purves said:
> I receive the following output from a daily clamscan:
>
> >>>
> /etc/cron.daily/clamscan:
> LibClamAV Warning: Ignoring empty field in " charset="
> LibClamAV Warning: Ignoring empty field in " charset="
>
> --- SCAN SUMMARY -
I receive the following output from a daily clamscan:
>>>
/etc/cron.daily/clamscan:
LibClamAV Warning: Ignoring empty field in " charset="
LibClamAV Warning: Ignoring empty field in " charset="
--- SCAN SUMMARY ---
Known viruses: 41434
Engine version: 0.87.1
Scanned directories:
On 11/14/05, Tomasz Papszun <[EMAIL PROTECTED]> wrote:
>
> On Mon, 14 Nov 2005 at 14:22:47 +0100, Richard Pijnenburg wrote:
> > Have you also tried to update to version 0.87.1 ?
> >
> > ankush grover wrote:
> [...]
> > >___
> >
hey,
I will update it to
On Mon, 14 Nov 2005 at 14:22:47 +0100, Richard Pijnenburg wrote:
> Have you also tried to update to version 0.87.1 ?
>
> ankush grover wrote:
[...]
> >___
> >http://lurker.clamav.net/list/clamav-users.html
> >
>
> --
>
> Met vriendelijke groet,
>
> R
Have you also tried to update to version 0.87.1 ?
ankush grover wrote:
hey,
I am using clamav 0.87 on Fedora Core3.Since I have updated to 0.87 I
am getting this error.Actually I have set a cron job for scanning
whole system
at midnight through clamscan.
LibClamAV Error: cli_untar: only standa
hey,
I am using clamav 0.87 on Fedora Core3.Since I have updated to 0.87 I
am getting this error.Actually I have set a cron job for scanning
whole system
at midnight through clamscan.
LibClamAV Error: cli_untar: only standard TAR files are currently supported
LibClamAV Warning: Multipart MIME me
1 - 100 of 129 matches
Mail list logo
