Bug 130222

Summary: Identical UID 100 for users messagabus and stunnel
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Stephan Wefing <wefing>
Component: BasesystemAssignee: Timo Hoenig <thoenig>
Status: VERIFIED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None CC: dkukawka
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Stephan Wefing 2005-10-24 07:01:06 UTC 
After an update from SuSE Prof 9.2 to SuSE Linux 10.0, UID 100 was found to be
assigned to user messagebus (presumably belonging to package dbus) and to user
stunnel. Only package stunnel is currently istalled. As a consequence, the YaST
module "users" aborts with a corresponding error message. These are the
conflicting entries in /etc/passwd:

messagebus:x:100:101:User for D-BUS:/var/run/dbus:/bin/false
stunnel:x:100:65534:Daemon user for stunnel (universal SSL
tunnel):/var/lib/stunnel:/bin/false

In addition, there is no corresponding entry for user messagebus in /etc/shadow.
Comment 1 Dr. Werner Fink 2005-10-24 09:21:01 UTC 
Peter? Timo?
Comment 2 Timo Hoenig 2005-10-24 09:36:47 UTC 
Seems that dbus-1.spec is to blame. It uses -o to add users:
       -o, --non-unique
              Allow duplicate (non-unique) User IDs.

I'll remove this flag from dbus-1.spec.

HAL seems to suffer from the same problem, cc'ing Danny.
Comment 3 Timo Hoenig 2005-10-24 09:39:50 UTC 
Hum. Actually most packages add users with -o. Maybe stunnel needs to add its user with -o, too, rather than dbus-1 without -o ;-)
Comment 5 Peter Poeml 2005-10-24 11:51:43 UTC 
Does -o without -u make any sense?
Comment 6 Thorsten Kukuk 2005-10-24 14:38:50 UTC 
-o is ignored if you use -r at the same time (and don't specify a fix UID).

For me it looks like as if all spec files are ok and this should not have happend.

So, before starting changing spec files, find out why UID 100 was used twice.
Comment 8 Timo Hoenig 2006-12-01 12:06:28 UTC 
Just checked with OS10.2, the issue is fixed.