From owner-freebsd-security@FreeBSD.ORG Wed May 14 08:34:53 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2C7037B401 for ; Wed, 14 May 2003 08:34:52 -0700 (PDT) Received: from cthulu.compt.com (cthulu.compt.com [209.115.146.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BD7C43F93 for ; Wed, 14 May 2003 08:34:52 -0700 (PDT) (envelope-from tkonefal@compt.com) Message-ID: <3EC26221.9070201@compt.com> Date: Wed, 14 May 2003 11:34:57 -0400 From: tomasz konefal MIME-Version: 1.0 To: freebsd-security@freebsd.org References: <5.2.1.1.2.20030514095822.00a800c0@computinginnovations.com> In-Reply-To: <5.2.1.1.2.20030514095822.00a800c0@computinginnovations.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 17 May 2003 08:10:19 -0700 Subject: Re: su-ing error with FreeBSD 5.0 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 May 2003 15:34:53 -0000 Derek Ragona wrote: > On a couple servers I have one running 5.0 Release, another running 5.0 > Stable I have a problem with su. > > If I login to the server using a regular account, then su - to root, > then I try to su - to any other account, other than the one I originally > logged in as the su works but with this error: > > su: No controlling tty (open /dev/tty: Permission denied) > su: warning: won't have full job control > > With this error, it makes it pretty bad to use this way. > > Do I have something not configured correctly? Or is there something I > need to do more in the 5.0 configuration from: http://www.freebsd.org/releases/5.0R/errata.html --snip-- /dev/tty Permissions FreeBSD 5.0-RELEASE has a minor bug in how the permissions of /dev/tty are handled. This can be triggered by logging in as a non-root, non-tty group user, and using su(1) to switch to a second non-root, non-tty group user. ssh(1) will fail because it cannot open /dev/tty. This bug has been fixed in 5.0-CURRENT. --snip-- this sounds similar to what you are experiencing. might want to check into 5.0-CURRENT. cheers, twkonefal -- Tomasz Konefal Systems Administrator Command Post and Transfer Corp. 416-585-9995 x.349