[2640] in Kerberos-V5-bugs
krb5-admin/349: kdb5_util doesn't know that init_ets is called in init_context
daemon@ATHENA.MIT.EDU (bjaspan@MIT.EDU)
Thu Jan 23 14:12:03 1997
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: bjaspan@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, bjaspan@MIT.EDU
Date: Thu, 23 Jan 1997 19:10:57 GMT
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU
>Number: 349
>Category: krb5-admin
>Synopsis: kdb5_util doesn't know that init_ets is called in init_context
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bjaspan
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Thu Jan 23 14:11:01 EST 1997
>Last-Modified:
>Originator: Barry Jaspan
>Organization:
mit
>Release: 1.0-development
>Environment:
System: IRIX beeblebrox 5.3 11091812 IP22 mips
>Description:
kdb5_util.c contains the code:
retval = krb5_init_context(&util_context);
if (retval) {
fprintf(stderr, "krb5_init_context failed with error #%ld\n",
(long) retval);
exit(1);
}
krb5_init_ets(util_context);
initialize_adb_error_table();
This is a relic from when krb5_init_context() did not call
krb5_init_ets() and should be fixed. Note that kdb5_util *still*
needs to call initialize_adb_error_table(); that is usually called by
kadm5_init but, because kdb5_util is special, it needs that table
initialized before any kadm5 function is called.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
