[clamav-users] LibClamAV Warning: PNG: Unexpected early end-of-file.

Andrew C Aitchison clamav at aitchison.me.uk
Mon Dec 12 16:34:39 UTC 2022


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 "program" 
> freshclam with the freshclam.conf.
> That is logic ;-)
>
> To feed clam*d*scan and clamscan with the same conf is stupid, because both 
> programs have different options.

clamscan (no 'd') does not have a config file at all.
Which options do you want to be different ?
Many of the options are the same. At least as a default I would expect the
  --scan-* --alert-* --max-* --*-pua options to be the same.

(Ignoring the freshclam config) clamscan *does not have a config file*
so there is curently no need for an option
 	--config-file=FILE

As I asked before,
which settings do you expect clamscan to read from this config ?


> Now it would be still super, if one would have the option --config-file=FILE 
> with the clamscan, as it is also the case with the clam*d*scan. If I want to 
> use the clamscan mutze and --config-file=URL, then this is of course not 
> possible and it breaks everything!
>
> Von / From: Andrew C Aitchison <mailto:andrew at aitchison.me.uk>
> An / To: Newcomer01 <mailto:newcomer01 at 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 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.
>> 
>>> Should i change something in my config for clamscan?
>> No.
>> 
>>> And mybe devs of clamav reas here to, it would be really nice, if you can 
>>> add
>>> the optional paramteter "---cofig-file="FILE" to clamscan too. Currnty 
>>> only
>>> cmab*d*scan has the option
>> The config file is for the clamd *daemon*.
>> clamd and clamdscan refer to it, but clamscan does not refer
>> this config file (although it *does* refer to freshclam.conf).
>> 
>> Which settings do you expect clamscan to read from this config ?

-- 
Andrew C. Aitchison                      Kendal, UK
                    andrew at aitchison.me.uk


More information about the clamav-users mailing list