From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 30 10:03:56 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D4D316A49E for ; Mon, 30 Oct 2006 10:03:56 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from cydem.org (S0106000103ce4c9c.vc.shawcable.net [24.87.27.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF4FC43D82 for ; Mon, 30 Oct 2006 10:03:53 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from soralx.cydem.org (unknown [192.168.0.249]) by cydem.org (Postfix/FreeBSD) with ESMTP id 0DECE90FD6 for ; Mon, 30 Oct 2006 02:03:52 -0800 (PST) Date: Mon, 30 Oct 2006 02:03:50 -0800 From: To: freebsd-hackers@freebsd.org Message-ID: <20061030020350.4d58e461@soralx.cydem.org> In-Reply-To: <20061030103212.13e6ad07@loki.starkstrom.lan> References: <20061029222847.GA68272@marvin.astase.com> <20061030003628.42bc5f8d@loki.starkstrom.lan> <45455f6a.yNcc0kkyEKpoRv3m%perryh@pluto.rain.com> <20061030083849.GB871@turion.vk2pj.dyndns.org> <20061030103212.13e6ad07@loki.starkstrom.lan> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [patch] rm can have undesired side-effects X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 10:03:56 -0000 > > protections at a later date. Unless Alice notices that her file > > has a second link before she deletes it, when she issues "rm -P", > > she will lose her link to the file (and her only way of uniquely > > identifying it) whilst leaving the remaining link to the file in > > Mallory's control. well, that's the whole point of '-P' -- erase file's data _before_ unlinking the file, is it not? > That isn't really that nice, true. But why can i link files that I > have no business with in the first place? Is there is specific reason? if you can't see the contents of other user's directory (think '0750') you really will get no buisiness there, whether you want it or not Of course, one must be careful when using `rm -P` (which, ironically, is very likely to happen in limited-time situations), and even the protection of requiring the '-f' flag if {(inode count) > 1} is inadequate protection for fools like me (who are used to good ol' `rm -rf` on large directory structures) ;P [SorAlx] ridin' VN1500-B2