> We just need someone to take it on once enough of the infrastructure is in 
> place.

I'd take this one! 

On Fri, Sep 04, 2015 at 07:52:00AM -0500, Seth Hall (JIRA) wrote:
> 
>     [ 
> https://bro-tracker.atlassian.net/browse/BIT-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21943#comment-21943
>  ] 
> 
> Seth Hall commented on BIT-835:
> -------------------------------
> 
> We should be able to get a very nice version of this into 2.5 with the Broker 
> key-value store and the net control framework.  
We just need someone to take it on once enough of the infrastructure is in 
place.
> 
> > Porting Drop and Catch-n-release to 2.0
> > ---------------------------------------
> >
> >                 Key: BIT-835
> >                 URL: https://bro-tracker.atlassian.net/browse/BIT-835
> >             Project: Bro Issue Tracker
> >          Issue Type: New Feature
> >          Components: Bro
> >    Affects Versions: git/master
> >            Reporter: Aashish Sharma
> >             Fix For: 2.5
> >
> >         Attachments: drop.bro, drop-catch-n-release.patch, scan.bro, 
> > test-drop-connectivity, test-restore-connectivity
> >
> >
> > The following patch ports the drop.bro to bro-2.0+ (along with 
> > catch-n-release functionality) 
> > [originally written for bro-1.5.3 and prior versions by Jim Mellander and 
> > Robin Sommer|policies] 
> > Also attaching scan.bro (which is ported to 2.0) 
> > scan.bro and drop.bro files need to go into policy/protocols/conn/ folder. 
> > Also adding test-drop-connectivity and test-restore-connectivity scripts 
> > which should go into aux/broctl/bin/ 
> > This patch and policies have been operational at LBNL for a few months now 
> > with bro-2.0. 
> > (sorry haven't created my own branch to commit these) \\- please let me 
> > know if this need to be otherwise.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.0.0-OD-02-259#70102)
> _______________________________________________
> bro-dev mailing list
> bro-dev@bro.org
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
_______________________________________________
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Reply via email to