Inconsistencies in KDC status messages formats

[Will Fiveash]

On Mon, Oct 22, 2012 at 11:35:43AM -0400, Zhanna Tsitkova wrote:
> Hello,
> As part of KDC status reporting, the string status messages are  
> generated and incorporated into log messages to be recorded in KDC log  
> files.
> It appears that the messages vary greatly  in format and style.  For  
> example,
> "ENCRYPTING_TICKET" (all upper case with underscore)
> "ANONYMOUS NOT ALLOWED"     (all upper case without underscore)
> "generating reply key"  (all lower case)
> "UNEXPECTED NULL in header_ticket"   etc
> In addition, the messages are inconsistent as the statements. Compare  
> "CANT_FIND_CLIENT_KEY" and "DECRYPT_SERVER_KEY".  Both of them are  
> reported on error, but only the former sound like it.
> 
> The logical thing would be to make the string status messages more  
> consistent ("All english words  without underscores" or,  
> alternatively, ALL_UPPER_CASE_WITH_UNDERSCORE ) and document the update.
> 
> Any thoughts on the matter?

All correctly spelled English words without underscores.

-- 
Will Fiveash
Oracle Solaris Software Engineer
http://opensolaris.org/os/project/kerberos/
Sent using mutt, a sweet, text based e-mail app <http://www.mutt.org/>