I can confirm the behavior above. This was supposed to be fixed here: http://mailman.mit.edu.ezproxyberklee.flo.org/pipermail/krb5-bugs/2002-September/000110.html