From owner-cvs-all Wed Nov 13 10:12:24 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94F5437B404; Wed, 13 Nov 2002 10:12:23 -0800 (PST) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB3DB43E75; Wed, 13 Nov 2002 10:12:22 -0800 (PST) (envelope-from nectar@nectar.cc) Received: from madman.nectar.cc (madman.nectar.cc [10.0.1.111]) by gw.nectar.cc (Postfix) with ESMTP id 76D9B10; Wed, 13 Nov 2002 12:12:22 -0600 (CST) Received: by madman.nectar.cc (Postfix, from userid 1001) id 3ECE8137BDD; Wed, 13 Nov 2002 12:12:22 -0600 (CST) Date: Wed, 13 Nov 2002 12:12:22 -0600 From: "Jacques A. Vidrine" To: Robert Watson Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libpam/modules/pam_krb5 pam_krb5.c Message-ID: <20021113181222.GC28901@madman.nectar.cc> Mail-Followup-To: "Jacques A. Vidrine" , Robert Watson , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org References: <200211131746.gADHkF68049244@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 13, 2002 at 01:04:26PM -0500, Robert Watson wrote: > Does this fix the 5.0 interaction problems with Kerberos5 PAM, or are > there still issues left? I've been setting up a box locally to see if I > could figure out the problems, but I can give up if you think things re > fixed :-). I believe it fixes it. It now works here locally on a recent -CURRENT with /usr/bin/login and /usr/sbin/sshd. It definitely did not work before... it would crash due to the phkmalloc memory scrubbing. I will be happy to follow-up any issues that might still exist as they are reported. The pam_krb5 from ports never had this problem due to sheer luck. The way it allocates a new krb5_ccache results in no sharing of data members with the krb5_context. Cheers, -- Jacques A. Vidrine http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos jvidrine@verio.net . nectar@FreeBSD.org . nectar@kth.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message