[Bro-Dev] [JIRA] (BIT-699) Reorganizing layout of protocol analyzers

Seth Hall (JIRA) jira at bro-tracker.atlassian.net
Thu Nov 7 08:29:31 PST 2013

    [ https://bro-tracker.atlassian.net/browse/BIT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627#comment-14627 ] 

Seth Hall commented on BIT-699:

I think this ticket was completed by the work Robin did on reorganizing the analyzers for 2.2.

> Reorganizing layout of protocol analyzers
> -----------------------------------------
>                 Key: BIT-699
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-699
>             Project: Bro Issue Tracker
>          Issue Type: Task
>          Components: Bro
>    Affects Versions: git/master
>            Reporter: Robin Sommer
>             Fix For: 2.2
> We should restructure how protocol analyzers are organized inside the
> C++ core. Ideally, I'd like to have a single directory per analyzer
> with everything in there that relates to that analyzer, with no need
> to touch other places (currently, one needs to touch quite many for
> adding an analyzer). This includes the analyzers' `{{*.cc}}{{, }}{{*.h}}{{,
> }}{{*.bif}}{{, and }}{{*.pac}}{{ files. For the }}{{bif}}{{s, we should also move
> the corresponding parts from }}{{event.bif}}{{ and }}{{init-bare.bif}}{{ into
> that directory.
> This restructuring is also a good opportuntity to reorganize the
> Broxygen generation for analyzers: I think it would be nice to have
> one page per analyzer that has (1) a general description, (2) all
> tuning parameters, (3) all core events, and (4) links to all relevant
> }}{{base}}{{ and }}{{policy}}` scripts. 
> I'm setting this to 2.1 for now. It's not high-priority for that
> release and we can bump it further out if necessary. But I think it's
> good to keep in mind, and perhaps work on parts of this as time
> permits.

This message was sent by Atlassian JIRA

More information about the bro-dev mailing list