Project

General

Profile

Actions
Copy link

Bug #543

closed

Windows directory parsing

Added by Peter Manev over 11 years ago. Updated over 6 years ago.

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

Description

6/9/2012 -- 19:01:31 - <Error> - [ERRCODE: SC_ERR_OPENING_RULE_FILE(41)] - openi
ng rule file C:\Program Files\Suricata 1.4beta1\rules\\stream-events.rule: No su
ch file or directory.
6/9/2012 -- 19:01:31 - <Error> - [ERRCODE: SC_ERR_OPENING_RULE_FILE(41)] - openi
ng rule file C:\Program Files\Suricata 1.4beta1\rules\\http-events.rule: No such
file or directory.

if the rule directory is given as
 default-rule-path: C:\Program Files\Suricata 1.4beta1\rules
if it is given as
 default-rule-path: C:\Program Files\Suricata 1.4beta1\rules\
there is no problem the rules files load.
Actions
Copy link
 #1

Updated by Victor Julien over 11 years ago

So in both cases it works, but it just prints 2 backslashes?

Actions
Copy link
 #2

Updated by Peter Manev over 11 years ago

no it does not work in the first case:
if the rule directory is given as
default-rule-path: C:\Program Files\Suricata 1.4beta1\rules

BUT if you add the "\" in the yaml conf it works without a problem
aka:
if it is given as
default-rule-path: C:\Program Files\Suricata 1.4beta1\rules\

Actions
Copy link
 #3

Updated by Victor Julien over 10 years ago

  • Target version set to TBD
Actions
Copy link
 #4

Updated by Peter Manev over 8 years ago

  • Status changed from New to Closed

There is too much admin/coding/sync overhead with regards to this - so it is less intrusive if it is reflected in the documentation as opposed to spending code hrs on it.
It is also taken care of in the msi packaging itself in order to minimize the exposure.

Actions
Copy link
 #5

Updated by Victor Julien over 6 years ago

  • Target version deleted (TBD)
Actions
Copy link

Also available in: Atom PDF