Import/Export data problem between KDCs

Sam Hartman hartmans at MIT.EDU
Thu Oct 31 23:28:01 EST 2002


>>>>> "Darren" == Darren Reed (Optimation) <darrenr at optimation.com.au> writes:

    Darren> Earlier in the week, I was doing some testing on importing
    Darren> and exporting data between a 1.2.5 KDC and an "old"
    Darren> CyberSafe KDC (dump output is 2.0.)

I don't think we really support cross-vendor dumps.  Certainly I'm not
aware of any work to make this work consistently.  I know that MIT has
stuff we represent in our database that cannot be represented in a
Heimdal database.  I'm fairly certain the converse is true as well.

If you can show that for example the current MIT code cannot make a
dump that 1.1-based code can read then we'd certainly consider it a
problem until we'd decided why it was broken.  AT that point we'd
either decide we weren't interested in fixing, or more likely produce
some sort of fix.

If you want this issue fixed quickly you should prove in the next day
or so that current code cannot produce a dump read by old code.



Alternatively, if you find out what the problem is, we'd be happy to
take a look.  I just don't expect we'll have time to go chasing down
cross-vendor dump problems without more direction.




More information about the krbdev mailing list