1@c $Id: migration.texi 9718 2001-02-24 05:09:24Z assar $ 2 3@node Migration, Acknowledgments, Programming with Kerberos, Top 4@chapter Migration 5 6@section General issues 7 8When migrating from a Kerberos 4 KDC. 9 10@section Order in what to do things: 11 12@itemize @bullet 13 14@item Convert the database, check all principals that hprop complains 15about. 16 17@samp{hprop -n --source=<NNN>| hpropd -n} 18 19Replace <NNN> with whatever source you have, like krb4-db or krb4-dump. 20 21@item Run a Kerberos 5 slave for a while. 22 23@c XXX Add you slave first to your kdc list in you kdc. 24 25@item Figure out if it does everything you want it to. 26 27Make sure that all things that you use works for you. 28 29@item Let a small number of controlled users use Kerberos 5 tools. 30 31Find a sample population of your users and check what programs they use, 32you can also check the kdc-log to check what ticket are checked out. 33 34@item Burn the bridge and change the master. 35@item Let all users use the Kerberos 5 tools by default. 36@item Turn off services that do not need Kerberos 4 authentication. 37 38Things that might be hard to get away is old programs with support for 39Kerberos 4. Example applications are old Eudora installations using 40KPOP, and Zephyr. Eudora can use the Kerberos 4 kerberos in the Heimdal 41kdc. 42 43@end itemize 44