Skip to content

Maldet with autoupdate_version and a remote Clamav server #456

@fredo-m

Description

@fredo-m

Hi,

I'm trying to get maldet 1.6.6 to work with autoupdate_version and switch from a local Clamav to a remote Clamav server. Maldet is launched by the cron script. I uninstalled clamscan from Debian server, only clamdscan remains.

The autoupdate overwrites some settings in the "conf.maldet" file. So I placed these settings in the "conf.maldet.cron" file:

email_addr="toto@XXXX"
autoupdate_signatures="1"
autoupdate_version="1"
autoupdate_version_hashed="1"
scan_days=5
scan_clamscan="1"
scan_clamd_remote="1"
remote_clamd_config="/etc/clamav/clamd.conf"

With this configuration clamdscan is not launched.

The settings in the "conf.maldet.cron" file are used by the cron script. Then the cron script runs the "maldet" command, which loads the "internals/internals.conf" file. This defines a "cron_custom_conf" variable with the path to the "conf.maldet.cron" file. But I have the impression that the "cron_custom_conf" variable is not used and clamdscan is not launched.

Looking at the code, I noticed that the maldet command uses the "/etc/default/maldet" file. I duplicated in this file what I had put in the "conf.maldet.cron" file. And now maldet works correctly with autoupdate and the remote clamav server.

In the "conf.maldet.cron" file it says that all variables can be redefined. I have the impression that this doesn't work every time.

The documentation should perhaps clarify the use of the "conf.maldet.cron" and "/etc/default/maldet" files.

Regards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions