[2514] in Kerberos-V5-bugs
krb5-admin/238: server_acl.c logs errors incorrectly
daemon@ATHENA.MIT.EDU (bjaspan@MIT.EDU)
Mon Nov 25 18:01:15 1996
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: Mon, 25 Nov 1996 23:00:12 GMT
From: bjaspan@MIT.EDU
Reply-To: bjaspan@MIT.EDU
To: krb5-bugs@MIT.EDU
>Number: 238
>Category: krb5-admin
>Synopsis: server_acl.c logs errors incorrectly
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: bjaspan
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Mon Nov 25 18:01:01 EST 1996
>Last-Modified:
>Originator: Barry Jaspan
>Organization:
mit
>Release: 1.0-development
>Environment:
System: IRIX the-tick 5.3 02091401 IP22 mips
>Description:
The acl-parsing and processing code in lib/kadm5/srv/server_acl.c does
not use krb5_klog_syslog to log errors; instead, it uses com_err and
fprintf(stderr). The com_err calls at least show up in the correct
log location, although they are ugly. The fprintf messages do not
show up anywhere if kadmind backgrounds itself. Some of the messages
that are fprintf'ed include "Invalid acl operation letter" (or
whatever it says).
This is not a high-priority 1.0 bug.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
