[2731] in testers
One comment about my patched kinit/kdestroy
daemon@ATHENA.MIT.EDU (Richard Basch)
Thu Dec 29 17:57:03 1994
Date: Thu, 29 Dec 1994 17:56:46 -0500
To: testers@MIT.EDU
From: "Richard Basch" <basch@MIT.EDU>
It does not fix one of the outstanding bugs:
It gets the krb4 ticket anyway, and creates a krb5cc_mumble file that
doesn't look to me like it could be valid (it has maybe 7 bytes,
ATHENA.MIT.EDU, a couple more bytes, the principal name, and perhaps 3
The krb5cc_* file will still be created, but no error will be printed.
To fix this would require even more patches, but the file is small, and
is in /tmp. So why bother. Most likely, you are getting kinit and
kdestroy from the same place, and the krb5cc_* file will get destroyed
on logout by the same person who created it. There are a few bizarre
conditions where this is not quite true, but in those cases, kinit will
not produce a non-zero exit status, as it did.
The v5 integration was a quick hack, and as long as there are no blatant
security concerns, and it works correctly for 99% of the cases, I am not
going to worry about a perfect solution.
-Richard
