From owner-freebsd-ports@FreeBSD.ORG Thu Aug 28 17:11:47 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8682016A4BF for ; Thu, 28 Aug 2003 17:11:47 -0700 (PDT) Received: from fire.org.nz (firewall.fire.org.nz [203.97.144.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id F391C43FE9 for ; Thu, 28 Aug 2003 17:11:45 -0700 (PDT) (envelope-from andy@fud.org.nz) Received: by homer.fire.org.nz id <336012>; Fri, 29 Aug 2003 12:11:00 +1200 From: Andrew Thompson To: ports@FreeBSD.org Content-Type: text/plain Message-Id: <03Aug29.121100nzst.336012@homer.fire.org.nz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 29 Aug 2003 12:11:55 +1200 Content-Transfer-Encoding: 7bit Subject: security/pam_smb X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2003 00:11:47 -0000 Hi, I have upgraded pam_smb to v2.0.0-rc5 due to the recent root exploit. It has stopped working with the error: radiusd: unable to resolve symbol: pam_sm_authenticate radiusd: unable to resolve symbol: pam_sm_setcred Strings shows a difference between v1.9.9 and v2 strings pam_smb.1.9.9/work/pam_smb/pamsmbm/pam_smb_auth.so | grep ^pam_ pam_get_user pam_get_item pam_sm_authenticate pam_sm_setcred pam_set_item strings pam_smb/work/pam_smb-2.0.0-rc5/pamsmbm/pam_smb_auth.so | grep ^pam_ pam_get_user pam_get_item pam_set_item Can anyone throw me a bone? Andy