Feature #1970
closedjson: make libjansson mandatory
Description
The idea is to reduce the number of conditionals and json/eve is a core component of suricata these days.
Updated by Victor Julien about 7 years ago
- Subject changed from make libjansson mandatory to json: make libjansson mandatory
Since Jason has some code to do JSON output w/o libjansson, this should be reconsidered.
Updated by Victor Julien almost 7 years ago
- Target version changed from 4.0beta1 to 70
Updated by Victor Julien almost 7 years ago
- Target version changed from 70 to TBD
Updated by Victor Julien about 6 years ago
- Related to Bug #2473: Please allow disabling every option (add --without-{option}) added
Updated by Victor Julien about 6 years ago
- Status changed from New to Assigned
- Assignee changed from OISF Dev to Jason Ish
Jason, any thoughts on this? I think now with Rust support we've tied in more to jansson.
Updated by Jason Ish about 6 years ago
I'd be OK with making libjansson mandatory. There would have to be a good argument made to make it required I think.
Updated by Victor Julien about 6 years ago
I guess the only reason not to do it is if your own json output code would be used instead?
Updated by Jason Ish almost 6 years ago
Victor Julien wrote:
Jason, any thoughts on this? I think now with Rust support we've tied in more to jansson.
With Rust mandatory, we could potentially move away from libjansson and do the eve output completely in Rust, using its own Rust support. Might be a bit of headache for logging app-layer protos that are done in C, but yeah, requiring Rust right now pretty much requires libjansson, if you want any logging.
Updated by Victor Julien over 5 years ago
- Target version changed from TBD to 5.0beta1
When Rust is mandatory we need to revisit this. Either make jansson mandatory or replace it.
Updated by Victor Julien about 5 years ago
- Status changed from Assigned to Closed