https://redmine.openinfosecfoundation.org/https://redmine.openinfosecfoundation.org/favicon.ico?17011170022018-12-04T08:50:53ZOpen Information Security FoundationSuricata - Bug #2722: yaml: If yaml bypass option is misspelled it does not result in error/warning https://redmine.openinfosecfoundation.org/issues/2722?journal_id=105882018-12-04T08:50:53ZVictor Julienvictor@inliniac.net
<ul></ul><p>I think this will be quite tricky. We don't define a list of valid options where options that are unknown lead to a warning. Lots of options are allowed to be missing from the yaml. In this case a built-in default is used.</p> Suricata - Bug #2722: yaml: If yaml bypass option is misspelled it does not result in error/warning https://redmine.openinfosecfoundation.org/issues/2722?journal_id=121522019-05-23T21:45:35ZAndreas Herzoisf@herzandreas.de
<ul><li><strong>Assignee</strong> set to <i>Community Ticket</i></li><li><strong>Target version</strong> set to <i>TBD</i></li></ul> Suricata - Bug #2722: yaml: If yaml bypass option is misspelled it does not result in error/warning https://redmine.openinfosecfoundation.org/issues/2722?journal_id=121972019-05-24T05:12:55ZVictor Julienvictor@inliniac.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Assignee</strong> deleted (<del><i>Community Ticket</i></del>)</li><li><strong>Target version</strong> deleted (<del><i>TBD</i></del>)</li></ul>