Here we collect a list of development projects and ideas for future Bro versions. Some are already in the works, some are scheduled to start shortly, and others are just ideas at this point. For those projects with more extensive descriptions, please keep in mind that usually these represent initial proposals for the targeted functionality, and won’t necessarily match what the end result will look like eventually. This list contains work items of all sizes, let us know if you are interested in helping out with any of them.
As we’re collecting initial experiences with Broker, some items for the wishlist have come up that would be nice to add.
The semantics for ProtocolViolation() and ProtocolConfirmation() need fine-tuning.
Bro’s source code has evolved over many years, and is now using a number of slightly different layout styles. We need a pretty printer that unifies layout automatically, both for C++ code and the Bro script code.
BroControl could setup/maintain an OS-level sandbox/jail for the running Bro process.
Regression testing tasks:
www.bro.org could use some layout/CSS cleanup.
Scripting language tasks:
- Add a list type
- Add UTF8 strings, replace current string type with type for raw bytes.
- All issues tagged with language in the tracker
- Bring POP3 back. (#672).
- Bring ARP back.
Fix and test Bro’s debugger (#678)
Intelligence interfaces to external source.
Develop and maintain database of vulnerable software for monitoring.
Broxygen wishlist, see #751.
Drop root privileges after opening interfaces, w/ integration into broctl.
Investigate optimizing management of memory shared between main and child threads.
Mechanism to feed external data directly into protocol and file analyzers. One application is fuzzing.
These projects are finished but we keep the information here for reference. Please note that since these are often initial design thoughts, specifics probably don’t match with what ended up being implemented in Bro.