Thanks, this has already been fixed and will be in the upcoming krb5-1.4.3 release.