[clamav-users] Manual cdiff update procedure
venkat.330 at gmail.com
Thu Apr 6 07:35:04 EDT 2017
Mentioned below is my current progress.
all in /tmp/clam folder
sigtool --unpack-current=daily (Unpacked Existing CVD from /var/lib/clam)
sigtool --verify-cdiff /media/sf_works/python/clamAv/daily-23265.cdiff
daily.cvd (Verfied it using sigtool for match)
sigtool --run-cdiff /media/sf_works/python/clamAv/daily-23265.cdiff
daily.cvd (Applied using this command)
After this process, this BUILD is my only option (sigtool --build
daily.cvd --server "" ) But I do not have any signing server to build
so what will happen if i copy all these contents from temp folder to
/var/lib/clam folder.. Will it use the updated DB for scanning threats
On Thu, Apr 6, 2017 at 2:29 PM, Mark Allan <markjallan at gmail.com> wrote:
> Yes and no. You can use sigtool to unpack and then apply the individual cdiff scripts in turn (check the man page for details). This will give you a directory full of files which is the equivalent of the current cvd file, however you cannot then repackage and sign the resulting database directory.
>> On 5 Apr 2017, at 6:51 pm, venkat swaminathan <venkat.330 at gmail.com> wrote:
>> Hello All,
>> I am very new to clamav and trying to understand some update procedure.
>> I\i have daily.cvd and its new cdiff file. is there a procedure document
>> where i will be able follow and update daily.cvd with newly downloaded
>> cdiff files.
>> clamav-users mailing list
>> clamav-users at lists.clamav.net
>> Help us build a comprehensive ClamAV guide:
> clamav-users mailing list
> clamav-users at lists.clamav.net
> Help us build a comprehensive ClamAV guide:
More information about the clamav-users