zeek-dev June 2012

zeek-dev@lists.zeek.org

103 discussions

[Bro-Dev] #478: Move BinPAC docs over to new server

by Bro Tracker

#478: Move BinPAC docs over to new server ----------------------------+-------------------- Reporter: robin | Owner: seth Type: Problem | Status: new Priority: Normal | Milestone: Bro1.6 Component: Website / Wiki | Version: Keywords: | ----------------------------+-------------------- There's some BinPAC documentation in the old Wiki that we should move over. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/478> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 10 months

[Bro-Dev] #754: Complete implementation of switch statement

by Bro Tracker

#754: Complete implementation of switch statement ----------------------+------------------------ Reporter: seth | Owner: Type: Task | Status: new Priority: Normal | Milestone: Bro2.1 Component: Bro | Version: git/master Keywords: language | ----------------------+------------------------ The switch statement is stubbed out in the parser but it's not completely implemented. I'd like to have it available, there are several use cases where it would be handy to have. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/754> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 10 months

[Bro-Dev] #730: Find and fix tcp sequence counting bugs

by Bro Tracker

#730: Find and fix tcp sequence counting bugs ---------------------+-------------------- Reporter: seth | Owner: Type: Problem | Status: new Priority: Normal | Milestone: Bro2.1 Component: Bro | Version: Keywords: | ---------------------+-------------------- Sometimes the code that watches for tcp sequence wrap around will trigger erroneously and the payload value will be grossly misrepresented in the c$(resp|orig)$size fields. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/730> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 11 months

[Bro-Dev] #660: Initializing a table with a record as an index does not work

by Bro Tracker

#660: Initializing a table with a record as an index does not work --------------------+--------------------- Reporter: amannb | Type: Problem Status: new | Priority: Normal Milestone: | Component: Bro Version: | Keywords: --------------------+--------------------- The following code {{{ type irecord: record { resp_h: addr; }; global my_table: table[irecord] of int = { [[$resp_h=1.2.3.4]] = 12, }; }}} results in an error: {{{ error in ./bug2.bro, line 7: illegal initializer ([[$resp_h=1.2.3.4]] = 12) }}} It probably should return an initialized table. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/660> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 11 months

[Bro-Dev] #474: &raw_output turns null values into \0

by Bro Tracker

#474: &raw_output turns null values into \0 ---------------------+-------------------- Reporter: seth | Owner: Type: Problem | Status: new Priority: Normal | Milestone: Bro1.6 Component: Bro | Version: Keywords: | ---------------------+-------------------- Files with the raw_output attribute shouldn't do any interpretation to the data. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/474> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 11 months

[Bro-Dev] #690: GTP de-tunneling

by Bro Tracker

#690: GTP de-tunneling ------------------------+--------------------- Reporter: robin | Type: Problem Status: new | Priority: Normal Milestone: 2.1 | Component: Bro Version: git/master | ------------------------+--------------------- ----- Forwarded message from "Langer, Carsten (NSN - DE/Duesseldorf)" ----- From: "Langer, Carsten (NSN - DE/Duesseldorf)" [...] I lately developed a GTP (GPRS Tunneling Protocol) de-tunneling functionality for bro-ids, which I want to share with you in the hope that you might find it helpful. [...] Please find attached a patched version of the Sessions.cc, where from line 601 to 701 I have introduced the de-GTP stuff. This is based on bro-ids v1.5.3. I found that patching this one single location was good enough for my purpose. It works for me, however I could only test it against a couple of network traces that I have, so if you are interested to re-use the patch, please give it a try against other sets of data as well. I added 3 weird-warnings (lines 614, 674, 691) if something goes wrong within the patch, but haven't updated anything in the weird.bro script. [...] As I'm not using the bro-ids for network security analysis but for application performance analysis, [...] I did not take any measures against recursive GTP tunnels. ----- End forwarded message ----- [attachment:"Sessions_patched_for_gtp-detunneling.cc"] -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/690> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 11 months

[Bro-Dev] #779: missing values cause bro to crash when used inside of a 'when' statement.

by Bro Tracker

#779: missing values cause bro to crash when used inside of a 'when' statement. ------------------------+--------------------------------------- Reporter: justin | Type: Problem Status: new | Priority: Normal Milestone: | Component: Bro Version: git/master | Keywords: when InterpreterException ------------------------+--------------------------------------- Simplest test case: {{{ event bro_init() { local loc: geo_location; when (local hostname = lookup_addr(127.0.0.1)){ print "Location", loc$country_code; print "ok"; terminate(); } } }}} gives: {{{ terminate called after throwing an instance of 'InterpreterException' }}} outside of the when block, reporter.log would get: {{{ Reporter::ERROR field value missing [loc$country_code] }}} -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/779> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 12 months

[Bro-Dev] #741: Remove HTTP verbs from HTTP analyzer

by Bro Tracker

#741: Remove HTTP verbs from HTTP analyzer ---------------------+-------------------- Reporter: seth | Owner: Type: Problem | Status: new Priority: Normal | Milestone: Bro2.1 Component: Bro | Version: Keywords: | ---------------------+-------------------- We should remove the HTTP verbs (methods) from the HTTP analyzer and just parse out whatever the client gives. Nonstandard verbs will cause the client side of the analyzer to completely not work which is clearly not optimal. Making this change will remove a couple of for loops from the HTTP analyzer too. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/741> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

7 years, 12 months

[Bro-Dev] #696: broctl dumps python traceback information when bro is communicating with other worker nodes and quits

by Bro Tracker

#696: broctl dumps python traceback information when bro is communicating with other worker nodes and quits ---------------------+--------------------- Reporter: aashish | Type: Problem Status: new | Priority: Normal Milestone: | Component: Bro Version: 1.5.3 | Keywords: ---------------------+--------------------- broctl dumps python traceback information when bro is communicating (ssh) with other worker nodes and this continues until the ssh connection is over. $ broctl check Traceback (most recent call last): File "/home/users/bro/cluster/bin/broctl", line 726, in <module> loop.onecmd(line) File "/usr/local/lib/python2.6/cmd.py", line 219, in onecmd return func(arg) File "/home/users/bro/cluster/bin/broctl", line 359, in do_check self.lock() File "/home/users/bro/cluster/bin/broctl", line 96, in lock if not util.lock(): File "/home/users/bro/cluster/lib/broctl/BroControl/util.py", line 180, in lock if do_ouput: NameError: global name 'do_ouput' is not defined Process info as follows: [bro@host]$ ps auxwww | fgrep bro bro 12704 1.6 0.2 10208 6676 ?? D 2:30PM 0:01.85 python /home/users/bro/cluster/bin/broctl cron bro 12613 0.0 0.1 4464 1716 ?? Is 2:30PM 0:00.01 /bin/csh -c /home/users/bro/cluster/bin/broctl cron bro 12743 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c sh bro 12745 0.0 0.0 3464 1120 ?? I 2:30PM 0:00.00 sh bro 12755 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.01 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-proxy sh bro 12757 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-proxy sh bro 12766 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-01 sh bro 12768 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-01 sh bro 12772 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-10 sh bro 12774 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-10 sh bro 12779 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-02 sh bro 12781 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-02 sh bro 12793 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-03 sh bro 12795 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-03 sh bro 12798 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-04 sh bro 12800 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-04 sh bro 12803 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-05 sh bro 12805 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.04 ssh -o ConnectTimeout=30 -l bro bc2-05 sh bro 12815 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-06 sh bro 12817 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.04 ssh -o ConnectTimeout=30 -l bro bc2-06 sh bro 12820 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-07 sh bro 12822 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-07 sh bro 12825 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-08 sh bro 12827 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-08 sh bro 12830 0.0 0.0 3464 1120 ?? Is 2:30PM 0:00.00 /bin/sh -c ssh -o ConnectTimeout=30 -l bro bc2-09 sh bro 12831 0.0 0.1 5560 2644 ?? I 2:30PM 0:00.03 ssh -o ConnectTimeout=30 -l bro bc2-09 sh -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/696> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

8 years

[Bro-Dev] #579: Syslog logging writer

by Bro Tracker

#579: Syslog logging writer ---------------------+------------------------ Reporter: seth | Owner: Type: Problem | Status: new Priority: Normal | Milestone: Bro1.7 Component: Bro | Version: git/master Keywords: | ---------------------+------------------------ Martin has completely convinced me of the need for this. I don't know about timeline we should put on it though. The one thought I have about it is that it needs to use TCP due to extremely long lines that Bro logs tend to have. I think it would be ok for it to have the same output rendering that the LogAscii writer has. -- Ticket URL: <http://tracker.bro-ids.org/bro/ticket/579> Bro Tracker <http://tracker.bro-ids.org/bro> Bro Issue Tracker

8 years, 1 month

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

zeek-dev June 2012