Thanks; this was fixed in the krb5-1.2.4 release.