Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 28 Mar 2001 09:06:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 28 Mar 2001 09:06:27 -0500 Received: from anchor-post-31.mail.demon.net ([194.217.242.89]:55569 "EHLO anchor-post-31.mail.demon.net") by vger.kernel.org with ESMTP id ; Wed, 28 Mar 2001 09:06:08 -0500 Message-ID: Date: Wed, 28 Mar 2001 15:04:46 +0100 To: Walter Hofmann Cc: linux-kernel@vger.kernel.org From: Simon Williams Subject: Re: Disturbing news.. References: <01032806093901.11349@tabby> In-Reply-To: MIME-Version: 1.0 X-Mailer: Turnpike Integrated Version 5.01 S Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 34 In message , Walter Hofmann writes > > >On Wed, 28 Mar 2001, Jesse Pollard wrote: > >> >Any idea? >> >> Sure - very simple. If the execute bit is set on a file, don't allow >> ANY write to the file. This does modify the permission bits slightly >> but I don't think it is an unreasonable thing to have. > >And how exactly does this help? > >fchmod (fd, 0666); >fwrite (fd, ...); >fchmod (fd, 0777); > I think their point was that a program could only change permissions of a file that was owned by the same owner. If a file is owned by a different user & has no write permissions for any user, the program can't modify the file or it's permissions. Sounds like a good plan to me. -- Simon Williams - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/