Please remove from your list. El 28/02/2019 a las 12:55 p. m., Alessandro Vesely via clamav-users escribió:
Hi Micah, Thank you so much for your prompt reply. On Wed 27/Feb/2019 20:48:44 +0100 Micah Snyder \(micasnyd\) via clamav-users wrote: You're correct, there are non-backwards compatible changes in clamav.h in version 0.101. The libclamav major version number as also increased to highlight the incompatibility. The changes are mentioned somewhat briefly in the release notes: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.clamav.net%2F2018%2F12%2Fclamav-01010-has-been-released.html&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770130980116&sdata=1XgAZinVLS3Ab8kyjtOlckWXaie0znypFQyiJAsZs%2BI%3D&reserved=0 https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCisco-Talos%2Fclamav-devel%2Fblob%2Fclamav-0.101.1%2FNEWS.md%23some-of-the-more-obvious-changes&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770130980116&sdata=RA1T%2BVN4LSifcg3VZ%2B34MD4%2B60mczwTKZO6giQ4KHVc%3D&reserved=0 That doc is rather brief about #define's. I attach my attempt at matching them. Besides having different values and going to different variables, CL_SCAN_* have new names. CL_SCAN_STDOPT previously enabled all parsers, plus heuristic alerts (which were sometimes/inconsistently referred to as algorithmic detection): https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCisco-Talos%2Fclamav-devel%2Fblob%2Fclamav-0.100.2%2Flibclamav%2Fclamav.h%23L181&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770130980116&sdata=BSOZzzz%2B%2FqPE6n3msSufGaRkyrpw5nO%2B1BGPOpsgQKs%3D&reserved=0 In 0.101, CL_SCAN_STDOPT has gone away. Instead, you can get the same functionality by setting the following, as shown in the example (https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCisco-Talos%2Fclamav-devel%2Fblob%2Fdev%2F0.101%2Fexamples%2Fex1.c%23L93&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770130980116&sdata=B4%2B%2FT57guKkuBQRiWyfb7pOdzaeDPHkb9w%2FWj6fmC4M%3D&reserved=0): I see. I think I'll code #ifdef CL_SCAN_STDOPT for compile time switching, trying to be compatible with v100. options.parse |= ~0; /* enable all parsers */ options.general |= CL_SCAN_GENERAL_HEURISTICS; /* enable heuristic alert options */ The docs suggest AlgorithmicDetection becomes HeuristicAlerts, I'm not clear if that implies CL_SCAN_ALGORITHMIC becomes CL_SCAN_GENERAL_HEURISTICS (as claimed in my attachment). Best Ale _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net<mailto:clamav-users@lists.clamav.net> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.clamav.net%2Fmailman%2Flistinfo%2Fclamav-users&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770131000125&sdata=TLJpCqa57kSWru%2FnHHKbc89QftQqU%2BkD8Fw2jD%2FnMdM%3D&reserved=0 Help us build a comprehensive ClamAV guide: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvrtadmin%2Fclamav-faq&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770131000125&sdata=Kkw%2BnEdZc3kfYPxUlfUFTQqrhKIEHXH5r0KzXoJKj5U%3D&reserved=0 https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.clamav.net%2Fcontact.html%23ml&data=02%7C01%7C%7Cb49c566de1bd4af3c7af08d69dae7f35%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636869770131000125&sdata=%2BcG%2BNAe2XAYoE9KnPWgLU60T3VwcDGogenV9cjq%2FGIQ%3D&reserved=0
_______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
