There's no need to create a CVD if all you want is to use official
clamav signatures and non-official signatures.

Use "sigtool -u" with a clamav cvd to unpack  it and choose the
signatures you want.

You can then point clamscan or clamdscan to the directory that
contains your signatures, official or non.

-Alain

> On Dec 16, 2016, at 12:52 PM, "filipecalderon66...@yahoo.com" 
> <filipecalderon66...@yahoo.com> wrote:
>
> Thanks Al. Unfortunately I require a bunch of the unofficial sigs for this 
> project.
>
>
>    On Thursday, December 15, 2016 8:47 PM, Al Varnell <alvarn...@mac.com> 
> wrote:
>
>
> Not a basic question, but one that has been asked several times before, so 
> you should search the archives for possible answers.
>
> There aren't any easy solutions with regard to the official signatures, so if 
> I were you I would focus on the unofficially ones you use first. Most of them 
> are designed for special purpose detection and may not be doing anything for 
> whatever your specific application is.
>
> Memory and media costs are small compared to the time expense you will need 
> to do what you are proposing.
>
> Sent from Janet's iPad
>
> -Al-
> --
> ClamXav User
>
>> On Dec 15, 2016, at 6:39 PM, wrote:
>> Hello all - first time post and new clamav user.
>> I have installed clamav on a box that has very specific exposures, and has 
>> very limited memory and disk space. The existing signatures when all the 
>> other optional ones are loaded like unofficial-sigs creates a ginormous file 
>> and eats all my memory. At first I thought I'd just create a whitelist of 
>> sigs to ignore, but that does not solve my problems of limited space/memory. 
>> Then I thought my solution would be to just create a minimal set of sigs 
>> from the daily.cvd file and then create my own daily.cvd. I didn't realize 
>> at the time that the cvd file is signed (whoops) and obviously this created 
>> a problem.
>> Is it possible for me to roll my own daily.cvd and if so how? Sorry if this 
>> is a basic question.
>> FC
> _______________________________________________
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
>
>
>
> _______________________________________________
> clamav-users mailing list
> clamav-users@lists.clamav.net
> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/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