From owner-freebsd-current Mon Jan 14 20:26:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2BB1F37B421 for ; Mon, 14 Jan 2002 20:26:24 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g0F4QMl12729 for ; Mon, 14 Jan 2002 21:26:22 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g0F4QLx78175 for ; Mon, 14 Jan 2002 21:26:21 -0700 (MST) (envelope-from imp@village.org) Date: Mon, 14 Jan 2002 21:26:02 -0700 (MST) Message-Id: <20020114.212602.69432904.imp@village.org> To: current@freebsd.org Subject: sudo redu From: "M. Warner Losh" X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK. This looks like a problem in 1.6.4p1 of sudo. It isn't a problem with 1.6.3p7_2. 1.6.4 works on -stable, but not -current. It apparently added a call to pam_setcred: 453) Now call pam_setcreds() to setup creds for the target user when PAM is in use. On Linux this often sets resource limits. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message