[Bro-Dev] Were to define global const (const.bif VS. bro.init + NetVar.{cc|h}

Vern Paxson vern at icir.org
Fri Dec 10 18:12:34 PST 2010


>  * in const.bif OR in bro.init and NetVar.{h|cc}
>  * in const.bif OR in a specific .bro script and NetVar.{h|cc}
> 
> it seems that all three options are used. I was wondering whether it
> makes sense to unify them wrt the general Bro documentation / cleanup
> efforts.

I believe const.bif is the right way to go.  It's cleaner than the others,
but we never managed to consistently only use it (much less migrate the
older stuff over to it).

> For analyzer specific configuration options (i.e., ones that are defined
> in a particular policy script) be more logical to keep them in the
> policy script. (Or they could still be defined in const.bif and then
> just redef'ed in the policy script, so that users who look at the policy
> script are aware that the const exists)

That latter makes sense to me.

		Vern


More information about the bro-dev mailing list