#340: Cleanup: unify where global consts are defined (access from policy layer
and event engine)
-----------------------------+--------------------
Reporter: gregor | Owner:
Type: Feature Request | Status: new
Priority: Low | Milestone: Bro1.6
Component: Bro | Version:
Keywords: |
-----------------------------+--------------------
{{{
#!rst
Global ``const``'s that are accessible from the policy layer and event
engine (e.g., to configure features) are currently defined in different
ways:
1. in ``bro.init`` and ``NetVar.{cc|h}``
2. in a specific .bro policy script and ``NetVar.{cc|h}``
3. in ``const.bif``
According to our discussion on bro-dev, we should change it to only use
``const.bif``.
For case 2. we should add a ``redef`` in the .bro policy scripts, so that
users looking at the script see that the const exists (TODO: how to best
auto-doucment these).
Setting milestone to 1.6 as it seems this can be done together with the
general policy script overhaul, but can also be pushed backed.
}}}
--
Ticket URL: <http://tracker.icir.org/bro/ticket/340>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#357: Only log missing support for libgeoip a single time.
---------------------+------------------------
Reporter: seth | Owner:
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version: git/master
Keywords: sprint |
---------------------+------------------------
I've seen too many people with logs that are full of messages indicating
no support for libgeoip.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/357>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#421: Initialize set/table field in records.
--------------------+--------------------
Reporter: robin | Owner: robin
Type: Task | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version:
Keywords: |
--------------------+--------------------
We should initialize set/tables in instantiated records to empty values if
they don't have an &optional attribute.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/421>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#412: Port the istate tests to btes
--------------------+--------------------
Reporter: robin | Owner: robin
Type: Task | Status: new
Priority: Normal | Milestone: Bro1.6
Component: Bro | Version:
Keywords: |
--------------------+--------------------
They are in testings/istate.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/412>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#430: Build error in LogMgr.cc
----------------------+-----------------------
Reporter: appleman | Owner:
Type: Problem | Status: new
Priority: Normal | Milestone:
Component: Bro | Version: git/topic
Keywords: |
----------------------+-----------------------
I cloned the repository as master and built bro. I then did ...
git checkout topic/robin/logging-internals
make
... and it died with the following errors:
[ 16%] Building CXX object src/CMakeFiles/bro.dir/LogMgr.cc.o
/home/appleman/bro/trunk/scripts/bro/src/LogMgr.cc: In member function
‘bool LogMgr::AddFilter(EnumVal*, RecordVal*)’:
/home/appleman/bro/trunk/scripts/bro/src/LogMgr.cc:691: error: ‘transform’
is not a member of ‘std’
make[3]: *** [src/CMakeFiles/bro.dir/LogMgr.cc.o] Error 1
make[3]: Leaving directory `/home/appleman/bro/trunk/scripts/bro/build'
make[2]: *** [src/CMakeFiles/bro.dir/all] Error 2
make[2]: Leaving directory `/home/appleman/bro/trunk/scripts/bro/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/appleman/bro/trunk/scripts/bro/build'
make: *** [all] Error 2
My gcc version is 4.4.3
Problem was resolved for me by adding
#include <algorithm>
to LogMgr.cc
--
Ticket URL: <http://tracker.icir.org/bro/ticket/430>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#401: broctl crash reports should display size of core dump
------------------------+--------------------
Reporter: seth | Owner: robin
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: BroControl | Version:
Keywords: |
------------------------+--------------------
This would help with remote debugging since it would become easier in some
cases to determine the result of a crash if the crash is due to memory
exhaustion. One case in particular that it would be really helpful for is
someone running 32-bit Bro on a 64-bit platform since the crash (i think)
will always happen right at 4GB.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/401>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#390: Problem with _logStats method in BroControl
------------------------+------------------------
Reporter: seth | Owner: robin
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: BroControl | Version: git/master
Keywords: |
------------------------+------------------------
In some installations (I don't know what criteria yet), the _logStats
method will cause the cron command to never finish.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/390>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#370: Plugin interface for BroControl
-----------------------------+--------------------
Reporter: seth | Owner: robin
Type: Feature Request | Status: new
Priority: Normal | Milestone: Bro1.6
Component: BroControl | Version:
Keywords: |
-----------------------------+--------------------
Features that a first version of the plugin interface should have...
* Hooks to execute external scripts before and after start, stop, and
install.
* Mechanism for plugin scripts to provide feedback to BroControl. Maybe
just succeed or fail+message would be enough?
* Setting options for plugins in broctl.cfg. Maybe set ENV vars when
running scripts?
Currently, I'm thinking that using a naming convention for files in
<prefix>/share/broctl/plugins would work for installing plugins. Names
like this: post-install-plugin1 or pre-start-plugin2. That would provide
BroControl enough information to know which configuration options to set
in the environment when executing those scripts and when they are supposed
to be executed.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/370>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#361: Copy Bro binary only when in NFS mode
------------------------+------------------------
Reporter: robin | Owner: robin
Type: Task | Status: new
Priority: Normal | Milestone: Bro1.6
Component: BroControl | Version: git/master
------------------------+------------------------
Currently, BroControl copies the bro binary to all clients' spool
directory, and then runs it from there. While that avoids problems
when the Bro installation is on NFS, it can cause trouble in other
contexts (like capabilities set for the binary to be lost; and I
think we had more in the past I don't recall right now).
So, the solution seems to be to avoid the copy unless in NFS mode.
We could also revisit whether we want to keep supporting runnign
from NFS at all, but generall I'd like to do so.
--
Ticket URL: <http://tracker.icir.org/bro/ticket/361>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
#337: BroCtl's top has trouble with large values
------------------------+------------------------
Reporter: robin | Owner: robin
Type: Problem | Status: new
Priority: Normal | Milestone: Bro1.6
Component: BroControl | Version: git/master
------------------------+------------------------
From Craig:
File "/home/users/bro/bro-151/lib/broctl/BroControl/control.py", line
588, in getTopOutput
d["vsize"] = int(p[1])
ValueError: invalid literal for int(): 2.17684e+09
Here's a possible fix for this:
d["vsize"] = int(float(p[1]))
Craig
fun 2 % !!
ipython
Python 2.6.6 (r266:84292, Sep 29 2010, 08:18:31)
Type "copyright", "credits" or "license" for more information.
IPython 0.10.1 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.
In [1]: p = [ 'foo', '2.17684e+09' ]
In [2]: print type(p[1])
<type 'str'>
In [3]: print p[1]
2.17684e+09
In [4]: d = {}
In [5]: d["vsize"] = int(float(p[1]))
In [6]: print d["vsize"]
2176840000
In [7]: print type(d["vsize"])
<type 'int'>
--
Ticket URL: <http://tracker.icir.org/bro/ticket/337>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker