I would suggest not packaging them at all, and they should be downloaded from 
the update servers the first time the update is ran.

> On Aug 12, 2019, at 9:47 AM, Nick Howitt <n...@howitts.co.uk> wrote:
> 
> On 12/08/2019 13:25, J.R. via clamav-users wrote:
>> main.cvd rarely changes (last update was Jan 2018), it is only when
>> the daily gets so large they push a bunch of signatures over. Bytecode
>> also does not get updated very often. Really the only things are daily
>> & safebrowsing (if enabled) that change regularly.
>> 
>> Since the are 'signed' files, there's really no way for a 3rd party to
>> fudge them (afaik).
>> 
>> I don't think it would be wise to include stub files, because if there
>> is a network issue during install a person could falsely believe that
>> their installation was successful and being protected, when they
>> really aren't. Even if you are including files that are slightly
>> outdated, that's giving them some level of protection out of the box.
>> 
>> _______________________________________________
>> 
>> clamav-users mailing list
>> clamav-users@lists.clamav.net
>> https://lists.clamav.net/mailman/listinfo/clamav-users
>> 
>> 
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>> 
>> http://www.clamav.net/contact.html#ml
> Thanks for replying.
> Are you suggesting just packaging main.cvd and not packaging daily.cvd or 
> bytecode.cvd?
> 
> 
> _______________________________________________
> 
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
> 
> 
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
> 
> http://www.clamav.net/contact.html#ml

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to