Bug 26851 - Wrong gid in up2date when called as non-root
Wrong gid in up2date when called as non-root
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: usermode (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jindrich Novy
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-09 14:19 EST by Carlos Fernanez
Modified: 2015-01-07 18:43 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-03 07:31:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Carlos Fernanez 2001-02-09 14:19:23 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)


When up2date is called from a non-root account (and after obviously 
providing the root password), up2date uses the group id from the non-root 
account, or so it seems. I'm assuming this because of the group owning the 
file in /var/spool/up2date.

Reproducible: Always
Steps to Reproduce:
1. up2date from a non-root account
2. skip some packages so they're left in /var/spool/up2date
3. ls /var/spool/2p2date
	

Actual Results:  I got
drwxr-xr-x   12 root     root         4096 Jan 15 08:35 ..
-rw-------    1 root     cfsmp3       7724 Jan 31 05:14 sysklogd-1.3.33-
8.i386.hdr
-rw-------    1 root     cfsmp3      28120 Jan 31 05:14 pam-0.72-
37.i386.hdr
drwxr-xr-x    2 root     root         4096 Jan 31 07:09 .


Expected Results:  drwxr-xr-x   12 root     root         4096 Jan 15 
08:35 ..
-rw-------    1 root     root         7724 Jan 31 05:14 sysklogd-1.3.33-
8.i386.hdr
-rw-------    1 root     root        28120 Jan 31 05:14 pam-0.72-
37.i386.hdr
drwxr-xr-x    2 root     root         4096 Jan 31 07:09 .
Comment 1 Cristian Gafton 2001-02-19 20:34:11 EST
Assigned QA to jturner
Comment 2 Preston Brown 2001-02-20 13:07:55 EST
this was a usermode issue, fixed in rawhide.

Note You need to log in before you can comment on or make changes to this bug.