Re: Weird timestamp length constraint in auparse.c
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.
Attachments:
- attachment.html (text/html — 405 bytes)