Re: Difference in handling SPNEGO tokens between heimdal 0.7.2 , 0.8.1 and 1.0.1

["Markus Moeller" <huaraz@moeller.plus.com>]

Thank you.
Markus

BTW Would the cross realm have worked with a Heimdal kdc instead of MIT ?



"Love Hörnquist Åstrand" <lha@kth.se> wrote in message 
03A7ED3C-357C-402A-AB68-BA564F407F9F@kth.se">news:03A7ED3C-357C-402A-AB68-BA564F407F9F@kth.se...
> Hello Markus,
>
> I added an option to trunk to disable the PAC check, but since my  change 
> require ABI change I've not pulled it up to the release branch.
>
> [libdefaults]
> check_pac = no
>
> Love
>
>
>
> 7 dec 2007 kl. 14.51 skrev Markus Moeller:
>
>> A small update on this:
>>
>> The environment is based on a cross-realm between a w2k3 kdc and a  MIT 
>> kdc.
>> Clients are in w2k3 and the HTTP service principal on MIT.  (sorry for
>> missing out on this details)
>>
>> The issue I experience seems to be related to the crosss realm setup  and 
>> how
>> MIT treats the pac data.
>>
>> Markus
>>
>> "Markus Moeller" <huaraz@moeller.plus.com> wrote in message
>> news:fh08tb$qk5$1@ger.gmane.org...
>>> I used mod_spnego for some time successfully with heimdall 0.7.2.  After
>>> upgrading to heimdal 1.0.1 I get the following error:
>>>
>>> [Thu Nov 08 23:31:04 2007] [error] [client 192.168.1.10] mod_spnego:
>>> gss_accept_sec_context failed; GSS-API: continuation call to routine
>>> required)
>>> [Thu Nov 08 23:31:04 2007] [error] [client 192.168.1.10] mod_spnego:
>>> gss_accept_sec_context failed; GSS-API mechanism: unknown mech-code  0 
>>> for
>>> mech unknown)
>>>
>>>
>>> Why does gss_accept_sec_context  now require a continuation ?
>>>
>>> Markus
>>>
>>>
>>>
>>>
>>
>>
>>
>
>