[3044] in Kerberos-V5-bugs
pending/694: kadmind problem
daemon@ATHENA.MIT.EDU (Doug Granzow)
Tue Feb 23 11:35:09 1999
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: gnats-admin@rt-11.MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU,
Doug Granzow <dgranzow@gunzour.isbu.digex.net>
Date: Tue, 23 Feb 1999 11:33:56 -0500 (EST)
From: Doug Granzow <dgranzow@gunzour.isbu.digex.net>
To: krb5-bugs@MIT.EDU
>Number: 694
>Category: pending
>Synopsis: kadmind can be crashed by client
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: gnats-admin
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Tue Feb 23 11:35:00 EST 1999
>Last-Modified:
>Originator: Super-User
>Organization:
DIGEX, Inc.
>Release: krb5-1.0.5
>Environment:
System: SunOS krb5-slave.digex.net.belt 5.6 Generic_105181-11 sun4u sparc SUNW,Ultra-1
Architecture: sun4
>Description:
An authenticated kadmin user can cause the kadmind server to exit
by typing control-c immediately after typing "listprincs".
>How-To-Repeat:
On any system, run kadmin. Once authenticated, enter the "listprincs"
command, then *immediately* type control-c before any response is
returned. The kadmind process on the kdc exits with nothing logged
to the log file. A core file is created in the root directory (/).
>Fix:
Not known
>Audit-Trail:
>Unformatted:
