From owner-freebsd-stable@FreeBSD.ORG Wed Dec 17 04:22:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0325D1065677 for ; Wed, 17 Dec 2008 04:22:31 +0000 (UTC) (envelope-from jcw@highperformance.net) Received: from mx1.highperformance.net (s6.stradamotorsports.com [64.81.163.124]) by mx1.freebsd.org (Postfix) with ESMTP id C663A8FC1E for ; Wed, 17 Dec 2008 04:22:30 +0000 (UTC) (envelope-from jcw@highperformance.net) Received: from [192.168.1.17] ([192.168.1.17]) by mx1.highperformance.net (8.14.3/8.14.3) with ESMTP id mBH45T70081309 for ; Tue, 16 Dec 2008 20:05:30 -0800 (PST) (envelope-from jcw@highperformance.net) Message-ID: <49487A89.80608@highperformance.net> Date: Tue, 16 Dec 2008 20:05:29 -0800 From: "Jason C. Wells" User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: freebsd-stable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=2.5 tests=ALL_TRUSTED autolearn=failed version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on s4.stradamotorsports.com Subject: Heimdal Breakage X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2008 04:22:31 -0000 After installing 6.4-RELEASE on my secondary KDC I decided to test the secondary KDC. When trying kinit I get this error: jcw@w17 ~ $ kinit jcw@STRADAMOTORSPORTS.COM's Password: kinit: krb5_get_init_creds: Key size is incompatible with encryption type One post on the net says that Heimdal changed the key format to add some padding or somesuch. I haven't gone about fixing the problem yet so maybe that post is not applicable to FreeBSD. Just the same I thought I would let folks know that their key databases are probably not forward compatible with 6.4-RELEASE. This would be a pretty big deal for some users. It would be nice to see this in UPDATING. Thanks, Jason