Re: [Bro-Dev] Option -z

> Does anybody remember what Bro's option -z is for? Well it's there in CHANGES, per the appended. But yeah looks like it never went anywhere beyond the original instigation, so I think removing it is okay. OTOH, it's a pretty handy general notion, so instead pushing it further strikes me as

Re: [Bro-Dev] CBAN design proposal

Here’s a revised/alternate design based on feedback so far: https://www.bro.org/development/projects/cban3.html Note that I put these at unique URLs and didn’t update in place since they’re different enough that, if someone tried to follow along from the start of the thread, I didn’t think it

Re: [Bro-Dev] CBAN design proposal

> On May 25, 2016, at 11:25 AM, Siwek, Jon wrote: > >> >> On May 25, 2016, at 9:49 AM, Slagell, Adam J wrote: >> >> So this has become an involved thread. Do we need a call, or do you think >> you can pull out enough to get started Jon? > > Yes I

Re: [Bro-Dev] CBAN design proposal

> On May 25, 2016, at 9:49 AM, Slagell, Adam J wrote: > > So this has become an involved thread. Do we need a call, or do you think you > can pull out enough to get started Jon? Yes I can reorganize all latest ideas into an alternate design document. Or if you meant

Re: [Bro-Dev] CBAN design proposal

> On May 25, 2016, at 12:12 AM, Robin Sommer wrote: > >> - discoverability metadata is aggregated during the nightly quality >> check processes and automatically commits that information to the >> “bro/cban” repo. > > Would it be better to maintain this information outside of

Re: [Bro-Dev] CBAN design proposal

> On May 24, 2016, at 4:46 PM, Matthias Vallentin wrote: > > More generally, there will presumably some functionality to add > "remotes" to one's configuration, allowing plugin writers to point to > experimental code if they wish. Then they can still hack out code and > mix

Re: [Bro-Dev] CBAN design proposal

> On May 24, 2016, at 2:52 PM, Jan Grashöfer wrote: > > > Imagine there was someone who published an awesome script but a new > version of Bro breaks it. Another one patched the script and sends the > patch to the original author. What will happen, in case he does not

Re: [Bro-Dev] CBAN design proposal

> On May 25, 2016, at 12:12 AM, Robin Sommer wrote: > > Overall, I agree that we can always add more restrictions later if it > turns out necessary. It's not that we'll have 1000s of Bro modules in > there within the first two weeks (as long as we prevent somebody > spamming us