From owner-freebsd-questions@FreeBSD.ORG Mon Jun 4 02:38:06 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 606DF16A468 for ; Mon, 4 Jun 2007 02:38:06 +0000 (UTC) (envelope-from hunteke@earlham.edu) Received: from sipala.earlham.edu (sipala.earlham.edu [159.28.1.75]) by mx1.freebsd.org (Postfix) with ESMTP id 1EAFA13C469 for ; Mon, 4 Jun 2007 02:38:05 +0000 (UTC) (envelope-from hunteke@earlham.edu) Received: from [192.168.1.107] (adsl-76-214-114-198.dsl.ipltin.sbcglobal.net [76.214.114.198]) (authenticated bits=0) by sipala.earlham.edu (8.13.6/8.13.6) with ESMTP id l542c0TK010098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 3 Jun 2007 22:38:00 -0400 (EDT) X-Authentication-Warning: sipala.earlham.edu: Host adsl-76-214-114-198.dsl.ipltin.sbcglobal.net [76.214.114.198] claimed to be [192.168.1.107] Message-ID: <46637B07.6050705@earlham.edu> Date: Sun, 03 Jun 2007 22:37:59 -0400 From: Kevin Hunter User-Agent: Thunderbird 1.5.0.7 (X11/20060909) MIME-Version: 1.0 To: VeeJay References: <2cd0a0da0706020638g48b7ac7fn946c6e3caddc0663@mail.gmail.com> <466199E5.3040005@vindaloo.com> <4661B6E0.803@earlham.edu> <2cd0a0da0706030142l1fd30d74yc443e132337daf37@mail.gmail.com> In-Reply-To: <2cd0a0da0706030142l1fd30d74yc443e132337daf37@mail.gmail.com> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Questions Subject: Re: How to disable command prompt history? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2007 02:38:06 -0000 At 4:42a -0400 on 03 Jun 2007, VeeJay wrote: > Actually, it was for the security reason that if somebody breaks in the > server then he/she doesn't see what commands are being executed, etc, > etc.... > > and I am using /bin/sh > > any more comments? I don't use /bin/sh on a regular basis (bash, for better or worse) so I can't help you. >From a security standpoint, I'm more wondering what makes you so worried that someone will break in? Would some suggestions from the community about securing your system be helpful? (I'm no security guru so don't ask me . . . 8-< ) Also, why are you worried about them seeing what commands you've been running? My first thought is that at the point a malicious someone has broken into your system, you have (much) bigger things to worry about. But, to dumbly answer your question, see if sh looks for ~/.logout. If it does, have it remove ~/.history and clear the screen. Or, if the order of that doesn't work (if .logout is read /before/ .history is written), 'chmod 000 .history'. Best of luck, Kevin