[2876] in Kerberos-V5-bugs
krb5-admin/547: minor nit in kadmin.local bahvaiour
daemon@ATHENA.MIT.EDU (Chris P. Ross)
Wed Feb 11 19:02:29 1998
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: bjaspan@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, cross@va.pubnix.com
Date: Wed, 11 Feb 1998 19:01:15 -0500 (EST)
From: cross@va.pubnix.com (Chris P. Ross)
Reply-To: cross@va.pubnix.com
To: krb5-bugs@MIT.EDU
Cc: cross@va.pubnix.com
>Number: 547
>Category: krb5-admin
>Synopsis: when kadmin.local is used, the "who modified" is "wrong"
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: bjaspan
>State: open
>Class: sw-bug
>Submitter-Id: unknown
>Arrival-Date: Wed Feb 11 19:02:01 EST 1998
>Last-Modified:
>Originator: Chris P. Ross
>Organization:
UUNET Technologies, Inc.
>Release: krb5-1.0.4
>Environment:
System: BSD/OS ballista.va.pubnix.com 3.1 BSDI BSD/OS 3.1 Kernel #5: Fri Nov 21 16:28:46 EST 1997 lidl@pembroke.va.pubnix.com:/export/src/bsdi/sys/compile/DESKTOP i386
>Description:
When kadmin.local is used to enter a new principal, it puts something
it constructs into the "who" part of the "Last modified" tag. In some cases,
this may not be a valid principal, tho it looks like it is.
>How-To-Repeat:
Take a user that doesn't exist in the db. Become root on the server
as that user, and create a user@REALM principal with kadmin.local. Then,
getprinc on that user. It will show a "user/admin@REALM" under "Last
modified:". But, user/admin@REALM doesn't actually exist...
>Fix:
Make it say something to indicate that no kerberos authentication was
done on the user who made/modified the principal being examined.
>Audit-Trail:
>Unformatted:
