From owner-freebsd-bugs Mon Jul 22 13:49:05 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06697 for bugs-outgoing; Mon, 22 Jul 1996 13:49:05 -0700 (PDT) Received: from kechara.flame.org (kechara.flame.org [192.80.44.209]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06687 for ; Mon, 22 Jul 1996 13:49:02 -0700 (PDT) Received: (from explorer@localhost) by kechara.flame.org (8.7.5/8.6.9) id QAA17958; Mon, 22 Jul 1996 16:47:46 -0400 (EDT) To: "David E. O'Brien" Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/1410: /usr/bin/login is suid, with little requirement for this References: <199607210940.CAA25451@freefall.freebsd.org> From: Michael Graff Date: 22 Jul 1996 16:47:45 -0400 In-Reply-To: "David E. O'Brien"'s message of Sun, 21 Jul 1996 02:40:02 -0700 (PDT) Message-ID: Lines: 15 X-Mailer: Gnus v5.2.36/Emacs 19.31 Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "David E. O'Brien" writes: > > I've found it useful for testing login stuff without risking a hangup. > > Bruce > > Makes sense in your case. But IMHO, that is a special case. And you > could manually make /usr/bin/login suid root on the machines you need > this functionality on. But do you think /usr/bin/login should be suid > root in the general case? I do, yes. IMHO, it should be linked -static, however. All setuid programs should be. --Michael