krb5_encrpyt_block freeing

[Ken Hornstein]

>Krb5_init_keyblock has a required length parameter 

Hmmm ... I guess I see what you mean; you can't allocate your own
space, because the wrong C runtime might try to free it.  But since
krb5_init_keyblock also takes the enctype, you would think that it
could just allocate the right amount of space for you, if you could
tell it somehow.

I know that if you pass in zero for the length, krb5_init_keyblock
won't allocate any space.  But is that even _useful_?

--Ken