Sorry, I was busy writing this mail.
Well, I'm not ClamAV, but I would bring order into the file chaos.
clam*d*scan should have its own config and clamscan too, because the two configs are not compatible.
For this reason I would wish that there would be also the option --config-file=URL with clamscan, in order to be able to load then the ONLY FOR clamscan valid settings.
As I said, as soon as you want to use an option of clam*d* scan for clamdscan, the whole process stops, customer-friendly is so I think not.
If the daemon also has its own configuration, then you have to think about what the config file could be called.
Von / From: Clamav User Mailinglist <mailto:clamav-users@lists.clamav.net>
An / To: Newcomer01 <mailto:newcomer01@posteo.de>
CC / CC: Andrew C Aitchison <mailto:clamav@aitchison.me.uk>
Gesendet / Sent: Montag, Dezember 12, 2022 um 17: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 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@aitchison.me.uk>
>> An / To: Newcomer01 <mailto:newcomer01@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 ?
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat