Migration
*********

Migration from MIT Kerberos to Heimdal
======================================

hpropd can read MIT Kerberos dump, the format is the same as used in mit-kerberos 1.0b7, and to dump that format use the following command: kdb5_util dump -b7.

To load the MIT Kerberos dump file, use the following command:

/usr/heimdal/libexec/hprop --database=dump-file --master-key=/var/db/krb5kdc/mit_stash --source=mit-dump --decrypt --stdout | /usr/heimdal/libexec/hpropd --stdin

General issues
==============

When migrating from a Kerberos 4 KDC.

Order in what to do things:
===========================

  * Convert the database, check all principals that hprop complains about.

     hprop -n --source=<NNN>| hpropd -n

     Replace <NNN> with whatever source you have, like krb4-db or krb4-dump.

  * Run a Kerberos 5 slave for a while.

  * Figure out if it does everything you want it to.

     Make sure that all things that you use works for you.

  * Let a small number of controlled users use Kerberos 5 tools.

     Find a sample population of your users and check what programs they use, you can also check the kdc-log to check what ticket are checked out.

  * Burn the bridge and change the master.

  * Let all users use the Kerberos 5 tools by default.

  * Turn off services that do not need Kerberos 4 authentication.

     Things that might be hard to get away is old programs with support for Kerberos 4. Example applications are old Eudora installations using KPOP, and Zephyr. Eudora can use the Kerberos 4 kerberos in the Heimdal kdc.