Hello Stêphane,
I am using ClamScan and have a subscription from securiteinfo.com, as you have described in the ClamScan documentation But I’m not sure what the right way is to integrate this into ClamScan properly. Do I have to copy the links at the top of the image into /etc/clamav/freshclam.conf or do I have to go another way?
OK, back to Clamscan…
Is there anything else I need to know about the settings in the app Or does Clamscan now download the signatureaupdates automatically from secureinfo.com?
ClamAV update process started at Sat Aug 8 11:47:59 2020
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.102.3 Recommended version: 0.102.4
DON’T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
daily.cvd database is up to date (version: 25897, sigs: 3804349, f-level: 63, builder: raynman)
main.cvd database is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
bytecode.cvd database is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
securiteinfo.hdb is up to date (version: custom database)
securiteinfo.ign2 is up to date (version: custom database)
Time: 1.5s, ETA: 0.0s [=============================>] 14.91MiB/14.91MiB
Testing database: ‘/var/lib/clamav/tmp.1ef60/clamav-616b6d91ad882237bef295801d20b480.tmp-javascript.ndb’ …
Database test passed.
javascript.ndb updated (version: custom database, sigs: 43527)
spam_marketing.ndb is up to date (version: custom database)
securiteinfohtml.hdb is up to date (version: custom database)
securiteinfoascii.hdb is up to date (version: custom database)
securiteinfoandroid.hdb is up to date (version: custom database)
securiteinfoold.hdb is up to date (version: custom database)
securiteinfopdf.hdb is up to date (version: custom database)
Time: 0.2s, ETA: 0.0s [=============================>] 14.47KiB/14.47KiB
Testing database: ‘/var/lib/clamav/tmp.1ef60/clamav-fb7dc3a97e8d17a5ba2f2114fbb5f4e5.tmp-securiteinfo0hour.hdb’ …
Database test passed.
securiteinfo0hour.hdb updated (version: custom database, sigs: 167)
securiteinfo.mdb is up to date (version: custom database)
[root@