From owner-freebsd-questions Tue Aug 6 13:56:16 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22314 for questions-outgoing; Tue, 6 Aug 1996 13:56:16 -0700 (PDT) Received: from cs.montana.edu (fubar.cs.montana.edu [153.90.192.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA22297 for ; Tue, 6 Aug 1996 13:56:11 -0700 (PDT) Received: by cs.montana.edu; id AA08590; Tue, 6 Aug 1996 14:55:40 -0600 Date: Tue, 6 Aug 1996 14:55:39 -0600 (MDT) From: Justin Ashworth To: John Clark Cc: questions@freebsd.org Subject: Re: blocking 'WHAT' in 'w' listing In-Reply-To: <2.2.32.19960806150432.0099e604@netview.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 6 Aug 1996, John Clark wrote: > Justin, > > >You're right, it would provide privacy, but who's going to stop > >somebody from doing a 'ps -U ' to find out what they're running? > > Same code in both ps & w, right? I don't know for sure, but that's a good point. If I were real concerned about it, I'd write a small program that filters it out of both of those commands. Hardcode the executable to execute ps and w, which may be hidden as .ps and .w in some obscure directory. It's kind of an ugly workaround, but I doubt that disabling it is built into the code. Actually, now that I think about it, grab 'ps' and 'w' out of the source tree and just compile them without those options. That would mean chopping a simple 'cout' or 'printf' command in 'w' and a few lines that look like they cater to the '-U' option in 'ps'. Go with my second suggestion. I got carried away with that first one before I realized the obvious best solution. - Justin J. Ashworth -- CS Student - Montana State University --- Chair, Association for Computing Machinery - MSU -- ashworth@cs.montana.edu - http://www.cs.montana.edu/~ashworth