1.
Introduction
2.
Installing
2.1.
Packages
2.2.
Docker
2.3.
Unix from source (v0.104+)
2.4.
Unix from source (v0.103-)
2.5.
Windows from source
2.6.
Community Projects
2.7.
Add a service user account
3.
Usage
3.1.
Configuration
3.2.
Updating Signature Databases
3.3.
Scanning
3.3.1.
On-Access Scanning
3.4.
Running ClamAV Services
3.5.
Report a Bug
4.
Signatures
4.1.
CVD Info File
4.2.
Dynamic Configuration Settings
4.3.
Trusted and Revoked EXE Certificates
4.4.
File Type Recognition
4.5.
Allow Lists
4.6.
Hash-based Signatures
4.7.
Content-based Signature Format
4.7.1.
Logical Signatures
4.7.2.
Extended Signatures
4.8.
YARA Rules
4.9.
Phishing Signatures
4.10.
Bytecode Signatures
4.11.
Container Metadata Signatures
4.12.
Archive Passwords (experimental)
5.
For Developers
5.1.
Pull Request Basics
5.2.
ClamAV Git Work Flow
5.3.
Working with Your Fork
5.4.
Reviewing Pull Requests
5.5.
Building for Development
5.6.
Building the Installer Packages
5.7.
Dev Tips & Tricks
5.8.
Performance Profiling
5.9.
Computing Code Coverage
5.10.
Fuzzing Sanitizers
5.11.
libclamav
5.12.
Contribute
6.
Frequently Asked Questions
6.1.
Selecting the Right Version of ClamAV for You
6.2.
FreshClam (Signature Updater)
6.3.
Signature Database (CVD)
6.4.
Misc
6.5.
Mailing Lists
6.6.
Safe Browsing
6.7.
Troubleshooting
6.8.
Interpreting Scan Alerts
6.9.
Upgrading
6.10.
Win32
6.11.
PUA (Potentially Unwanted Application)
6.12.
Ignore
6.13.
Uninstall
6.14.
ClamAV EOL Policy
7.
Appendix
7.1.
Terminology
7.2.
Hosting a Private Database Mirror
7.3.
Microsoft Authenticode Signature Verification
7.4.
ClamAV File Types and Target Types
7.5.
ClamAV Versions and Functionality Levels
Dark
Light
ClamAV Documentation
Using YARA rules in ClamAV
Due to an incompatible license for the YARA code, using YARA rules is not possible in (open)SUSE.