Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create default clam daemon scan configuration #1870

Closed
ramizpolic opened this issue Jul 8, 2024 · 0 comments · Fixed by #1920
Closed

Create default clam daemon scan configuration #1870

ramizpolic opened this issue Jul 8, 2024 · 0 comments · Fixed by #1920
Labels
no-stale Marks an issue so that it never goes stale.

Comments

@ramizpolic
Copy link
Member

ramizpolic commented Jul 8, 2024

Overview

Currently, we use clamscan to perform malware testing. However, using clamdscan is more performant and we should use it by default. To do that, we need to create default configuration file to use with daemon scan, otherwise the clam scanner uses default empty config which makes the scanner throw errors (daemon cannot use empty config).

  1. Define default clam daemon scan configuration and enable clam daemon scanner to be used by default (when use_daemon=true, and clam_daemon_config_path="". The default file should reside in temp directory.
  2. Once the default configuration has been added, make sure to switch to clam daemon scan by default when creating a scanner/posting scan configs.
@ramizpolic ramizpolic added the no-stale Marks an issue so that it never goes stale. label Jul 8, 2024
@zsoltkacsandi zsoltkacsandi linked a pull request Jul 16, 2024 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-stale Marks an issue so that it never goes stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant