From owner-freebsd-current  Thu Jan 27 18:24: 2 2000
Delivered-To: freebsd-current@freebsd.org
Received: from iris.vsrc.uab.edu (iris.vsrc.uab.edu [138.26.156.231])
	by hub.freebsd.org (Postfix) with ESMTP id 3B79E1599A
	for <freebsd-current@freebsd.org>; Thu, 27 Jan 2000 18:23:59 -0800 (PST)
	(envelope-from emre@iris.vsrc.uab.edu)
Received: by iris.vsrc.uab.edu (Postfix, from userid 1001)
	id B0EFD1250B; Thu, 27 Jan 2000 20:24:54 +0000 (GMT)
Date: Thu, 27 Jan 2000 20:24:54 +0000
From: Emre <emre@iris.vsrc.uab.edu>
To: Dan Nelson <dnelson@emsphone.com>
Cc: freebsd-current@freebsd.org
Subject: Re: .bash_history and permissions
Message-ID: <20000127202454.A12343@iris.vsrc.uab.edu>
References: <20000127155328.A32492@iris.vsrc.uab.edu> <20000127172415.A19202@dan.emsphone.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <20000127172415.A19202@dan.emsphone.com>; from dnelson@emsphone.com on Thu, Jan 27, 2000 at 05:24:16PM -0600
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Jan 27, 2000 at 05:24:16PM -0600, Dan Nelson wrote:
> Delete permission comes from the directory, not the file.  No amount of
> chmod'ing the file will affect it.

Hmm, so If I took out write permission for the directory, the user wouldn't
be able to delete his .bash_history, correct? (or any file inside it for
that matter)
 
> Under FreeBSD, you can run "chflags sappnd,sunlnk .bash_history" to
> make the file undeletable, append-only.   Under other Unixes, the user
> can simply do a "cp /dev/null ~/.bash_history && kill -9 $$" to log out
> with no history file.

Thanks, the chflags method worked for me...

-- 
DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE  


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