Who screwed up ClamAV in F18?

[Michael H. Warfield]

Ok...  (Before anyone tells me I need to) I will be filing a bugzilla
report on this later today but someone did a bad thing in ClamAV.

If you install the latest packages from the update repositories, they
url chunks unable to create the clamupdate user and group.  Problem
appears to be in the clamav-update package.

During the yum install of the clamav packages...

[Michael Schwendt]

On Tue, 28 May 2013 09:36:18 -0400, Michael H. Warfield wrote:
> Ok...  (Before anyone tells me I need to) I will be filing a bugzilla
> report on this later today but someone did a bad thing in ClamAV.

A different suggestion: If you care about ClamAV in the Fedora package
collection, observe it more closely. Fresh installs probably have not
been (re)tried, but three testers have given feedback on the update:
https://admin.fedoraproject.org/updates/FEDORA-2013-8047/clamav-0.97.8-1.fc1...

[Reindl Harald]

Am 28.05.2013 15:52, schrieb Michael Schwendt:
> On Tue, 28 May 2013 09:36:18 -0400, Michael H. Warfield wrote:
> > Ok...  (Before anyone tells me I need to) I will be filing a bugzilla
> > report on this later today but someone did a bad thing in ClamAV.
>
> A different suggestion: If you care about ClamAV in the Fedora package
> collection, observe it more closely. Fresh installs probably have not
> been (re)tried, but three testers have given feedback on the update:
> https://admin.fedoraproject.org/updates/FEDORA-2013-8047/clamav-0.97.8-1.fc1...

it works without any problem on machines installed 2011
with F14 and after that 4 times "yum distro-sync"-upgrades

----------- SCAN SUMMARY -----------
Known viruses: 2287387
Engine version: 0.97.8
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 69.57 MB
Data read: 14.71 MB (ratio 4.73:1)
Time: 10.307 sec (0 m 10 s)

[root@rh:/fileserver/software/windows]$ rpm -q clamav
clamav-0.97.8-1.fc18.x86_64

[Michael H. Warfield]

On Tue, 2013-05-28 at 16:00 +0200, Reindl Harald wrote:
> Am 28.05.2013 15:52, schrieb Michael Schwendt:
> > On Tue, 28 May 2013 09:36:18 -0400, Michael H. Warfield wrote:
> > > Ok...  (Before anyone tells me I need to) I will be filing a bugzilla
> > > report on this later today but someone did a bad thing in ClamAV.
> >
> > A different suggestion: If you care about ClamAV in the Fedora package
> > collection, observe it more closely. Fresh installs probably have not
> > been (re)tried, but three testers have given feedback on the update:
> > https://admin.fedoraproject.org/updates/FEDORA-2013-8047/clamav-0.97.8-1.fc1...
> it works without any problem on machines installed 2011
> with F14 and after that 4 times "yum distro-sync"-upgrades

It would.  The "clamupdate" user and group already exist then and it
doesn't have to add them.  It's strictly with a new installation of
ClamAV where the user and group doesn't exist that it fails to create
them and causes problems later on.  Existing systems are not impacted.
The only reason I ran into this was when I set up a new, pristine, F18
system for testing out NST (Network Security Toolkit) respin builds and
it started hurling chunks with ClamAV.
> ----------- SCAN SUMMARY -----------
> Known viruses: 2287387
> Engine version: 0.97.8
> Scanned directories: 0
> Scanned files: 1
> Infected files: 0
> Data scanned: 69.57 MB
> Data read: 14.71 MB (ratio 4.73:1)
> Time: 10.307 sec (0 m 10 s)
>
> [root@rh:/fileserver/software/windows]$ rpm -q clamav
> clamav-0.97.8-1.fc18.x86_64

Regards,
Mike

[Michael H. Warfield]

I see it's already been reported...

https://bugzilla.redhat.com/show_bug.cgi?id=963920

On Tue, 2013-05-28 at 09:36 -0400, Michael H. Warfield wrote:
> Ok...  (Before anyone tells me I need to) I will be filing a bugzilla
> report on this later today but someone did a bad thing in ClamAV.
>
> If you install the latest packages from the update repositories, they
> url chunks unable to create the clamupdate user and group.  Problem
> appears to be in the clamav-update package.
>
> During the yum install of the clamav packages...
>
> -- 
>  groupadd [options] GROUP
>
> Options:
>   -f, --force                   exit successfully if the group already exists,
>                                 and cancel -g if the GID is already used
>   -g, --gid GID                 use GID for the new group
>   -h, --help                    display this help message and exit
>   -K, --key KEY=VALUE           override /etc/login.defs defaults
>   -o, --non-unique              allow to create groups with duplicate
>                                 (non-unique) GID
>   -p, --password PASSWORD       use this encrypted password for the new group
>   -r, --system                  create a system account
>   -R, --root CHROOT_DIR         directory to chroot into
>
> useradd: group 'clamupdate' does not exist
> warning: user clamupdate does not exist - using root
> warning: group clamupdate does not exist - using root
>
> Installing: clamav-filesystem            ################### [1522/2490] 
>   Installing: clamav-update                ################### [1523/2490]/usr/bin/chown: invalid group: ‘root:clamupdate’
> No such file or directory
> warning: %post(clamav-update-0.97.8-1.fc18.x86_64) scriptlet failed, exit status 1
>
> --
>
> I've had to add that user and group by hand on some of my real systems
> but that's not possible in building the NST (Network Security Toolkit)
> http://www.networksecuritytoolkit.org/nst/index.html respins of F18
> since those are building bootable iso images.
>
> Obviously, it only affects fresh installs where someone installs ClamAV
> on a new system (or, at least, one that hasn't had it on there before).
> If the UID and GID already exist on the system, there's not a problem.
>
> Regards,
> Mike