From owner-freebsd-stable Sat Oct 14 9:38: 7 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nxe.de (mail.nxe.de [212.42.225.6]) by hub.freebsd.org (Postfix) with ESMTP id 4498837B671 for ; Sat, 14 Oct 2000 09:38:05 -0700 (PDT) Received: by mail.nxe.de (8.10.2/nora-20000620) for freebsd-stable@freebsd.org (envelope-from nora) id e9EGc3R26167; Sat, 14 Oct 2000 18:38:03 +0200 (CEST) Apparently-To: freebsd-stable@freebsd.org Date: Sat, 14 Oct 2000 18:38:03 +0200 From: Nora Etukudo To: freebsd-stable@freebsd.org Subject: Re: Why cu i suid && sgid Message-ID: <20001014183803.A25616@mail.nxe.de> References: <20001014124428.A7367@genesis.k.pl> <20001014182342.A24430@mail.nxe.de> <20001014182829.B877@genesis.k.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0.1i In-Reply-To: <20001014182829.B877@genesis.k.pl>; from ns88@genesis.k.pl on Sat, Oct 14, 2000 at 06:28:29PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Oct 14, 2000 at 06:28:29PM +0200, Tomasz Paszkowski wrote: > But think about the situation when you have cisco console connected > to the serial port. Everyone can operate on it. Well, the 'cu' command is like many others in your unix -- if not to say most others -- a program of general purpose and intended for the use of several users. In your special case, you may restrict the use of 'cu' but this isn't valid for normal cases. Better is the restriction on the cisco itself. Most cisco's (if not all) can be password protected. Liebe Grüße, Nora. -- nora@sappho-net.de http://www.sappho-net.de/ Lesbian Computer Networks, Finland http://www.sappho.net/ Web for Women (von Frauen, für Frauen) http://www.w4w.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message