From owner-freebsd-security Tue Aug 31 13: 8:33 1999 Delivered-To: freebsd-security@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 0501114C1C for ; Tue, 31 Aug 1999 13:08:29 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id NAA72350; Tue, 31 Aug 1999 13:07:43 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199908312007.NAA72350@gndrsh.dnsmgr.net> Subject: Re: Not sure if you got it... In-Reply-To: <199908311450.IAA11239@harmony.village.org> from Warner Losh at "Aug 31, 1999 08:50:15 am" To: imp@village.org (Warner Losh) Date: Tue, 31 Aug 1999 13:07:43 -0700 (PDT) Cc: bde@zeta.org.au (Bruce Evans), dynamo@ime.net, security@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In message <199908310720.AAA68164@gndrsh.dnsmgr.net> "Rodney W. Grimes" writes: > : Actually I think that was done on purpose. Since UF_NOUNLINK is to > : protect the user from removing the file it would kinda make since > : that rm -rf should bitch loudly when asked to rm a UF_NOUNLINK flagged > : file shouldn't it? > : > : IMHO, rm should not know about flags at all. chflags knows about flags, > : and if we ever get acl's rm should not be tought about them either, > : some other command (acl(1) anyone) will know how to deal with them. > > Yes, but if force doesn't mean try your best to delete it, then it is > kinda useless... Ahhh.. you said it not me... one more misconceived and not easily correctly implemented option. > There are times that policy is to kill everything, > flags to the contrary non-with-standing. Unix commands should not implement policy, only methods. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message