mit-krb5 thread support -- fork safety

[Sam Hartman]

>>>>> "Wyllys" == Wyllys Ingersoll <wyllys.ingersoll at sun.com> writes:


    Wyllys> Remind me again what we did that was not going to work for MIT?
    Wyllys> I know we talked about it before, but I can't recall the
    Wyllys> outcome of the conversation.

You changed the krb5_keyblock structure which is part of our ABI.

We created an initializer for krb5_keyblock.  OUr code can have an
expanded krb5_keyblock structure with private data and can cache key
schedules when the initializer and allocator are used, but cannot when
the caller manages krb5_keyblocks themselves.

--Sam