Re: [Prelude Hybrid IDS] #269: Wrong idmef_*_get_next_* python binding functions?
"Prelude Hybrid IDS" <[email protected]>
| Newsgroups | gmane.comp.security.ids.prelude.devel |
|---|---|
| Message-ID | <[email protected]> |
#269: Wrong idmef_*_get_next_* python binding functions? ------------------------------------+--------------------------------------- Reporter: [email protected] | Owner: yoann Type: defect | Status: new Priority: normal | Milestone: Libprelude 0.9.17 Component: libprelude | Version: 0.9 Severity: normal | Resolution: Keywords: python binding | ------------------------------------+--------------------------------------- Comment (by anonymous): Replying to [comment:9 pollux]: > [attachment:ticket:269:bindings_get_next.diff] should fix the problem for all _get_next_* functions. Thank you! Could you also have a look at the uint32_t* and uint16_t* types? Thanks in advance, Ben -- Ticket URL: <https://trac.prelude-ids.org/ticket/269#comment:10> 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