#125 closed defect (fixed)

cups-files.conf.default from cups 2.1.3 is in error

Reported by: lewisr Owned by:
Priority: Feedback pending Milestone:
Component: cups Version:
Severity: medium Keywords:


cups-files.conf.default contains:

# Administrator user group, used to match @SYSTEM in cupsd.conf policy rules...
# This cannot contain the Group value for security reasons...
SystemGroup admin

Unfortunately, with this line, cupsd.exe -t fails with:

[c:\usr\sbin] cupsd.exe -t
"/@unixroot/etc/cups/cups-files.conf" contains errors.

I'm not certain what group name should be used there, as no matter what I try cupsd -t returns a notice that the file contains errors.

Was cupsd really built with the --with-system-groups option? Are we ensuring that the default system group has been created upon cups install? On this machine, for example, groups says:

{1}[c:\usr\sbin] groups
groups.exe: cannot find name for group ID 0

There is no /@unixroot/etc/group file, so I'm not even sure how we handle these in our environment (we don't seem to have groupadd available).

Commenting the SystemGroup? parameter resolves the error, but I can't tell whether this is causing printing to fail (separate ticket).

Change History (8)

comment:1 Changed 19 months ago by diver

It's perfect valid. The group stuff comes either with samba or with our still to deliver klibc user management.

comment:2 Changed 19 months ago by lewisr

Okay, then. So in order to create a valid group I need to install...what? And in so doing, should I create a "lp" group for this or an "admin" group? How?

I know how all of this works on Linux. It's the translation to OS/2-land which is always so baffling to me. ;-)

comment:3 Changed 19 months ago by diver

I will give you the right hints soon. But first I finally need to create the missing klibcum rpm.

comment:4 Changed 18 months ago by diver

  • Priority changed from major to Feedack pending

iirc this is history with the kLIBCum package.

comment:5 Changed 18 months ago by lewisr

Well, actually, this could be fixed a couple of different ways:

SystemGroup in cups-files.conf refers to the group "admin" which does not exist. However, upon opening kLIBCum, I see that we have an "admins" group (plural). Without saving any changes from kLIBCum, but editing cups-files.conf to change SystemGroup from admin to admins, cupsd.exe starts and runs without error.

We should either change the built-in admin group name to "admin" or change the distributed cups-files.conf SystemGroup to "admins" to resolve this.

Do we consider this closed when we can't just install the rpm and start CUPS?

comment:6 Changed 18 months ago by diver

thx for the hint. We are now fixing it in eiter way. Cups or kLIBCum.

comment:7 Changed 18 months ago by herwigb

The issue "admin" versus "admins" was fixed in kLIBCum 1.0.9. It will silently rename any "admins" it find into "admin". For smbusers (where the bug was initially introduced) there will be the same kind of fix.

comment:8 Changed 18 months ago by lewisr

  • Resolution set to fixed
  • Status changed from new to closed

Okay, then, guys. I vote we close this one as fixed at this point.

Note: See TracTickets for help on using tickets.