| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The capability has been added for module to specify that they do not
like being unloaded.
related bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=222
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
|\ \ \ \ \
| |/ / / /
|/| | / /
| | |/ /
| |/| |
| | | |
| | | | |
Conflicts:
ChangeLog
configure.ac
doc/manual.html
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
a problem in the current testbench is that it depends on the locally
assigned system name. We have changed the default to the most common
default value. However, in the long term we need to fix this (and will
do so via a preloaded DNS cache, which we do not yet have!)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this could happen if multiple rulesets were used and some output batches
contained messages belonging to more than one ruleset.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=226
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=218
|
| | | |
| | | |
| | | |
| | | |
| | | | |
currently it generates only the power set, more work to do to make it
a real config generator.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
as well as potentially in a number of other places where MsgDup() was
used. This only happened when the imudp input module was used and it
depended on name resolution not yet had taken place. In other words,
this was a strange problem that could lead to hard to diagnose
instability. So if you experience instability, chances are good that
this fix will help.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
this could happen if multiple rulesets were used and some output batches
contained messages belonging to more than one ruleset.
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=226
fixes: http://bugzilla.adiscon.com/show_bug.cgi?id=218
|
| | | | |
|
|\ \ \ \ |
|
| |\ \ \ \ |
|
| | | | | | |
|
| | |_|/ /
| |/| | | |
|
|\ \ \ \ \
| |_|/ / /
|/| | / /
| | |/ /
| |/| | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | | |
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=225
|
| |/ /
|/| | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
control character escaping is now also being tested
|
| | |
| | |
| | |
| | |
| | | |
The previous fix left variable lenMsg in an inconsistent state when
sanitization actually happend. This could lead to message truncation.
|
| | |
| | |
| | |
| | |
| | | |
This also causes problems when NUL characters are present inside
the message (as is the case with spamd).
|
| | | |
|
| | |
| | |
| | |
| | | |
thanks to Michael Biebl for alterting me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This was a regression from the imuxsock partial rewrite. Happened
because the message is no longer run through the standard parsers.
Now imuxsock does this sanitization itself.
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=224
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
we do this directly in the beta because a) it does not affect existing
functionality and b) one may argue that this missing functionality is
close to a bug.
|
|\ \ \ |
|
| |\| | |
|
| | | |
| | | |
| | | |
| | | | |
... what actually was a left-over. Java is no longer required.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is considered cosmetic as multiple threads tried to write exactly
the same value into the same memory location without sync. The method
has been changed so this can no longer happen.
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
this occured only on some platforms/compilers. thanks to Dražen Kačar
for the fix
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
non-existance and other detectable problems are now reported,
and the work directory is NOT set in this case
|
| | |
| | |
| | |
| | |
| | |
| | | |
circumstances
This has now been solved, at least for common situations.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
...when in disk-assisted mode. This especially affected imfile, which
created unnecessarily queue files if a large set of input file data was
to process.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Support for multiple unix sockets and activation in forking mode
Signed-off-by: Marius Tomaschewski <mt@suse.de>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
when removing text from the message, decrement the length when you increment
the pointer through the message. there were a number of places where this was
missed.
Signed-off-by: Rainer Gerhards <rgerhards@adiscon.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Thanks to Peter Eisentraut for reporting and analysing this problem.
bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=221
|