no, the cvd cannot be recreated from the directory since it needs to be signed, in your case freshclam failed to download a differential then it downloaded the whole daily.cvd and removed daily.inc

Would it be possible for you to just keep the signatures on one server and have all computers on the LAN use those signatures when scanning?

Regards,

Do you mean by shared folders? Yes, but I wouldn't want to because I don't really have a server. I just use my own computer as the base for spreading out updates. I wouldn't want it to be constantly used by the other computers.

I say if you can create daily.cvd from scratch then you can also create it from the folder on the fly. Nothing beats having just one file. It's a chore having to worry about a whole folder.

Any updates on that evaluation? It drives me nuts. Again, it's all the same to me if you just find a way to recreate daily.cvd upon closing the update screen. But be it as it may, the current situation is a disaster. I've started updating much less often hoping it would give up and download the whole file (which tends to happen if you update less frequently).

Don't you see you're killing ClamWin with this for people with networks?!

Please find a way for us to end up just with 2 files - main and daily, and not with whole folders.

All I want is for client computers to compare their daily and main files' dates with mine and update if needed.

Doesn't the new update method effect how to install or update a https://www.clamwin.com/content/view/118/89/ "Portable ClamWin on a USB or Removable Drive" ?

I'm just a regular ClamWin user (not ClamWin Portable) trying to save the developers some time so they can do some more work on version 1.0, so I could be wrong, but I believe there are some program defaults that should take care of updates--provided you have configured the signature database directory to be where you want it to be--which would be on your portable app drive with the executables, I think. If I'm wrong, I'm sure someone will say so.

Regards,

you can still use .cvd files, .inc directories are for incremental updates, but you'll have main.cvd and daily.cvd if you remove the .inc dir
and do an update, so manual download of .cvd files is still ok

The new method finally gave in a little. In v0.93 there's no longer a folder but just a single file called "daily.cld".

Nevertheless, it's 4 times the size of daily.cvd and if I rename it to "daily.cvd" things go wrong.

Can't you please just call it "daily.cvd"? It's a mess enough trying to get other network computers to catch up on one file.

1. ClamWin does not make these decisions, ClamAV does. ClamWin is a front-end for the ClamAV engine. (www.clamav.net)
2. The ".inc" folders were to support incremental updates.
3. The CLD format replaces the ".inc" directories.
4. CLD formats are a zlib (?) container which supports incremential updates
5. CLD formats are uncompressed by default.

I'm not sure why it makes a difference if they use subdirectories or files though. It seems like it would be fairly simple to write a batch script to copy all these files from a shared resource like a network share or http server. Alternatively, you could waste a lot of your own bandwidth, and clamav's bandwidth (a rude thing to do) and delete the cld file prior to update, which results in a full cvd file being pulled down.

b0ne cld is a tar (not gzip-ed) file with 512bytes header, similar to cvd that is gzip-ed
they are not inter-changeables

ClamAV has no forum. Can't you just run some sort of command (untar & gzip) on daily.cld to turn it into daily.cvd?

yes possible but it would not be digital signed anymore and clamav will complain about non-verified digital signature
cvd files are digitally signed with clamav team private key and the client will check against their public key
to check if its "genuine"

Hi,

I just thought I'd add my comments on this.

I also run a LAN of Windows PCs behind a server. In my case the server is a linux box.

Previously, I would ensure that freshclam on the linux server ran and updated daily.cdb, published that directory on my internal webserver, and configured all my ClamWin clients to retrieve their updates from my server. Neat - it worked well.

Then came the .inc directory, and now the cdiff files. I struggled at first with the .inc directory, but the .cdiff files caused my setup to break completely.

My current solution is to configure all my ClamWin clients to use the caching webproxy (squid) on my linux server for updating from the clamav.net servers. What happens is that the first PC to update grabs the file(s), and then subsequent PCs find that file in the proxy cache.

It is simple to set up, is robust, and requires no maintenance. And best of all, it handles even exceptional cirsumstances automatically. When I run up a new PC, it will automatically get all the files it needs. Those that are in the cache come from there, and those which aren't (were never retrieved, or have been cleaned up) are retrieved from the internet.

I don't know of everyone else's exact situation, but a caching web-proxy is working perfectly for me.

Cheers!
Nik

When I download virus database updates from your link
https://www.clamwin.com/content/view/58/27/ https://www.clamwin.com/content/view/58/27/

they are main.cvd & daily.cvd but when I update from ClamWin they are main.cld & daily.cld!!
Now I want to go with only one of them either .cvd or .cld !!!
I installed ClamWin in portable form https://www.clamwin.com/content/view/118/89/ https://www.clamwin.com/content/view/118/89/ on my system for my feild work, some times I update Clamwin directly (on my system) and sometimes manually (on feild).

Please guide me what can I do or which method is good!!!

Thaks in advance