I’ve suddenly started receive a lot of emails from Qnap users saying they can’t
update ClamAV anymore. Anyone have a Qnap system that is technically inclined
that can help me troubleshoot?
Sent from my iPhone
___
clamav-users mailing list
J.R. is correct about the `--database=FILE/DIR` or `-d FILE/DIR` option being
for clamscan. The for clamd, you'll have to place it in your database
directory.
Our documentation on Github is moving from the clamav-devel repo over to our
https://github.com/Cisco-Talos/clamav-faq repository so
Also I believe you have to use clamscan, not clamdscan if you want to
use the "-d" option. However once you test it successfully you can add
it as a custom db for clamd to load.
___
clamav-users mailing list
clamav-users@lists.clamav.net
On 30.01.19 11:46, Joel Esler (jesler) wrote:
I’ve suddenly started receive a lot of emails from Qnap users saying they can’t
update ClamAV anymore. Anyone have a Qnap system that is technically inclined
that can help me troubleshoot?
On 30.01.19 18:38, Matus UHLAR - fantomas wrote:
seems
On 30.01.19 11:46, Joel Esler (jesler) wrote:
I’ve suddenly started receive a lot of emails from Qnap users saying they can’t
update ClamAV anymore. Anyone have a Qnap system that is technically inclined
that can help me troubleshoot?
seems they have fscked up their new firmware version:
Hello,
I read this document
https://blog.clamav.net/2016/06/create-your-own-anti-virus-signatures.html
I need add a signature to database:
# cat 30012019_term_4373.doc | sigtool –hex-dump | head -c 2048 > customsig.ndb
# clamdscan -d customsig.ndb 30012019_term_4373.doc
WARNING: Ignoring
Hi Emanuel,
When creating ClamAV signatures, refer to
https://github.com/Cisco-Talos/clamav-devel/tree/dev/0.102/docs/UserManual,
specifically:
- NDBs:
https://github.com/Cisco-Talos/clamav-devel/blob/dev/0.102/docs/UserManual/Signatures/ExtendedSignatures.md
- LDBs:
