Bug #4554: Configuration test mode succeeds when classification.config file contains invalid content - Suricata - Open Information Security Foundation

Actions

Copy link

Bug #4554

closed

Configuration test mode succeeds when classification.config file contains invalid content

Added by Jeff Lucovsky almost 3 years ago. Updated over 1 year ago.

Status:

Closed

Priority:

Normal

Assignee:

Jeff Lucovsky

Target version:

7.0.0-rc1

Affected Versions:

5.0.7, 6.0.3

Effort:

Difficulty:

Label:

Description

lucovsky@ ~/src/jal/suricata (master) $ echo "this is invalid" > classification.config
jlucovsky@ ~/src/jal/suricata (master) $ suricata -T -c suricata.yaml -S ~/rules/be.rule
[279217] 3/7/2021 -- 08:26:22 - (suricata.c:1615) <Info> (ParseCommandLine) -- Running suricata under test mode
[279217] 3/7/2021 -- 08:26:22 - (suricata.c:1059) <Notice> (LogVersion) -- This is Suricata version 7.0.0-dev (fb6246b26 2021-06-02) running in SYSTEM mode
[279217] 3/7/2021 -- 08:26:23 - (util-classification-config.c:260) <Error> (SCClassConfAddClasstype) -- [ERRCODE: SC_ERR_INVALID_SIGNATURE(39)] - Invalid Classtype in classification.config file
[279217] 3/7/2021 -- 08:26:23 - (suricata.c:2782) <Notice> (SuricataMain) -- Configuration provided was successfully loaded. Exiting.
jlucovsky@ ~/src/jal/suricata (master) $ echo $?
0

The expected behavior is a return code of 1

Related issues 2 (1 open — 1 closed)

Actions

Copy link

Updated by Jeff Lucovsky almost 3 years ago

Related to Bug #4553: Configuration test mode succeeds when reference.config file contains invalid content added

Actions

Copy link

Updated by Jeff Lucovsky almost 3 years ago

Subject changed from Configuration test mode succeeds when reference.config file contains invalid content to Configuration test mode succeeds when classification.config file contains invalid content

Actions

Copy link