-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error normalizing NETFILTER_CFG #69
Comments
This is essentially a duplicate of issue 25 and issue 35. I recommend close as duplicate. |
@rgbriggs Hmm, I don't think I follow. To me those issues don't look related at all. Could you elaborate, please? |
On 2018-03-18 06:22, Nikolai Kondrashov wrote:
@rgbriggs Hmm, I don't think I follow. To me those issues don't look
related at all. Could you elaborate, please?
Perhaps I misunderstood the goal of this issue report.
Is there work expected by the scribery/aushape team to work around this
or ignore it? Or is it to get Steve to stop the normalizer from
complaining? Or is it expected that the kernel folks resolve
ghak25/ghak35.
Now that a number of other issues have been addressed and better
understood I am optimistic ghak25/35 can be addressed which should
resolve this scribery/aushape issue.
|
I think the solution to this on aushape side should be to fail generating the normalized data, and mark the partially-converted JSON object with an error. I would, of course, like this resolved on the audit or kernel side, but I expect things like this will keep happening, so aushape will need to handle it anyway, and it can start with handling this case while it's being resolved. |
The
auparse_normalize
function returns an error for following piece of audit.log:The particular issue can be reproduced with
auparse
as well, like this:This was seen on Fedora 25 with the following packages installed:
Response from Steve Grubb from the audit team was:
The text was updated successfully, but these errors were encountered: