$ sigtool --info safebrowsing.cvd File: safebrowsing.cvd Build time: 30 Apr 2018 18:49 -0400 Version: 47323 Signatures: 2898788 Functionality level: 63 Builder: google MD5: df018f5caf24960004570ab3eb0b2049 Digital signature: P+Jbcme4Qp66dwjnHxKCXwyhhZ3xg0QvI5bSDTNP9UwkRDmL1DNeTDZJcPGdWiIQOScjwpt1kFU1z4ImWvL+w9ENN3mRyZMRL7vUw7fKKkIirdwyCa1KfddGk6JOEsAtUPf1CmMBOytzXX6Oa2ljUad9ViEkkLe17NtXygczIWj Verification OK.
just in case someone saw the same. I haven’t tried the latest cvd but I’ll do it so later today. > On May 1, 2018, at 1:19 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > > > > Am 01.05.2018 um 04:40 schrieb Rafael Ferreira: >> It seems that the latest safebrowsing.cvd update is causing clamd daemons >> with version 0.99 to get into a broken state (100% cpu and rampant memory >> growth) > > no - but hey, who knows what is "the latest" for you > > May 1 07:25:57 buildserver freshclam[7413]: Downloading > safebrowsing-47324.cdiff [100%] > May 1 07:26:05 buildserver freshclam[7413]: safebrowsing.cld updated > (version: 47324, sigs: 2898710, f-level: 63, builder: google) _______________________________________________ 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
