This is the mail archive of the
mailing list for the Cygwin project.
Re: Packaging Heimdal for Cygwin was Re: Heimdal 1.5.2: "unknown mech-code 2529639054 for mech 1 3 6 1 4 1 311 2 2 10"
- From: Jeffrey Altman <jaltman at openafs dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 24 Jun 2013 07:56:50 -0400
- Subject: Re: Packaging Heimdal for Cygwin was Re: Heimdal 1.5.2: "unknown mech-code 2529639054 for mech 1 3 6 1 4 1 311 2 2 10"
- References: <409A0E510096B044A0EE3778BB3F1F5C01379C903ECD at EXMAIL dot hrl dot com> <51C33835 dot 6000207 at openafs dot org> <409A0E510096B044A0EE3778BB3F1F5C01379C904127 at EXMAIL dot hrl dot com> <51C38880 dot 3090401 at openafs dot org> <20130621074355 dot GE1620 at calimero dot vinschen dot de> <51C45788 dot 7080908 at openafs dot org> <20130621140733 dot GF7362 at calimero dot vinschen dot de> <51C48EE2 dot 1000406 at openafs dot org> <20130624091012 dot GA14319 at calimero dot vinschen dot de>
On 6/24/2013 5:10 AM, Corinna Vinschen wrote:
> On Jun 21 13:35, Jeffrey Altman wrote:
>> Since Cygwin Heimdal is built as Linux without any platform specific
>> credential cache support it will be restricted to using FILE: caches as
>> a ticket store. Microsoft Kerberos never uses FILE: based caches and
>> native MIT and Heimdal distributions use them only when explicitly
>> configured to.
>> The preferred location of a krb5.conf file on Windows is
>> By reading the DOS formatted file stored at that location any configuration
>> applied to native Kerberos library distributions will also be used by
>> Cygwin applications.
> Sorry if I'm dense but what does that mean exactly for Cygwin? Assuming
> the Cygwin heimdal package would use that file location, would it be only
> able to interact correctly with other third part kerberos or heimdal
> packages, or would it also work with the native stuff and AD?
If Cygwin shared that location it would share the configuration for
native MIT and Heimdal Kerberos distributions.
Microsoft's Kerberos SSP is in-kernel and does not use configuration
files. All Microsoft configuration is via Group Policy and Registry
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple