clamav-milter socket permissions wrong
Bug #430418 reported by
Stephen Warren
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ClamAV |
Unknown
|
Unknown
|
|||
clamav (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Binary package hint: clamav
According to /etc/default/
## SOCKET_RWGROUP
# by default, the socket created by the milter has permissions
# clamav:clamav:755. SOCKET_RWGROUP changes the group and changes the
# permissions to 775 to give read-write access to that group.
This doesn't make sense:
* A socket shouldn't ever have execute permissions.
* If the idea is that only a particular user/group should have access to the socket, no group/world permissions should be set at all.
So, I think the modes should be 600 or 660 respectively.
Changed in clamav (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
To post a comment you must log in.
This is the upstream default. I'd suggest file a bug with upstream and see how open they are to changing it:
https:/ /wwws.clamav. net/bugzilla/