[Bro-Dev] get_event_peer() with Broker

I was looking at how to extend the get_event_peer() bif to work with Broker events and realized that there's problem I hadn't thought about so far: when a event comes into Bro through Broker, there's no way right now to tell which peer it was sent from. If I'm not missing anything, the event comes

[Bro-Dev] [JIRA] (BIT-1530) protocol_confirmation event cannot be hooked by plugin

[ https://bro-tracker.atlassian.net/browse/BIT-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24008#comment-24008 ] Robin Sommer commented on BIT-1530: --- Yeah, I think I agree this should be changed. The origin

[Bro-Dev] [JIRA] (BIT-1527) Please merge topic/johanna/cve-2015-3194

[ https://bro-tracker.atlassian.net/browse/BIT-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Sommer updated BIT-1527: -- Resolution: Merged (was: Fixed) Status: Closed (was: Merge Request) > Please merge topic/joha

[Bro-Dev] [JIRA] (BIT-1531) Use of mktemp command should be more portable

[ https://bro-tracker.atlassian.net/browse/BIT-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24007#comment-24007 ] Tim Yardley commented on BIT-1531: -- I would suggest changing the fix to represent the generic

[Bro-Dev] [JIRA] (BIT-1531) Use of mktemp command should be more portable

[ https://bro-tracker.atlassian.net/browse/BIT-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robin Sommer reassigned BIT-1531: - Assignee: Robin Sommer > Use of mktemp command should be more portable > ---

[Bro-Dev] [Auto] Merge Status

Open Merge Requests === IDComponentReporterAssigneeUpdated For Version PrioritySummary --- -- -- -- - -- -- BIT