From owner-freebsd-security Tue Aug 31 23:41: 7 1999 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1787014C0C for ; Tue, 31 Aug 1999 23:41:02 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA10641; Wed, 1 Sep 1999 00:41:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA16059; Wed, 1 Sep 1999 00:40:41 -0600 (MDT) Message-Id: <199909010640.AAA16059@harmony.village.org> To: Frank Tobin Subject: Re: Not sure if you got it... Cc: FreeBSD-security Mailing List In-reply-to: Your message of "Tue, 31 Aug 1999 10:56:40 CDT." References: Date: Wed, 01 Sep 1999 00:40:41 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Frank Tobin writes: : 3) Use chflags -R , followed by rm -rf. This two step : process is consistent with unix philosophy. This is probably the cleanest : (traditionally) solution. However, it causes two disk passes instead of : one. And might also have a race condition in it, since if someone adds a flag after the chflags -R has gone over it, rm will not be able to remove the file. : 4) Use find(1) with -exec chflags and rm. This has the downside of many : processes getting started (one chflags and one rm for each node), and : again, more disk usage (we don't all use SCSI yet). 5) find -delete should take all measures that it can to remove the file. The whole file flags thing was a cool idea, but it is a PITA and likely shouldn't have been implemented the way it was:-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message