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

Clamav socket #1

Closed
teoberi opened this issue Dec 1, 2022 · 2 comments
Closed

Clamav socket #1

teoberi opened this issue Dec 1, 2022 · 2 comments

Comments

@teoberi
Copy link

teoberi commented Dec 1, 2022

According to the configuration file clamav/etc/clamd.conf.sample the local socket file is clamd.socket but in the configuration file squid-ecap-av/src/ecap_adapter_av.conf it appears avdsocket = /tmp/clamd.sock
To avoid changing the configuration file, it would be necessary to update avdsocket = /tmp/clamd.sock -> avdsocket = /tmp/clamd.socket
Are there any issues preventing this update?

@sp-andwei
Copy link

Seems reasonable.

@teoberi
Copy link
Author

teoberi commented Aug 29, 2023

Sorry for that!
It seems that the latest version of Clamav 1.2.0 remodifies the socket name and location for (clamd.socket -> clamd.sock) to reflect the recommended in Docker images.
https://github.com/Cisco-Talos/clamav/releases/tag/clamav-1.2.0

Other improvements
...
The suggested path for the clamd.pid and clamd.sock file in the sample
configs have been updated to reflect the recommended locations for these files
in the Docker images. These are:

/run/clamav/clamd.pid
/run/clamav/clamd.sock
For consistency, it now specifies clamd.sock instead of clamd.socket

Patch courtesy of computersalat.

GitHub pull request: Cisco-Talos/clamav#931

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants