From owner-freebsd-security@FreeBSD.ORG  Wed May 14 08:04:20 2003
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
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 7831637B401
	for <freebsd-security@freebsd.org>;
	Wed, 14 May 2003 08:04:20 -0700 (PDT)
Received: from computinginnovations.com (dsl081-142-072.chi1.dsl.speakeasy.net
	[64.81.142.72])	by mx1.FreeBSD.org (Postfix) with ESMTP id 7CAE043FB1
	for <freebsd-security@freebsd.org>;
	Wed, 14 May 2003 08:04:19 -0700 (PDT)
	(envelope-from derek@computinginnovations.com)
Received: from p4.computinginnovations.com
	(dhcp-192-168-1-121.computinginnovations.com [192.168.1.121])
	h4EF4Ivp077727	for <freebsd-security@freebsd.org>;
	Wed, 14 May 2003 10:04:18 -0500 (CDT)
Message-Id: <5.2.1.1.2.20030514095822.00a800c0@computinginnovations.com>
X-Sender: derek@computinginnovations.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Wed, 14 May 2003 10:04:19 -0500
To: freebsd-security@freebsd.org
From: Derek Ragona <derek@computinginnovations.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: 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]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2003 15:04:20 -0000

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




         -Derek
         derek@computinginnovations.com