Bug 258461 - sm-notify can't drop root privileges
Summary: sm-notify can't drop root privileges
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 7
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-08-27 23:45 UTC by David K. Means
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version: 1.1.0-4.fc7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-29 19:02:25 UTC
Type: ---


Attachments (Terms of Use)

Description David K. Means 2007-08-27 23:45:12 UTC
sm-notify (a part of nfs-utils), installed version 1.1.0.3-fc7
complains (in /var/log/messages) that it is running as root, and
suggests that I change the owner of /var/lib/nfs/sm, so that it can
drop its privileges to match those of the directories it should write into.

Unfortunately, fc7 does not create this directory; instead, it creates
  /var/lib/nfs/statd/sm  and /var/lib/nfs/statd/sm.bak, and sets the
owner of statd and its subdirectories to "rpcuser", which looks right.

Is this just a version mismatch, or a more serious "out-of-sync" problem
with the nfs-utils?  I have not investigated, but the documentation says that
rpc.statd writes into these directories, and sm-notify reads and updates the
contents.  Surely, they ought to both be working from the same data.

How reproducible:
  on every boot

Comment 1 Steve Dickson 2007-09-14 18:15:38 UTC
Its a bug and is fixed in nfs-utils-1.1.0-4.fc7

Comment 2 Fedora Update System 2007-09-18 22:31:19 UTC
nfs-utils-1.1.0-4.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.

Comment 3 Fedora Update System 2007-10-29 19:02:23 UTC
nfs-utils-1.1.0-4.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.


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