From owner-freebsd-security Wed Jun 30 9:38:52 1999 Delivered-To: freebsd-security@freebsd.org Received: from entic.net (shell.entic.net [209.157.122.66]) by hub.freebsd.org (Postfix) with SMTP id 1A5CC15546 for ; Wed, 30 Jun 1999 09:38:41 -0700 (PDT) (envelope-from aj@entic.net) Received: (qmail 6760 invoked by uid 1000); 30 Jun 1999 16:39:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Jun 1999 16:39:27 -0000 Date: Wed, 30 Jun 1999 09:39:27 -0700 (PDT) From: Anil Jangity To: freebsd-security@freebsd.org Subject: kill!!! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ;-) I was wondering, is it possible/safe to make kill(1) to not allow it to kill a root process run from the console? Only the console should be able to kill those processes and no one else. The reason is, I leave a root login on the console at all times... just incase something stupid happens like the passwd is changed for root or you can no longer su to root etc because of a compromise or whatever, but if you have a logged in root already, it'll be easy to fix those. I was thinking making kill not be able to kill the shell after it was hacked etc. -- Anil Jangity To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message