-
Notifications
You must be signed in to change notification settings - Fork 104
tests: add test for force-hash YAML validation. #2735
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
tests: add test for force-hash YAML validation. #2735
Conversation
| checks: | ||
| - shell: | ||
| args: | | ||
| (grep -q "Invalid configuration: force-hash algorithm 'shanani' must be one of: md5, sha1, sha256" suricata.log || \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which one is expected to succeed? Why are there 2 checks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! This does not seem to be resolved/answered. Could you please address this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still open :-/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
related OISF/suricata#14305 (comment)
Add test to ensure Suricata rejects invalid force-hash algorithm values in file logging configuration. The test verifies that an invalid hash type (e.g., 'shanani') causes Suricata to exit with an error during configuration validation. Issue: OISF#4330
493925e to
24bf792
Compare
|
hello @catenacyber , @inashivb changes are ready |
|
New version in #2751 |
Add test to ensure Suricata rejects invalid force-hash algorithm values in file logging configuration. The test verifies that an invalid hash type (e.g., 'shanani') causes Suricata to exit with an error during configuration validation.
Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status: OISF/suricata#14223
Redmine ticket: OISF#4330