I believe it still works, but yes, you shouldn't use it.
> On Aug 2, 2019, at 3:51 PM, J.R. via clamav-users
> wrote:
>
> When browsing the page on creating signatures for clamav, I couldn't
> find info on the *.db format
>
> https://www.clamav.net/documents/creating-signatures-for-clamav
>
>
When browsing the page on creating signatures for clamav, I couldn't
find info on the *.db format
https://www.clamav.net/documents/creating-signatures-for-clamav
It used the simple format: MalwareName=HexSignature
I'm guessing it has been depreciated in favor of the extended
signature format? Do
Hello,
Le 02/08/2019 à 16:45, J.R. via clamav-users a écrit :
I just checked (again) today and SecuriteInfo.com doesn't support HTTP
compression when downloading its signatures...
Yes, I know. It could be a future feature on our side. Not so easy to
implement. It needs development.
On th
I just checked (again) today and SecuriteInfo.com doesn't support HTTP
compression when downloading its signatures...
Which is a shame because the files compress down to about 1/3-1/4
their original size.
Due to the semi-static nature of your files, you might want to have
pre-compressed copies on
Inline below:
> On Aug 1, 2019, at 11:33 PM, J.R. via clamav-users
> wrote:
>
>> I think that's the intended purpose of the local private mirror in this case.
>>
>
> I realize that, but I believe in that person's case back the he was
> doing a basic web server to re-distributed the full .cvd
