Why use krb5_set_real_time() instead of NTP ?

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan (metze) Metzmacher wrote:

> When windows gets the CLOCK_SKEW error to a kdc request it 
> uses the time field in the error response and then retries
> the request. It also looks at the error string fieled in
> this case, I assume the NTSTATUS code should be in there
> to make this work.
> 
> I fixed this against samba4 by sending no error string 
> at all, at the windows clients are happy to retry
> against samba4 now too.

Thanks Metze.  That makes sense now.  If we controlled the krb5
stack in Samba 3 more, I would try this.  Maybe some time
in the future.




cheers, jerry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEYfybIR7qMdg1EfYRAnY7AJ9jHHMCyQQarXzenEDsTeSkW42sSwCfbp3z
jIdwG1/RnCcCFhROwvr6M+c=
=nIQF
-----END PGP SIGNATURE-----