Date: Thu, 18 Jul 2002 13:15:52 -0500 (CDT) From: Mark Hittinger <bugs@pu.net> To: freebsd-security@freebsd.org Subject: today's bugtraq flock issue Message-ID: <200207181815.g6IIFqBs011069@ns1.pu.net>
next in thread | raw e-mail | index | archive | help
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? What will break if software can't lock files that aren't writeable or belong to someone else? The only problem I can see is performance. I don't think we want to have more overhead during each lock call as this will hurt database speed. Could we have the kernel decide on "lockability" during the open call and keep track of that state? Subsequent lock calls on that fd would then be permitted or denied based on "lockability". Later Mark Hittinger bugs@pu.net 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?200207181815.g6IIFqBs011069>