Multiple ETYPE-INFO-ENTRY with same etype but different salts

[Weijun Wang]

>> We will fix our problem. My last question would be: so the customer
>> has no workaround now on their KDC side?
>
> For existing keys, no.  There aren't a lot of knobs on the KDC for this
> other than the key data itself.

I guess the keys are stored in a db file as a array. Isn't there a way 
to strip some kinds of keys from this file to make a new db? Or, its 
integrity protection is so nice that we cannot touch it at all?

Thanks
Max