Natalie Li wrote:
> ...
>>
>>> ----------------------
>>>
>>> + printf "%s" $newpw | $KSETPW -n -s $salt -v $kvno -k
>>> "$new_keytab" "${ar...@]}" HOST/${fq...@${realm} > /dev/null 2>&1
>>> + if [[ $? -ne 0 ]]
>>> + then
>>> + printf "$(gettext "Failed to set account
>>> password").\n"
>>> + error_message
>>> + fi
>>> +
>>>
>>> This is a workaround for the following CR:
>>>
>>> 6824434 P3 kerberosv5_b/applications Unable to accept context
>>> establishment initiated by Windows 2000 clients
>>>
>>> If your team plans to fix the above CR by modifying mech_krb5 to
>>> perform case-insensitive lookup in the near future, it'd be better
>>> not to push this workaround along with the fixes for 6405422 & 6817447.
>>
>> There is conflicting information regarding service components; some
>> implementors say that it should be case sensitive in theory, but have
>> conceded that they treat this component case insensitive. I had to
>> make a judgment call and preserve the case sensitivity as it might
>> mean different things to other implementors or in the future. As a
>> result, adding both a "host" and "HOST" entries avoids case
>> insensitivity.
> So, you might want to push your changes as a fix for the above CR
> (i.e. 6824434) as well.
Yes, good idea. I'll take ownership of this shortly and update the
delta comments in my ws.
Thanks,
Shawn.
--
