Hello developers,

I have a main goal, namely to prefix third-party signatures as well as official ClamAV signatures so that the signature source is easily identifiable for each found virus.

1. Is there a documented and/or preferred way to do it? It seems easy to do so with some script for most database types, because they are line-based and human-readable. It is not trivial for bytecode signatures, though. Hence the second question:

2. Are there plans to make clamav-bytecode-compiler work with Clang/LLVM newer than 16? Debian Stable has versions 17-19, and version 17 turned out incompatible already.

Regards
_______________________________________________

clamav-devel mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-devel

Please submit your patches to our Github: 
https://github.com/Cisco-Talos/clamav-devel/pulls

Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to