From owner-freebsd-questions Wed May 30 16:19:25 2001 Delivered-To: freebsd-questions@freebsd.org Received: from shell1.nominum.com (shell1.nominum.com [204.152.187.163]) by hub.freebsd.org (Postfix) with ESMTP id 920DB37B423 for ; Wed, 30 May 2001 16:19:23 -0700 (PDT) (envelope-from Peter.Losher@nominum.com) Received: from svalbard.nominum.com (svalbard.nominum.com [204.152.187.73]) by shell1.nominum.com (Postfix) with ESMTP id 8320F66B01 for ; Wed, 30 May 2001 16:19:15 -0700 (PDT) Date: Wed, 30 May 2001 16:18:15 -0700 (PDT) From: Peter Losher To: Subject: Odd kpasswd problem in 3.5-STABLE and MIT Krb5. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Here's the situation; I have two FreeBSD 3.5-STABLE servers running MIT Krb5 from ports. From all accounts, it works fine, except for kpasswd. When I originally set up these boxes a couple of years ago, kpasswd worked fine. Then in when I updated the port to 1.1.2, it stopped working. When invoking kpasswd on these boxes, it asks for your old password, then your new passwd, then a re-confirmation. Then it just sits there for a minute and come back with the response: "kpasswd: Operation timed out changing password" I thought perhaps that MIT changed the protocol slightly between versions, thus having to update our KDC as well. Then I installed 4.3-RELEASE on some new boxes, and after installing MIT Krb5 1.2.2 from ports, kpasswd worked fine. I have since updated the Krb5 installs on the 3.5-STABLE boxes to 1.2.2, and kpasswd still times out. I have checked /etc/services and /etc/krb5.conf, and they are exactly the same. Has anyone experienced this and if so, how did they get around it? Best Wishes - Peter Losher -- Peter.Losher@nominum.com - [ Systems Admin. | Nominum, Inc. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message