Received: from jalapeno.cc.columbia.edu (IDENT:cu41754@jalapeno.cc.columbia.edu [128.59.59.238]) by krbdev.mit.edu (8.9.3) with ESMTP id OAA21181; Tue, 10 Jun 2003 14:24:35 -0400 (EDT) Received: from columbia.edu (iam-82.iamx.com [166.84.156.82]) (user=jaltman mech=PLAIN bits=0) by jalapeno.cc.columbia.edu (8.12.8p1/8.12.8) with ESMTP id h5AIOVDH001853 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Jun 2003 14:24:33 -0400 (EDT) Message-Id: <3EE62263.3020801@columbia.edu> Date: Tue, 10 Jun 2003 11:24:35 -0700 From: "Jeffrey Altman [Kermit Project]" Organization: The Kermit Project at Columbia University in the City of New York User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030525 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Hartman Cc: rt-comment@krbdev.mit.edu, jaltman@mit.edu, krb5-prs@mit.edu Subject: Re: [krbdev.mit.edu #1586]krb4 credentails structures References: <3EE6169B.40405@columbia.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-No-Spam-Score: Local X-Scanned-BY: MIMEDefang 2.32 (www . roaringpenguin . com / mimedefang) RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 1514 I am still investigating the problem. The problem is not really caused by the fact the CREDENTIALS definition is different in KRB5_32.DLL or KRB4_32.DLL. The problem is that building Leash has a conflict with attempting to bring in the correct header file since they have the same names. I am still not sure whether or not that is the problem. I am still investigating. Sam Hartman wrote: >>>>>>"Jeffrey" == Jeffrey Altman [Kermit Project] writes: > > > Jeffrey> How would it break the ABI? The changes are Windows > Jeffrey> only. The Krb5 Krb4 library is not supported (nor > Jeffrey> shipped) on Windows at the present time. > > > It's a little unclear to mea how much the krb5 krb4 library is or is > not supported on Windows. You yourself said that you had implemented > support for this library in Kermit because people were using it. > > KFW does not ship this library, but the krb5 sources do support > building outside the KFW framework on Windows and in that > configuration do build the library. > > > When we contemplated the krb524 change, you were asked to review > whether the difference in the credential structure would be a problem. > You said that because the KFW krb4 library had a larger credentials > structure and that because it was allocated by the caller, no problem > would result. > > The fact that we were concerned about the difference in the > credentials structure suggests to me that we are at least reluctant to > change it for 1.3.