Project

General

Profile

Actions

Bug #2418

closed
MA MA

Skip configuration "include" nodes when file is empty

Bug #2418: Skip configuration "include" nodes when file is empty

Added by Maurizio Abba over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Whenever the yaml file has an "include" key, suricata include the value as a new configuration file.
If the included file is empty suricata will create a node with an empty string as a name. This should be avoided.

Note that this only happens if the included file is a valid empty yaml file (i.e, starting with "%YAML 1.1\n---\n" sequence).

It is sufficient to skip an included file whenever it's empty (value0 == '\0').

AH Updated by Andreas Herz over 8 years ago Actions #1

  • Target version set to TBD

VJ Updated by Victor Julien about 8 years ago Actions #2

  • Status changed from Assigned to Closed
  • Target version changed from TBD to 4.1beta1
Actions

Also available in: PDF Atom