On Dec 1, 2016, at 4:32 AM, Jan Grashöfer wrote:
>> Thanks. Let’s space out our blogs a little bit (We posted one yesterday on
>> bro-pkg) and save this one for after the 2.5 release.
>
> As 2.5 has been released and there have already been some questions on
> the mailing list, it would be go
> Thanks. Let’s space out our blogs a little bit (We posted one yesterday on
> bro-pkg) and save this one for after the 2.5 release.
As 2.5 has been released and there have already been some questions on
the mailing list, it would be good to publish the blog post.
Jan
___
Thanks. Let’s space out our blogs a little bit (We posted one yesterday on
bro-pkg) and save this one for after the 2.5 release.
> On Oct 4, 2016, at 4:09 PM, Jan Grashöfer wrote:
>
> Meanwhile I have added Michal's suggestions and he reviewed again:
> https://gist.github.com/J-Gras/3ff4d5308a6
Meanwhile I have added Michal's suggestions and he reviewed again:
https://gist.github.com/J-Gras/3ff4d5308a69e91fb61c65c12ecb818c
Feel free to publish :)
Jan
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-
> On Aug 31, 2016, at 11:42 AM, Jan Grashöfer wrote:
>
>> Jan, would you mind if we posted this directly to the Bro blog?
>
> I thought that was the original idea. I would be glad if the post is
> shared on the Bro blog once we have a final version.
Hah, ignore me. I was reading Michal's emai
> Feedback shared privately.
Thanks a lot for your detailed feedback Michal! I will definitely add
the changes you suggested.
> That's why I said polish not publish ;-) Send feedback, have it included or
> rejected, all can be done before 2.5
As already mentioned, I am kind of busy at the momen
That's why I said polish not publish ;-) Send feedback, have it included or
rejected, all can be done before 2.5
> On 31 Aug 2016, at 15:23, Seth Hall wrote:
>
>
>> On Aug 30, 2016, at 8:10 PM, Michał Purzyński
>> wrote:
>>
>> Feedback shared privately.
>>
>> Come on, let's read it and pol
> On Aug 30, 2016, at 8:10 PM, Michał Purzyński
> wrote:
>
> Feedback shared privately.
>
> Come on, let's read it and polish it a bit. It's already very good!
Let's wait until the 2.5 release. Seems like it might be a bit premature to
post it now since the 2.5 release hasn't happened yet.
Feedback shared privately.
Come on, let's read it and polish it a bit. It's already very good!
On Thu, Aug 25, 2016 at 1:22 AM, Jan Grashöfer
wrote:
> I have finished my draft for a blog post explaining the new intel
> framework features including some examples:
>
> https://gist.github.com/J-Gr
I have finished my draft for a blog post explaining the new intel
framework features including some examples:
https://gist.github.com/J-Gras/3ff4d5308a69e91fb61c65c12ecb818c
Feedback welcome!
Jan
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.
Thanks, integrated!
Robin
--
Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
I've attached the list of significant BroControl changes.
On 8/8/16 2:04 PM, Robin Sommer wrote:
Could folks take a look at NEWS and see what's missing?
Couple of things I think we should add at least:
- Document the cluster framework's new logger node, with an
example how to use it
Since the changes are impressive, a blog post would be a great idea indeed. Bro
is first (?) on the market (again!) to come up with something like this :)
Such post should describe all new Intel framework feature and give examples how
to use them.
> On 09 Aug 2016, at 17:21, Robin Sommer wrote
Thanks, will add.
Robin
On Tue, Aug 09, 2016 at 16:23 +0200, you wrote:
> > Could folks take a look at NEWS and see what's missing?
> > ...
> > - Document the recent intel framework updates.
>
> For the NEWS (all changes, feel free to cut down):
>
> +++
> - Bro's Intelligence Framework was
> Could folks take a look at NEWS and see what's missing?
> ...
> - Document the recent intel framework updates.
For the NEWS (all changes, feel free to cut down):
+++
- Bro's Intelligence Framework was refactored and new functionality
has been added:
- The intel framework now supports t
I will create a list of BroControl changes.
On 8/8/16 2:04 PM, Robin Sommer wrote:
> Could folks take a look at NEWS and see what's missing?
>
> Couple of things I think we should add at least:
>
> - Document the cluster framework's new logger node, with an
> example how to use it.
>
>
16 matches
Mail list logo
