Bug 963920
Summary: | clamav-filesystem has useradd and groupadd issues | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Schanzle <bugzilla> |
Component: | clamav | Assignee: | Nick Bebout <nb> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | cristis53, darthludi, frankly3d, j, martin.marques, mhw, nathanael, nb, olaf.lessenich+redhatbugs, ondrejj, pwouters, redhat-bugzilla, sergio, steve |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | clamav-0.97.8-2.fc17 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-18 06:24:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Schanzle
2013-05-16 18:53:52 UTC
Workaround: pre-create group and user account, then install or reinstall with yum: yum remove clamav\* groupadd -r clamupdate useradd -r -g clamupdate -d /var/lib/clamav -s /sbin/nologin -c "Clamav database update user" clamupdate yum install clamav clamav-update In reviewing the clamav.spec, I also see similar issues with %pre scanner getent group %{scanuser} >/dev/null || groupadd -r ${scanuser} -g 49 getent passwd %{scanuser} >/dev/null || \ useradd -r -g %{scanuser} -d / -s /sbin/nologin -u 49 \ -c "Clamav scanner user" %{scanuser} exit 0 I suggest: 1. removing '-g 49' 2. fixing ${scanuser} to %{scanuser} 3. removing '-u 49' So that it appears as below: getent group %{scanuser} >/dev/null || groupadd -r %{scanuser} getent passwd %{scanuser} >/dev/null || \ useradd -r -g %{scanuser} -d / -s /sbin/nologin \ -c "Clamav scanner user" %{scanuser} exit 0 I also see use of ${milteruser} rather than %{milteruser} which is broken. There is much inconsistent use of braces around macro names (e.g., %{milteruser} vs %milteruser) and some macros never have braces when used (%milterlog), but I do not see where this violates any packaging guidelines. Seriously broken. I've been running into this. Workaround are useless if you are building respins such as the Network Security Toolkit (NST) since they're trying to build run-live file systems that include this package and you have no opportunity to precreate the user and group ids. *** Bug 964328 has been marked as a duplicate of this bug. *** clamav-0.97.8-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/clamav-0.97.8-2.fc18 clamav-0.97.8-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/clamav-0.97.8-2.fc19 clamav-0.97.8-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/clamav-0.97.8-2.fc17 Package clamav-0.97.8-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing clamav-0.97.8-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10853/clamav-0.97.8-2.fc19 then log in and leave karma (feedback). clamav-0.97.8-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. Any chance of getting this fix into the reported release (Fedora 18 Spherical Cow)? (In reply to Peter Ludikovsky from comment #10) > Any chance of getting this fix into the reported release (Fedora 18 > Spherical Cow)? Read comment #5 clamav-0.97.8-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. clamav-0.97.8-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |