Is there any reason this never made it into the source? It was reported at 1.4.3 and the problem still exists in 1.6.3. http://mailman.mit.edu/pipermail/krb5-bugs/2006-February/004246.html Luckily the patch still applies cleanly to 1.6.3.