On Tue, Mar 22, 2016 at 00:24 +0100, you wrote:
> If there are no objections, I (or Daniel?) will merge it into the
> broker-integration branch.
Let's merge it into master first, master can then be merged into the
integration branch. It's better to keep things as separate as possible
(I
I found a bug in the bro-part of broker in bro/src/EventHandler.cc and
bro/src/Event.h. I came across this when integrating my multi-hop
capable broker into bro in a deep-cluster setup.
The bug causes routing loops in between two directly peered bros when
both have subscribed to exactly the same
I got a query from ANL about Bro's capability to detect MOTS:
"I had a question for you – I was at a talk last week, and someone was
talking about a Man on the Side attack. The presenter had indicated that
suricata was currently the only tool doing this detection, but that they
[
https://bro-tracker.atlassian.net/browse/BIT-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Thayer updated BIT-1557:
---
Status: Merge Request (was: Open)
Assignee: (was: Daniel Thayer)
> broccoli code examples
[
https://bro-tracker.atlassian.net/browse/BIT-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Thayer updated BIT-1557:
---
Fix Version/s: 2.5
> broccoli code examples don't compile
>
>
>
[
https://bro-tracker.atlassian.net/browse/BIT-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=25101#comment-25101
]
Daniel Thayer commented on BIT-1557:
In branch "topic/dnthayer/ticket1557" in the broccoli repo, I've
fixed
[
https://bro-tracker.atlassian.net/browse/BIT-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer reassigned BIT-1533:
-
Assignee: Robin Sommer
> mysql analyzer does not set service to mysql
>
[
https://bro-tracker.atlassian.net/browse/BIT-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer reassigned BIT-1553:
-
Assignee: Robin Sommer
> Please merge topic/johanna/filter_subnet_table
>
On Mon, Mar 21, 2016 at 10:36 -0700, you wrote:
> That's fine in my thinking, because anyone developing and compiling a
> Broker application must have CAF installed anyway.
Yeah, I agree, sounds like the right strategy at this point.
Robin
--
Robin Sommer * ICSI/LBNL * ro...@icir.org *
Thanks for chiming in, Jon.
> [..] i.e. treat the use of CAF an implementation detail.
This is the clean way to think about layering and creating abstractions.
It applies to the API perspective, though. As long as CAF internals are
hidden from a Broker user, we are good.
The "implementation
> On Mar 18, 2016, at 10:20 PM, Matthias Vallentin wrote:
>
> During Broker refactoring, I noticed the following: all headers in
> broker/* include either standard library headers or Broker headers. This
> appears to be by design, which makes sense to me.
>
> As a library
[
https://bro-tracker.atlassian.net/browse/BIT-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Thayer reassigned BIT-1557:
--
Assignee: Daniel Thayer
> broccoli code examples don't compile
>
Daniel Thayer created BIT-1557:
--
Summary: broccoli code examples don't compile
Key: BIT-1557
URL: https://bro-tracker.atlassian.net/browse/BIT-1557
Project: Bro Issue Tracker
Issue Type: Task
Open Merge Requests
===
IDComponentReporterAssignee Updated For
VersionPrioritySummary
--- -- --
- --
14 matches
Mail list logo