Note that klog _IS_ a v4 protocol. I don't believe the windows distribution includes a v4 aklog equivalent.
-derek "T. Matthew Cocker" <[EMAIL PROTECTED]> writes: > I am running the same configuration as you by the sound of it and am > not having the same problem. Was the MIT KDC compiled with krb4 > support. My krb5kdc.log shows a v4 request anytime a windows box tries > to get a token via windows klog. What does your log show? > > Cheers > > Matt > > At 06:21 p.m. 16/02/2002 +0100, Andrej Filipcic wrote: > > >I have a question about Windows authorization to afs-krb5 server. If I > >have understood correctly, the token is received through kerberos 4 on > >windows. The linux server runs mit krb5, afs and fakeka ( to enable > >klog). On windows, if I try to obtain a token, a receive one, but it is > >valid until 1/1/1601. The only way to obtain a token is to run MIT krb win32 > >stuff (kinit + aklog). What is the problem with openafs login on windows? > > > >Best regards, > > > >Andrej > > _______________________________________________ > OpenAFS-info mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-info -- Derek Atkins Computer and Internet Security Consultant [EMAIL PROTECTED] www.ihtfp.com _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
