[16326] in Kerberos-V5-bugs
[krbdev.mit.edu #8816] kproplog cannot display LOCKDOWN_KEYS
daemon@ATHENA.MIT.EDU (Greg Hudson via RT)
Tue Jun 11 11:17:34 2019
Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: Greg Hudson via RT <rt-comment@KRBDEV-PROD-APP-1.mit.edu>
In-Reply-To: <rt-8816@krbdev.mit.edu>
Message-ID: <rt-8816-49488.5.90333191361509@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #8816'":;
Date: Tue, 11 Jun 2019 11:16:30 -0400
MIME-Version: 1.0
Reply-To: rt-comment@KRBDEV-PROD-APP-1.mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
Ticket 8125 (commit 971fae8285427b27dfd8c9a535a18eb588ee0689) added
krb5_flags_to_strings() and used it in kadmin.c, replacing the local
flags table there. It left alone the local flags table and
print_flags() function in kproplog.c.
Ticket 8365 (commit 534db9834d6a77dc5e948e12844e72ba4e971e8c) added the
lockdown_keys flag, but did not update the table in kproplog.c.
kproplog only displays attribute flags in double-verbose mode (-vv), so
this omission is probably not noticeable, but for code hygiene the
local flags table in kproplog should be removed in favor of
krb5_flags_to_strings(), just as it was for kadmin.
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
