Weird timestamp length constraint in auparse.c

[Santosh Ananthakrishnan]

I don't think anything needs to be done, a malformed timestamp only causes
that line to be parsed badly. I was wondering if this behavior was
intentional, now that I see it was, I'm happy to leave this as an FYI for
anybody else being lazy with their test case generation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-audit/attachments/20151214/0e32e271/attachment.htm>