You can view the documentation below, or browse our GitHub Repository, where you can contribute to user manual and FAQ.
General | Installing ClamAV | How to Report A Bug | Miscellaneous FAQ | ClamAV Virus Database FAQ | End of Life Policy (EOL) | Potentially Unwanted Applications (PUA) | Mailing Lists FAQ | Troubleshooting FAQ | Safebrowsing | Upgrading ClamAV | ClamAV on Microsoft Windows FAQ | Which Version of ClamAV should I use? | Uninstalling ClamAV | ClamAV Overview | Interpreting Scan Alerts FAQ | Freshclam FAQ | How do I ignore a ClamAV signature?
Manual | Clam AntiVirus User Manual
Manual | UserManual | Installing ClamAV on Unix / Linux / macOS from Source | Installing ClamAV on Windows | Introduction | LibClamAV | On-Access Scanning | Creating signatures for ClamAV | Usage | ClamAV Development
Manual | UserManual | Installation-Unix | Installation on Debian and Ubuntu Linux Distributions | Installation on macOS (Mac OS X) | Installation on Redhat and CentOS Linux Distributions
Manual | UserManual | Signatures | Trusted and Revoked Certificates | Body-based Signature Content Format | Bytecode Signatures | Signatures based on container metadata | Database Info | Dynamic Configuration (DCONF) | Passwords for archive files \[experimental\] | Extended signature format | File Type Magic | ClamAV File Types | Functionality Levels (FLEVELs) | File hash signatures | Logical signatures | PhishSigs | Using YARA rules in ClamAV | Allow list databases
Manual | UserManual | Usage | Configuration | Scanning | Signature Testing and Management
Additional | Microsoft Authenticode Signature Verification | Private Local Mirrors
CURRENT STATUS at October 2020.
The safebrowsing feature has now been spun off into a related project. It requires substantially more effort to implement safebrowsing than simply enabling the relevant freshclam.conf configuration option.
Briefly, tools are needed to
Download the data from Google to a local mysql database using Google’s API [*];
produce a local copy of the safebrowsing database file in a form suitable for use by the ClamAV tools;
distribute this database file to the systems which need it; and
optionally notify any clamd daemons of the change.
[*] For efficiency, the API permits downloading differences, in much the same way that ClamAV itself uses .cdiff files.
Documentation can be found at
https://github.com/Cisco-Talos/clamav-safebrowsing
HISTORY
ClamAV 0.95 introduced support for the Google Safe Browsing database.
For use with ClamAV a copy of the database was packed inside the file
“safebrowsing.cvd” which was distributed in the same way as the other
ClamAV database files via the ClamAV mirror network. Downloading the
database was disabled by default, and the feature was to be enabled
only with extreme caution. In order to enable this feature it was
necessary to add the option SafeBrowsing Yes
to freshclam.conf.
This would tell freshclam to download the safebrowsing.cvd database,
and when ClamAV found the database in the database directory it would
enable the safe browsing feature. To turn it off it was necessary to
remove the configuration option from freshclam.conf AND to remove the
safebrowsing files from the database directory. If clamd was running
it was necessary to restart it.
Updates to the safebrowsing.cvd database were discontinued in 2019 and it was declared obsolete.