[37843] in Kerberos
Re: Documenting the kerberos KDC log file format
daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Tue Jan 31 10:13:33 2017
Date: Tue, 31 Jan 2017 00:44:20 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Todd Grayson <tgrayson@cloudera.com>
Message-ID: <20170131064420.GC8460@kduck.kaduk.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CALNT6MUYmXOyCS9-p80qw3dkPk2E3H+-r6VwxTQJjG9esocCSg@mail.gmail.com>
Cc: "kerberos@MIT.EDU" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
On Mon, Jan 30, 2017 at 11:01:46PM -0700, Todd Grayson wrote:
> Has anyone seen a good writeup of the krb5kdc.log file output format? For
> the types of log file output statements that it writes out. So for example
> the AS_REQ and TGS_REQ and follow up "closing down" lines representing a
> full connection span.
>
> More specifically does anyone have any content or pointers to constructing
> good parsers for turning this log data into record data? Parser tools for
> the default MIT KDC log format?
Unfortunately, the idea of a unified format was not in mind when things
were originally written, so a programmatic parse will be somewhat difficult.
We've tried to be more careful with more recent additions, but feel rather
constrained to not change the historical behavior and break existing
log-parsing scripts.
Maybe someone else on the list has some prior art that you could start
from, though.
-Ben
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
