From owner-freebsd-security Mon Jun 3 08:18:50 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22967 for security-outgoing; Mon, 3 Jun 1996 08:18:50 -0700 (PDT) Received: from epprod.elsevier.co.uk (epprod.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22962 for ; Mon, 3 Jun 1996 08:18:42 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by epprod.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id QAA10834 for ; Mon, 3 Jun 1996 16:16:47 +0100 Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Mon, 3 Jun 1996 16:17:05 +0100 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id QAA03397; Mon, 3 Jun 1996 16:15:57 +0100 Date: Mon, 3 Jun 1996 16:15:57 +0100 Message-Id: <199606031515.QAA03397@cadair.elsevier.co.uk> To: bde@zeta.org.au CC: coredump@nervosa.com, freebsd-security@FreeBSD.org In-reply-to: <199606021959.FAA04887@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 3 Jun 1996 05:59:38 +1000) Subject: Re: [linux-security] ext2fs file attributes -- denial-of-service attack (fwd) From: Paul Richards X-Attribution: Paul X-Mailer: GNU Emacs [19.30.1], RMAIL, Mailcrypt [3.3] Reply-to: p.richards@elsevier.co.uk Sender: owner-security@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Bruce" == Bruce Evans writes: Bruce> Root had better know how to clear flags using chflags -R. Bruce> FreeBSD's `rm' has been hacked to unconditionally turn off the Bruce> user append and immutable flags before attempting removals. Bruce> 4.4Lite2's rm still fails to remove user-append/immutable Bruce> files. This doesn't make sense. What's the point of setting the immutable flag on something like the kernel if 'rm' has been hacked to disable it? The normal file permissions would prevent ordinary users from deleting it and the one reason I'd want to set the immutable flag would be to stop me as root doing something stupid to it.