[97] in bug-owl
Re: libzephyr bug affecting owl users who renew tickets
daemon@ATHENA.MIT.EDU (James M. Kretchmar)
Sun Oct 13 23:42:17 2002
Message-Id: <200210140342.XAA24599@mission-control.mit.edu>
To: Greg Hudson <ghudson@MIT.EDU>
cc: bug-owl@MIT.EDU
In-Reply-To: Your message of "Sat, 12 Oct 2002 21:08:31 EDT."
<200210130108.VAA06513@error-messages.mit.edu>
Date: Sun, 13 Oct 2002 23:42:16 -0400
From: "James M. Kretchmar" <kretch@MIT.EDU>
> In 1994, I introduced a bug into libzephyr such that
owl developers will not be held responsible for any code written
before they arrived at MIT.
> ZResetAuthentication() after each notice. (Please try to avoid
> calling ZResetAuthentication() between recipients when there is a
> single notice with multiple recipients.)
I added that and it'll be out in the next owl patch release. Seems to
fix the problem.
> Also, I think there is an owl bug in the handling of authentication
> failures; owl appears to wait forever for an ack, instead of noticing
> the nack it should be getting.
Actually, I think the problem is that in this state nothing is getting
sent to the server at all. I'm not sure why. (Though owl makes a
mess of authentication stuff it should be reporting on naks).
I do notice that the server implementation only sends a nack if it
receives some data in the first place. Perhaps there should be an
nnack for not-a-nack that the server sends out sporadically regardless
of whether or not any data is received.
Thanks for the bug report.
kretch
