I seem to remember that the community signature program has aways welcomed all unofficial sig programs to join so that those sigs could be QC'd and de-duped. I think that is very generous and the only way that Cisco/ClamAV would be able to host those signatures in any official capacity. Few, if any such programs have agreed to participate, mostly due to the factors you mention.

What you are suggesting would likely result in an out-of-control situation for the ClamAV staff with uncontrolled duplication and additional work to resolve False Positives.

I'm not sure what you find unacceptable about the current script procedure that has been successfully used by a multitude of users for a very long time now. I recall having used it over a decade ago without too much effort, but found it didn't have much to add for Mac users and removed it after a short period.

But I can't speak for Joel and his team and I'm sure they will evaluate your suggestion and let you know shortly.

-Al-

On Feb 18, 2019, at 02:44, Paul Wise <pabs3@bonedaddy.net> wrote:

Hi folks,

Previously Joel Esler pointed out that ClamAV has a community signature
program and I pointed out that this isn't sufficient to replace the
clamav-unofficial-sigs script that helps to download various
third-party signatures and install them into the ClamAV
signatures directory.

https://lists.debian.org/msgid-search/7691F66D-AC31-411E-98D6-6B53FE860208@cisco.com
https://github.com/extremeshok/clamav-unofficial-sigs

As far as I can tell, these third-party signatures are never going to
be merged into the official ClamAV signature set, since some of them
require an account and others are paid subscription services.

I would really like to see clamav-unofficial-sigs be replaced with a
simple configuration file for freshclam that adds the additional
third-party signatures to the freshclam download process. The config
file could be shipped with freshclam itself but disabled by default.

Is this something that ClamAV could support?

-- 
bye,
pabs