Ticket History #536: kdc crashes when requires-preauth is set

From mione@boeing.rutgers.edu Mon Jan 26 14:41:28 1998
Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by rt-11.MIT.EDU (8.7.5/8.7.3) with SMTP id OAA26151 for <bugs@RT-11.MIT.EDU>; Mon, 26 Jan 1998 14:41:23 -0500
Received: from boeing.rutgers.edu by MIT.EDU with SMTP
id AA16121; Mon, 26 Jan 98 14:41:31 EST
Received: (from mione@localhost) by boeing.rutgers.edu (8.8.5/8.6.12) id OAA02551; Mon, 26 Jan 1998 14:41:20 -0500 (EST)
Message-Id: <199801261941.OAA02551@boeing.rutgers.edu>
Date: Mon, 26 Jan 1998 14:41:20 -0500 (EST)
From: Tony Mione <mione@boeing.rutgers.edu>
Reply-To: mione@boeing.rutgers.edu
To: krb5-bugs@MIT.EDU
Subject: kdc crashes when requires-preauth is set
X-Send-Pr-Version: 3.99

Tony Mione, RUCS/NS, Rutgers University, Hill 055, Piscataway,NJ - 732-445-0650
mione@nbcs-ns.rutgers.edu W3: http://www-ns.rutgers.edu/~mione/
PGP Fingerprint : E2 25 2C CD 28 73 3C 5B 0B 91 8A 4E 22 BA FA 9F
Editorial Advisor for Digital Systems Report ***** Important: John 17:3 *****
System: SunOS boeing.rutgers.edu 5.5.1 Generic_103640-05 sun4u sparc SUNW,Ultra-1
Architecture: sun4

I've seen this in the known bugs list on the mit web server
(http://web.mit.edu/kerberos/www/krb5-1.0/known-bugs.html). The entry says
it will be fixed soon. My question is, will this be fixed in patch level 5?
Also, can you give an approximate timeframe as to when the patch will be
available. This is a fairly important feature for us to have.




From: Tom Yu <tlyu@MIT.EDU>
To: mione@boeing.rutgers.edu
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-kdc/536: kdc crashes when requires-preauth is set
Date: Mon, 26 Jan 1998 21:39:16 -0500

The fix for the preauth crash has been checked into the trunk, and
will also be present in the 1.0.5 patch release, which should be
coming out in the next couple of weeks.

---Tom

From: Tom Yu <tlyu@MIT.EDU>
To: mione@boeing.rutgers.edu
Cc: krb5-bugs@MIT.EDU
Subject: Re: krb5-kdc/536: kdc crashes when requires-preauth is set
Date: Mon, 26 Jan 1998 22:48:15 -0500

Actually, does the kdc still crash with 1.0.4 when you set
requires-preauth? If so, we should look into that, since I believe
the problem was supposed to be fixed quite some time ago. (well before
1.0.4)

---Tom

State-Changed-From-To: open-feedback
State-Changed-By: tlyu
State-Changed-When: Tue Jan 27 00:19:58 1998
State-Changed-Why:

Should have been fixed already... checking...

Responsible-Changed-From-To: krb5-unassigned->tlyu
Responsible-Changed-By: tlyu
Responsible-Changed-When: Tue Jan 27 00:20:03 1998
Responsible-Changed-Why:

Refiled


From: Tony Mione <mione@boeing.rutgers.edu>
To: Tom Yu <tlyu@MIT.EDU>
Cc: Tony Mione <mione@boeing.rutgers.edu>, krb5-bugs@MIT.EDU
Subject: Re: krb5-kdc/536: kdc crashes when requires-preauth is set
Date: Tue, 27 Jan 1998 06:53:21 -0500 (EST)

-----BEGIN PGP SIGNED MESSAGE-----

On Mon, 26 Jan 1998, Tom Yu wrote:


Actually, I haven't applied patch levels 2-4. I didn't see the
patch in the release notes for those levels. In addition, the bug still
shows up on the known bugs page:

http://web.mit.edu/kerberos/www/krb5-1.0/known-bugs.html

If it has been fixed, then I will apply the patches to bring us up
to rev. Otherwise, I was going to wait for 1.0.5 so I am not constantly
patching and releasing new code. Sorry if I had you chasing your tail.


Tony Mione, RUCS/NS, Rutgers University, Hill 055, Piscataway,NJ - 732-445-0650
mione@nbcs-ns.rutgers.edu W3: http://www-ns.rutgers.edu/~mione/
PGP Fingerprint : E2 25 2C CD 28 73 3C 5B 0B 91 8A 4E 22 BA FA 9F
Editorial Advisor for Digital Systems Report ***** Important: John 17:3 *****

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQB1AwUBNM3KqfMKRuSgNA5pAQF+ywL/UZwOiko4f5Nm4vaGDP56/GwoKK0z7UnJ
h+GF21llXDaZ7dp/ZuuCH0+yj2CWTu1NWKs754nYT/tMjjneNQ12pbEgT0MJxr4h
RkaxS/a5YtBHzLqLuplHcfUqnRtThrLD
=rW3B
-----END PGP SIGNATURE-----


From: Tom Yu <tlyu@MIT.EDU>
To: Tony Mione <mione@boeing.rutgers.edu>
Cc: Tom Yu <tlyu@MIT.EDU>, krb5-bugs@MIT.EDU
Subject: Re: krb5-kdc/536: kdc crashes when requires-preauth is set
Date: Tue, 27 Jan 1998 23:29:25 -0500



It's ok. We were lame and failed to update the known bugs page. It
was in fact fixed as far back as 1.0.3 I believe, though if I were
you I would wait for 1.0.5 anyway, due to some additional fixes we've
applied.

I tested our current sources recently and the bug does not seem to be
present.

---Tom

State-Changed-From-To: feedback-closed
State-Changed-By: tlyu
State-Changed-When: Sun Feb 22 21:12:38 1998
State-Changed-Why:

Is already fixed.