[krbdev.mit.edu #1429] AES/GSS combination broken

[Ken Raeburn via RT]

Just checked more carefully, and I don't think there's a memory
management problem after all.  The enctype list in the krb5_context has
an associated count and no terminating 0 value, whereas the function
interfaces tend to use a 0 terminator and no count; the allocations
varying in the addition of one extra value (for the terminator) had me
concerned, but it looks okay.