Re: [Prelude Hybrid IDS] #158: Perl bindings lack idmef_criterion_value functions.
Prelude Hybrid IDS <[email protected]>
| Newsgroups | gmane.comp.security.ids.prelude.devel |
|---|---|
| Message-ID | <[email protected]> |
#158: Perl bindings lack idmef_criterion_value functions. ------------------------------------+--------------------------------------- Reporter: [email protected] | Owner: yoann Type: defect | Status: new Priority: normal | Milestone: Component: libprelude | Version: 0.9 Severity: normal | Resolution: Keywords: | ------------------------------------+--------------------------------------- Comment (by [email protected]): Hi, I am already a freenode user and I have joined the channel now. no idmef_criterion_* is not used in preludedb-admin. The alert_criteria (idmef_criteria_t) needed by preludedb_get_alert_idents is created via idmef_criteria_new_from_string. Unfortunately while I could probably manipulate/create such a string in perl I couldn't find any docs explaining its format. (reading the lex/yacc files didn't help) I have since found https://trac.prelude-ids.org/wiki/IDMEFCriteria which may help. But I did prefere the idea of manipulating objects in perl not a (presumably) long string. So for one reason or another tried to create the criteria using the API to first create criterion and build up a criteria. This seemed fairly straight forward to do and it looked like I could work out how to do it. But then I found idmef_criterion_* is missing from perl. Thorben -- Ticket URL: <https://trac.prelude-ids.org/ticket/158> 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