[
https://bro-tracker.atlassian.net/browse/BIT-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seth Hall updated BIT-1159:
---------------------------
Attachment: signature.asc
I actually avoid the parse time name resolution and tend toward runtime lookups
with the dns bifs going on the assumption that Bro is an extremely long lived
process and I’d rather not rely on a name lookup that happened a (potentially)
long time ago.
> type checking inconsistencies
> -----------------------------
>
> Key: BIT-1159
> URL: https://bro-tracker.atlassian.net/browse/BIT-1159
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Bro
> Affects Versions: git/master, 2.2
> Reporter: Justin Azoff
> Assignee: Jon Siwek
> Priority: Low
> Labels: language
> Attachments: signature.asc, signature.asc
>
>
> If you try to compare a count to a port directly, you get the following:
> {code}
> operands must be of the same type (1500/tcp < 2000)
> {code}
> but if you have a record, and mixup the types like so, it silently fails:
> {code}
> type PortRange: record {
> min: port &default=1/tcp;
> max: port &default=65535/tcp;
> };
> global pr = PortRange($min=1000,$max=2000);
> #CORRECT: global pr = PortRange($min=1000/tcp,$max=2000/tcp);
> event bro_init()
> {
> print (pr$min <= 1500/tcp && 1500/tcp < pr$max) ? "OK" : "NOTOK";
> }
> {code}
> {code}
> $ bro a.bro
> NOTOK
> {code}
--
This message was sent by Atlassian JIRA
(v6.2-OD-10-004-WN#6253)
_______________________________________________
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
