kerberos password change in master-slave environ

[John Hascall]

> Our KDC implements incremental propogation and provides the
> support for local password changes rather than a password change
> needing to connect to the master - we pass the password change
> request from slave to master(s) when received a nd then the
> master propogates this change back to ALL secondaries along with
> any updates made by administrators on the master. We rarely need
> to propogate the entire database since the slaves and masters are
> always in sync ...

Do you handle the case where a password gets changed
on KDC "a" and before it is replicated it is changed
on KDC "b" too?  If so, how?


John