Date: Thu, 18 Jul 2002 16:01:03 -0700 From: "Crist J. Clark" <crist.clark@attbi.com> To: Mark Hittinger <bugs@pu.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: today's bugtraq flock issue Message-ID: <20020718230103.GC31150@blossom.cjclark.org> In-Reply-To: <200207181815.g6IIFqBs011069@ns1.pu.net> References: <200207181815.g6IIFqBs011069@ns1.pu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020718230103.GC31150>