Re: [Bro-Dev] Flare removal

> On May 20, 2016, at 6:02 PM, Azoff, Justin S wrote: > > I think Robins branch doesn't fix the problem because I don't think the > flares were really the issue.. I think bro started having issues because > between 2.3 and 2.4 traffic volumes increased, cluster sizes

Re: [Bro-Dev] CBAN design proposal

> On May 21, 2016, at 5:44 PM, Robin Sommer wrote: > > As I read through the design doc, I started questioning our plan of > curating CBAN content. I know that's what we've been intending to do, > but is that really the best approach? I don't know of script > repositories for

Re: [Bro-Dev] CBAN design proposal

> In other words, my proposal is to put authors into control of their > code, and make them fully responsible for it too --- not us. We'd just > connect authors with users, with as little friction as possible. > I support this completely. > If we want some kind of quality measure, we could

Re: [Bro-Dev] CBAN design proposal

On Fri, May 20, 2016 at 20:16 +, Jon wrote: > Here’s an updated design doc for CBAN, a plugin manager for Bro, with > some new ideas on how it could work: Cool, thanks. I'm going to send some feedback but first I wanted to bring something up that might be controversial. :-) As I read

[Bro-Dev] Broker status update

This is just a brief summary of where the Broker overhaul is currently at. The new Broker API will come two types of endpoints: blocking and nonblocking. The former provides a synchronous API to receive messages, whereas the latter operates fully asynchronous. Performance-wise, the asynchronous