Re: [Prelude Hybrid IDS] #150: A number of issues with command line options
Prelude Hybrid IDS <[email protected]>
| Newsgroups | gmane.comp.security.ids.prelude.devel |
|---|---|
| Message-ID | <[email protected]> |
#150: A number of issues with command line options ------------------------------+--------------------------------------------- Reporter: [email protected] | Owner: yoann Type: defect | Status: assigned Priority: normal | Milestone: Libprelude 0.9.8 Component: prelude-manager | Version: 0.9 Severity: normal | Resolution: Keywords: | ------------------------------+--------------------------------------------- Changes (by yoann): * milestone: => Libprelude 0.9.8 * status: new => assigned * summary: a number of issues with the prelude-manager command line options => A number of issues with command line options Old description: > i ran into a number of problems when trying to set up a prelude-manager > under a different > profile name. some options cause problems or must be used differently > than described. > > 1.) the usage of prelude-manager says "--prelude --profile=ARG" but that > does not work. > removig the = and writing "--prelude --profile ARG" works ok. > > 2.) using "--config=ARG" gives a warning: Invalid option -- "config" (0). > but the specified config-file seems to be used anyway. > > 3.) using two options from the "--prelude" subcategory without the > category gives a segfault. > adding another "--prelude" (i.e. saying "--prelude --profile foo > --prelude > --heartbeat-interval=60" instead of "--prelude --profile foo > --heartbeat-interval=60" > works ok). for the other categories, you can give multiple categroy- > options per category. > > 4.) "--prelude --profile foo" (and maybe others) only works if specified > before "-d" > > some of this behaviour may be intended, but at least it should be > documented... > > there could be more issues with the command-line option handling. i did > not test this > systematically. these are just the ones i ran into... > > this was done with prelude-manager-0.9.4.1 and libprelude-0.9.7.2 New description: i ran into a number of problems when trying to set up a prelude-manager under a different profile name. some options cause problems or must be used differently than described. 1. the usage of prelude-manager says ''--prelude --profile=ARG'' but that does not work. Removing the ''='' and writing ''--prelude --profile ARG'' works ok. 2. using ''--config=ARG'' gives a warning: '''Invalid option -- "config" (0).''' but the specified config-file seems to be used anyway. 3. using two options from the ''--prelude'' subcategory without the category gives a segfault. adding another ''--prelude'' (i.e. saying ''-- prelude --profile foo --prelude --heartbeat-interval=60'' instead of ''-- prelude --profile foo --heartbeat-interval=60'' works ok). for the other categories, you can give multiple categroy-options per category. 4. ''--prelude --profile foo'' (and maybe others) only works if specified before ''-d'' some of this behaviour may be intended, but at least it should be documented... there could be more issues with the command-line option handling. i did not test this systematically. these are just the ones i ran into... this was done with prelude-manager-0.9.4.1 and libprelude-0.9.7.2 Comment: Reword description for readability. Reword summary since this is not prelude-manager specific. -- Ticket URL: <https://trac.prelude-ids.org/ticket/150> Prelude Hybrid IDS <http://www.prelude-ids.org> The Prelude Hybrid Intrusion Detection System suite _______________________________________________ Prelude-devel site list [email protected] http://www.prelude-ids.org/mailman/listinfo/prelude-devel