From owner-freebsd-security Tue Jul 16 07:39:43 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28770 for security-outgoing; Tue, 16 Jul 1996 07:39:43 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA28762; Tue, 16 Jul 1996 07:39:38 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id KAA11124; Tue, 16 Jul 1996 10:39:14 -0400 (EDT) Date: Tue, 16 Jul 1996 10:39:14 -0400 (EDT) From: Brian Tao To: Sean Kelly cc: phk@freebsd.org, freebsd-security@freebsd.org Subject: Re: suidness of /usr/bin/login In-Reply-To: <199607161434.OAA26815@gatekeeper.fsl.noaa.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Jul 1996, Sean Kelly wrote: > > exec /usr/bin/login > > to terminate one login session and start another, on the same tty/pty. > In fact, csh/tcsh has a builtin `login' which does the exec. Other than that, there is no real need for it to be setuid root (since telnetd and getty are both already running as root). I guess this would put it under "setuid root subject to local policy". -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"