Attributed metadata history

ClamAV 1.5.0 released!

The ClamAV 1.5.0 is now available. You may find the source code and installers for this release at clamav.net/downloads or on the ClamAV GitHub release page. IMPORTANT: A major feature of the 1.5 release is a FIPS-mode compatible method for verifying the authenticity of CVD signature database archives and CDIFF signature database patch files. This feature relies on “.cvd.sign” signature files for the daily, main, and bytecode databases. The Freshclam with 1.5.0 will download these files as will the latest version of CVDUpdate. When they are not present, ClamAV will fall back to using the legacy MD5-based RSA signature check.Tip: If you are downloading the source from the GitHub release page, the package labeled "clamav-1.5.0.tar.gz" does not require an internet connection to build. All dependencies are included in this package. However, if you download the ZIP or TAR.GZ generated by GitHub, located at the very bottom, then an internet connection will be required during the build to download additional Rust dependencies. ClamAV 1.5.0 includes the following improvements and changes: Major changesAdded checks to determine if an OLE2-based Microsoft Office document is encrypted.GitHub pull requestAdded the ability to record URIs found in HTML if the generate-JSON-metadata feature is enabled. Also adds an option to disable this in case you want the JSON metadata feature but do not want to record HTML URIs. The ClamScan command-line option is --json-store-html-uris=no. The clamd.conf config option is JsonStoreHTMLURIs no. The libclamav general scan option is CL_SCAN_GENERAL_STORE_HTML_URISGitHub pull request #1GitHub pull request #2GitHub pull request #3Added the ability to record URIs found in PDFs if the generate-JSON-metadata feature is enabled. Also adds an option to disable this in case you want the JSON metadata feature but do not want to record PDF URIs. The ClamScan command-line option is --json-store-pdf-uris=no. The clamd.conf config option is JsonStorePDFURIs no. The libclamav general scan option is CL_SCAN_GENERAL_STORE_PDF_URISGitHub pull request #1GitHub pull request #2GitHub pull request #3GitHub pull request #4Added regex support for the clamd.conf OnAccessExcludePath config option. This change courtesy of GitHub user b1tg.GitHub pull requestAdded CVD signing/verification with external .sign files.Freshclam will now attempt to download external signature files to accompany existing .cvd databases and .cdiff patch files. Sigtool now has commands to sign and verify using the external signatures.ClamAV now installs a 'certs' directory in the app config directory (e.g., <prefix>/etc/certs). The install path is configurable. The CMake option to configure the CVD certs directory is -D CVD_CERTS_DIRECTORY=PATHNew options to set an alternative CVD certs directory:The command-line option for Freshclam, ClamD, ClamScan, and Sigtool is --cvdcertsdir PATHThe environment variable for Freshclam, ClamD, ClamScan, and Sigtool is CVD_CERTS_DIRThe config option for Freshclam and ClamD is CVDCertsDirectory PATHAdded two new APIs to the public clamav.h header:cl_error_t cl_cvdverify_ex( const char *file, const char *certs_directory, uint32_t dboptions); cl_error_t cl_cvdunpack_ex( const char *file, const char *dir, const char *certs_directory, uint32_t dboptions); The original cl_cvdverify and cl_cvdunpack are deprecated.Added a cl_engine_field enum option CL_ENGINE_CVDCERTSDIR. You may set this option with cl_engine_set_str and get it with cl_engine_get_str, to override the compiled in default CVD certs directory.Thank you to Mark Carey at SAP for inspiring work on this feature with an initial proof of concept for external-signature FIPS compliant CVD signing.GitHub pull request #1GitHub pull request #2GitHub pull r

This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.