[Bro] bad record initializer (between Bro 2.3 and 2.4)

Azoff, Justin S jazoff at illinois.edu
Mon Nov 14 06:27:03 PST 2016


Does it work if you use 'count' instead of 'int' ?
-- 
- Justin Azoff

> On Nov 13, 2016, at 4:54 PM, Mike Dopheide <dopheide at gmail.com> wrote:
> 
> I've isolated the problem to using an 'int' in a record type as seen below.  According to try.bro.org the it started to fail between versions 2.3 and 2.4.  If you change the boothnum to a string and put quotes around it, everything is fine.
> 
> Was there a syntax change that requires something around the int when it's initialized?
> 
> -Dop
> 
> 
> @load base/frameworks/input
> @load base/frameworks/notice
> 
> # add some stuff to generate notices from our test traffic:
> @load misc/scan
> @load misc/detect-traceroute
> @load protocols/ssh/detect-bruteforcing
> 
> module Conn;
> 
> export {
> 
>     type vlandata: record {
>         booth: string &log &optional;
>         boothnum: int &log &optional;
>     };
> 
>     global vlanlist: table[int] of vlandata = table() &redef;
> 
> }
> 
> redef vlanlist += {
>     [11] = [$booth="darkspace"],
>     [18] = [$booth="ASDF",$boothnum=1743]
> };
> 
> 
> _______________________________________________
> Bro mailing list
> bro at bro-ids.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/bro




More information about the Bro mailing list