expert install user not a sudoer if root password given

[stestagg]

So I installed 6.06 beta in windows XP SP2(Athlon 2400, 512mb ram, 8GB virtual SCSI Drive) using VMWare server E.X.P using the i386 ISO (not the live-cd one). I chose expert mode and everything went smoothly until I was told to login using the OEM user and execute: sudo oem-config-prepare, but the oem user wasn't in /etc/sudoers. It would make sense to add a group to /etc/sudoers of which, oem was a member, this would make installation more logical.

Stephen.

[Alex (alexcastan)]

It happens the same to me.

Dapper 6.06 beta2 i386 expert install is not working (well, sudo is not working).

I do an expert install on a PC. at installation time I give root password 'aaa', and create normal user account named 'acastan' with password 'bbb'.

/etc/sudoers and /etc/group files are misconfigured.

not "%admin " line in /etc/sudoers
not "admin" group in /etc/groups

this is the /etc/sudoers in the expert installation (see no "%admin" line at the end of the file):

-------------------

# /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
# Host alias specification

# User alias specification

# Cmnd alias specification

# Defaults

Defaults !lecture,tty_tickets,!fqdn

# User privilege specification
root ALL=(ALL) ALL

-------------------

root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:acastan
tty:x:5:
disk:x:6:
lp:x:7:cupsys
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:cupsys,acastan
fax:x:21:
voice:x:22:
cdrom:x:24:haldaemon,acastan
floppy:x:25:haldaemon,acastan
tape:x:26:
sudo:x:27:
audio:x:29:acastan
dip:x:30:acastan
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:acastan
sasl:x:45:
plugdev:x:46:haldaemon,acastan
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
dhcp:x:101:
syslog:x:102:
klog:x:103:
crontab:x:104:
ssh:x:105:
lpadmin:x:106:acastan
messagebus:x:107:
haldaemon:x:108:
slocate:x:109:
scanner:x:110:cupsys,acastan
gdm:x:111:
acastan:x:1000:

[Pete Savage (petesavage)]

This has been brought up as a bug several times but has been listed as the intentional actions for the package

[stestagg (stestagg)]

It means that the install is broken.
During install, instructions are given onscreen of actions that should be carried out during the OEM configuration phase. These actions don't work if followed because of this 'intentional' feature of the package.
So either there is a bug in the sudo package OR a mistake in the install instructions.

I don't see why the OEM user can't be added to the sudoers list and then removed by oem-config-prepare. There isn't a security issue and it can't be hard to write a script to remove them from the sudoers file.

[Colin Watson (cjwatson)]

Pete should not have closed this bug.

[Pete Savage (petesavage)]

Apologies

[Chris Moore (dooglus)]

/var/lib/dpkg/info/passwd.config includes these lines:

    if ! root_password; then
     sudoers_admin_group
     addgroup --system admin >/dev/null 2>&1 || true
     adduser "$USER" admin >/dev/null 2>&1 || true
    fi

basically, if you've set a root password, then it won't make the 'admin' group, or allow the admin group to use sudo to become root.

This in turn makes the GNOME menu entries for 'synaptic' and other admin programs not work, since they use 'gksudo'.

Do you have references for the other bugs where this has been brought up? This bug should be marked as a duplicate of them.

[Colin Watson (cjwatson)]

/var/lib/dpkg/info/passwd.config is no longer used in Dapper; the corresponding code is in user-setup.

Please do not mark this bug as a duplicate of any other bug; it is already a duplicate of bug 16139.

[Colin Watson (cjwatson)]

Oh, sigh, you actually just marked this bug as a duplicate of bug 16139. I'd prefer it to stay separate, as it's now a clean bug documenting just the issue that the expert user isn't a sudoer if the root password is given, rather than a grab-bag of other partially-fixed issues.

[Alex Mauer (hawke)]

This bug also occurs if you don't actually create an initial user during the expert install -- the admin group is not created, and not given sudo access.