Import/Export data problem between KDCs

[Darren Reed (Optimation)]

Hi Sam,

The following is an single record output from the Cybersafe kdb5_edit utility:

kdb5_edit load_dump version 2.0
10      9      28      28      0       0       0001 at REALM     
1       000000084fd338bcc676c7e36918bfb13a87d8434185189239122d76        1       
86400   604800  1       2145830400      0       912666651       0       0       
0       K/M at REALM      912666651       0       0               
1       00000008c97d8f3ca1efd3b59bbd3c19e1bea30f8f3e5578996e34da        0       
        0       0       0       0       0       0       0       0;

Looks good, so what's the problem, you might say?

I've been unable to get kdb5_util to create a dump which has the second hex
string.  I decode that as being:
name_len=10
mod_name_len=9
key_len=28
alt_key_len=28
salt_len=0
alt_salt_len=0
name=0001 at REALM
key_type[0]=1
key[0]=000000084fd338bcc676c7e36918bfb13a87d8434185189239122d76
kvno=1
max_life=86400
max_renewable_life=604800
??=1
expiration=2145830400
last_pw_change=0
last_success=912666651
last_failed=0
fail_auth_count=0
??=0
mod_name=K/M at REALM
mod_date=912666651
attributes=0
key_type[1]=1
key[1]=00000008c97d8f3ca1efd3b59bbd3c19e1bea30f8f3e5578996e34da
salt_type=0
salt=

It imports fine into 1.2.5 with the correct KDC password.

Darren