Project

General

Profile

Feature #13

Provide the ability for the user to define the analyzer configuration file

Added by Yoann VANDOORSELAERE over 18 years ago. Updated almost 14 years ago.

Status:
Closed
Priority:
High
Target version:
-
Start date:
Due date:
% Done:

0%

Resolution:
fixed

Description

Currently each analyzer hardcode access to it's own configuration file. We need to add a 'config-file' command line option, overriding default hardcoded analyzer configuration file.

In combination with ticket #12, this will allow to have several analyzer instance running with their own independant configuration.

History

#1 Updated by over 18 years ago

This (and #12 as well) has been already been implemented manually in the Snort sensor (I was told that people do run multiple Snort instances) by letting the user specify values passed to prelude_sensor_init(), hence this possibility should not be removed. Additionally libprelude cannot parse Snort's command line directly so care should be taken with including any functionality requiring access to the command line.

#2 Updated by Yoann VANDOORSELAERE over 18 years ago

The workaround you are describing here is a common workaround which work well for sensor not depending uppon prelude-getopt. The point of this ticket is to make the functionnality available to anyone who want to use it (things won't be broken for sensors not using prelude-getopt).

#3 Updated by Yoann VANDOORSELAERE over 18 years ago

  • Status changed from New to Assigned

#4 Updated by Yoann VANDOORSELAERE over 18 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Fixed in r3717

#5 Updated by Yoann VANDOORSELAERE almost 14 years ago

  • Project changed from PRELUDE SIEM to Libprelude
  • Category deleted (1)

Also available in: Atom PDF