28 Jan
2011
28 Jan
'11
10:20 a.m.
#372: bifcl cannot pass specific enum types
---------------------+--------------------
Reporter: robin | Owner:
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version:
Keywords: |
---------------------+--------------------
From Seth:
I have an enum named Logging::ID, and I want it to be
the first argument
in this BiF…
{{{function logging_log%(id: Logging::ID, rec: any%):
bool}}}
From Gregor:
bifcl supports enums (it just casts them as a
"neutral" Val*, same as
for record types). So it would just be a matter of telling bifcl to
accept the Namespace::Type name syntax. That should be it.
The C part doesn't really care about the type. It's all a "netural"
Val*. The type is only used for the policy file and type checking.
EnumType and EnumVal should make accessing the enum's value relatively
easy. I'm using that in my re-working of the NFS analyzer. Let me know
if you want details.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/372>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
28 Jan
28 Jan
11:22 a.m.
#372: bifcl cannot pass specific enum types
----------------------+---------------------
Reporter: robin | Owner:
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version:
Resolution: | Keywords: logging
----------------------+---------------------
Changes (by seth):
* keywords: => logging
--
Ticket URL: <http://tracker.icir.org/bro/ticket/372#comment:1>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
3 Feb
3 Feb
2:41 p.m.
#372: bifcl cannot pass specific enum types
----------------------+---------------------
Reporter: robin | Owner:
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version:
Resolution: | Keywords: logging
----------------------+---------------------
Comment (by robin):
Attaching a tiny patch that teaches bifcl to accept scoped names. That
seems to do the trick already.
Gregor, can you post short example of how you're then accessing the enum
for reference?
--
Ticket URL: <http://tracker.icir.org/bro/ticket/372#comment:2>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
4 Feb
4 Feb
4:04 p.m.
#372: bifcl cannot pass specific enum types
----------------------+---------------------
Reporter: robin | Owner:
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version:
Resolution: | Keywords: logging
----------------------+---------------------
Comment (by gregor):
{{{
#!rst
How use enums in C++, bif, and .bro
-----------------------------------
That's actually pretty straight forward. The functionality has been in Bro
for quite a while but it has been scarcely used.
In ``const.bif`` you can define enums. These are then available in the
policy layer as well
as in the C++/bif layer. E.g.,::
enum foobar %{
foo,
bar
%}
Will make the enum ``foobar`` available in the policy layer.
For the C++ layer the bif will automatically the following code that is
included in ``NetVar.h`` (and also the necessary initialization code)::
extern EnumType* enum_foobar;
namespace BroEnum { enum foobar {
foo,
bar
};}
Some code snippets showing how you can make use of those in C++ and bif::
BroEnum::foobar x;
x = BroEnum::foo;
if (x == BroEnum::bar)
do_something();
....
EnumVal *y = new EnumVal(x, enum_foobar);
EnumVal *z = new EnumVal(BroEnum::bar, enum_foobar);
// y and z can now be passed to an event or returned from a bif.
// In the policy script the type would be foobar.
}}}
--
Ticket URL: <http://tracker.icir.org/bro/ticket/372#comment:3>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
3948
days inactive
3956
days old
3 comments
1 participants
participants (1)
-
Bro Tracker