[Oisf-devel] [COMMIT] OISF branch, master, updated. suricata-2.0beta1-274-ga26243a
noreply at openinfosecfoundation.org
noreply at openinfosecfoundation.org
Wed Oct 9 11:46:38 UTC 2013
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "OISF".
The branch, master has been updated
via a26243a23c4a99330b8f5dca6bdc148b4ef32eb0 (commit)
via b24fb72247992e63586b4e9926ce35ce2904caaf (commit)
via 83a72d50dd34266fe5b52e497e3405b398c54eb0 (commit)
via 1ea5d27508f09fd202838041556d5efe59e43ac9 (commit)
via 836bad85a47f4e9f5f34472534c3e77bd39b3dc9 (commit)
via 87edd2ade9e84423b77308a369c32fd4b693806e (commit)
via 73be9d3ef7a6b26aaa3c228c59537c415ea7de61 (commit)
from 1d18155a169418e129ffad1dbb2a764a98fd41e3 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit a26243a23c4a99330b8f5dca6bdc148b4ef32eb0
Author: Victor Julien <victor at inliniac.net>
Date: Wed Oct 9 13:45:55 2013 +0200
Clean up rule reload logging
commit b24fb72247992e63586b4e9926ce35ce2904caaf
Author: Anoop Saldanha <anoopsaldanha at gmail.com>
Date: Fri Oct 4 21:51:33 2013 +0530
fix for bug #987.
We don't support jabber protocol detection atm. Disable the code check
inside suricata to check if jabber protocol detection is enabled in the
yaml file.
Also updated an error log message for app layer.
commit 83a72d50dd34266fe5b52e497e3405b398c54eb0
Author: Anoop Saldanha <anoopsaldanha at gmail.com>
Date: Tue Oct 8 21:41:17 2013 +0530
API renaming/beautification.
commit 1ea5d27508f09fd202838041556d5efe59e43ac9
Author: Anoop Saldanha <anoopsaldanha at gmail.com>
Date: Thu Oct 3 10:12:54 2013 +0530
Fix for bug #989.
In case of recursive call to protocol detection from within protocol
detection, and the recursively invoked stream still hasn't been ack'ed
yet, protocol detection doesn't take place. In such cases we will end up
still calling the app layer with the wrong direction data. Introduce a
check to not call app layer with wrong direction data.
When sockets are re-used reset all relevant vars correctly.
This commit fixes a bug where we were not reseting app proto detection
vars.
While fixing #989, we discovered some other bugs which have also been
fixed, or rather some features which are now updated. One of the feature
update being if we recieve wrong direction data first, we don't reset the
protocol values for the flow. We let the flow retain the detected
values.
Unittests have been modified to accomodate the above change.
commit 836bad85a47f4e9f5f34472534c3e77bd39b3dc9
Author: Anoop Saldanha <anoopsaldanha at gmail.com>
Date: Thu Oct 3 10:10:11 2013 +0530
Reset app layer processed flag for segments that have been sent for proto
detection, but we failed to figure out the proto.
Updated a unittest to reflect the above change.
commit 87edd2ade9e84423b77308a369c32fd4b693806e
Author: Anoop Saldanha <anoopsaldanha at gmail.com>
Date: Tue Oct 8 20:52:06 2013 +0530
Inside PP parser, we were using the return value from DetectPortParse as
the ip_proto value, which is wrong. We have fixed this now.
commit 73be9d3ef7a6b26aaa3c228c59537c415ea7de61
Author: Anoop Saldanha <anoopsaldanha at gmail.com>
Date: Tue Oct 1 21:13:07 2013 +0530
Update ssl parser protocol detection pattern strings.
-----------------------------------------------------------------------
Summary of changes:
src/app-layer-detect-proto.h | 3 ++
src/app-layer-htp.c | 5 ++-
src/app-layer-parser.c | 37 ++++++++++++++++----
src/app-layer-ssl.c | 7 ++++
src/app-layer.c | 77 ++++++++++++++++++++++++++++++++++--------
src/detect-engine.c | 15 +++-----
src/flow-timeout.c | 8 ++--
src/stream-tcp-private.h | 2 +
src/stream-tcp-reassemble.c | 8 ++++-
src/stream-tcp.c | 2 +
src/stream-tcp.h | 2 +-
11 files changed, 129 insertions(+), 37 deletions(-)
hooks/post-receive
--
OISF
More information about the Oisf-devel
mailing list