-
Notifications
You must be signed in to change notification settings - Fork 0
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
Requesting new variable #1
Comments
Hi, note that this will require to create/fix run directory for clamav daemon accordingly to the value you give (using tmpfiles.d) , so this may require to restart server or launch "systemd-tmpfiles --create" each time you change this value sorry for the late reply |
let me know if it does not work as expected |
I think you mean the |
It's not working, adjusting the ETA: I believe that new variable needs to go here: Mode 0750 is still hard coded. |
in fact there are plenty of variables, and permission layers : by changing only the latter clamav_daemon_socket_group and leaving the other ones by default it should work (allow users in that group the directory traversal needed to reach the world-writable socket), but see my warning above on using tmpfiles.d : you need some more step to actually "recreate" the directory with your custom group if you do not want to reboot |
sorry i forgot i've changed the "world-writable" default socket permissions to user and group writable : see variable clamav_daemon_socket_mode: '660', but the comment above still applies |
Greetings.
First, this is a great role I appreciate the effort you've put into it. I've tried three ClamAV roles and this is the best one so far.
I would like to request you add a variable that will let users control the permissions on
clamav_daemon_localsocket
's directory. I understand what you're trying to do with the 'add users to the virusgroup' functionality, but sometimes it's just easier and simpler to relax perms on the directory itself.The text was updated successfully, but these errors were encountered: