From owner-freebsd-security  Sun Aug 29 20: 8:24 1999
Delivered-To: freebsd-security@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 55F1F14D23
	for <security@FreeBSD.ORG>; Sun, 29 Aug 1999 20:08:20 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA06836;
	Mon, 30 Aug 1999 13:07:57 +1000
Date: Mon, 30 Aug 1999 13:07:57 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199908300307.NAA06836@godzilla.zeta.org.au>
To: bde@zeta.org.au, imp@village.org
Subject: Re: Not sure if you got it...
Cc: dynamo@ime.net, security@FreeBSD.ORG
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>Is there a better way to turn off all the user flags then?

Turning them all off works of course:

    chflags dump,noopaque,nouappnd,nochg,nouunlnk

Is this better :-)?  It's not future-proof.  I'd prefer `chflags nouflags'.

cheflags.3 misdescribes the nodump flag.  It says that `dump' sets the
dump flag.  It doesn't say that users can set it.  It gives the worst
possible example for the use of `no' before a flag by giving `nodump'
as an example of turning off a flag.  Actually, `dump' clears the nodump
flag and `nodump' sets the nodump flag.

The `opaque' flag is not mentioned in chflags.3.

These bugs are fixed in Lite2.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message