Re: today's bugtraq flock issue
From: Crist J. Clark (crist.clark@attbi.com)
Date: 07/19/02
- Next message: Michael Sharp: "chroot"
- Previous message: Chris Knipe: "Re: wierdness in my security report"
- In reply to: Mark Hittinger: "today's bugtraq flock issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 18 Jul 2002 16:01:03 -0700 From: "Crist J. Clark" <crist.clark@attbi.com> To: Mark Hittinger <bugs@pu.net>
On Thu, Jul 18, 2002 at 01:15:52PM -0500, Mark Hittinger wrote:
>
> Just saw the flock issue on bugtraq. This probably needs some discussion.
>
> Should file locking only be permitted on files that are either owned by the
> caller or are writeable to the caller?
Locks are permitted if you can _read_ the file.
# chmod 660 /etc/dumpdates
Will "fix" dump(8).
Not sure where tip(1) might block up if aculog is locked. It doesn't
appear to lock it. aculog is just a log file. I don't see a reason to
block on opening it. Just change that.
-- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
- Next message: Michael Sharp: "chroot"
- Previous message: Chris Knipe: "Re: wierdness in my security report"
- In reply to: Mark Hittinger: "today's bugtraq flock issue"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
