[OpenAFS] 1.3.71 for Windows questions/problems

[Robbie Foust]

Ok, the "aklog -4" seems to have done the trick.  Thanks for the help!

I do have another question though.  The aklog that comes with KFW 2.6.4 
works, but if I use the one that comes with OpenAFS 1.3.71, then no 
matter what arguments I give it (even a -?), I get a windows pop-up 
error that says "The procedure entry point krb5_524_convert_creds could 
not be located in the dynamic link library krb5_32.dll"

I was looking back through previous posts on the list to see if this had 
already been covered and saw where you had mentioned that aklog would be 
removed from the next version of KFW, but that's the one which seems to 
be working for me at the moment.

Thanks again for your help,

- Robbie



Jeffrey Altman wrote:

>
> ms2mit   = copy kerberos 5 tickets from MS credentials cache to the
>            default MIT credentials cache
>
> k524init = use Kerberos 5 TGT to obtain a Kerberos 4 TGT
>
> aklog    = use a Kerberos 5 TGT to obtain a Kerberos 5 afs service
>            ticket and repackage the Kerberos 5 ticket as an afs 2b token
>
> aklog -4 = use a Kerberos 4 TGT to obtain a Kerberos 4 afs service
>            ticket and repackage the Kerberos 4 ticket as an afs token
>
> You do not need to upgrade all of your clients when you upgrade your
> servers.  You should upgrade your servers first and then your clients.
>
>
> Jeffrey Altman
>
>
>
> Robbie Foust wrote:
>
>> How does the AFS client determine if KFW is installed/running or 
>> not?  Is there some type of configurable option to force production 
>> of Kerberos 4 tickets within the tokens when running aklog, even if 
>> Kerberos 5 tickets are available?
>>
>> I need to be able to use ms2mit, k524init, and aklog from the KFW 
>> package for seamless logins.  Unfortunately, we aren't able to 
>> upgrade our db servers at this time because if our understanding is 
>> correct, we must upgrade all file servers too, and then all clients, 
>> and we still need to access other cells outside of our control which 
>> are still using older AFS builds and don't support Kerberos 5.
>>
>> Thanks,
>>
>> - Robbie
>>

-- 
Robbie Foust, IT Analyst
OIT - Administrative Information Support
Duke University