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
command-line options: validate #15
Comments
You can just run the laurel executable without any parameters and pipe auditd log lines into its STDIN. (But don't forget the EOE messages, at least for now.) It will write its log to an |
having a full event set seems to be a partial issue
part is validate processing, part syntax. something that can be used for example in ansible template deployment to ensure not deploying broken config |
Thanks for the clarification. I'm not really sure how one should test with live data. I think, for the time being, I should just add a |
@juju4 ping? |
Sorry for delay
I tried with an expected valid config file and and after adding some useless line with same results Ideally, in success or fail, I would add some output to confirm laurel version, config file used, syntax ok or not and if not which lines are problematic Thanks! Note: when publishing releases, would be nice to add checksums (sha256...) |
There is now a |
as best practice, laurel executable should have a test/dry-run/foreground option to test configuration (syntax and working execution)
The text was updated successfully, but these errors were encountered: