Project

General

Profile

0.8.0

closed

12/31/2009

First public release

100%

24 issues   (24 closed — 0 open)

Time tracking
Estimated time 45.00 hours
Issues by
Bug

23/23
Feature

1/1
Related issues
Bug #4: DetectBytetestMatch: Error extracting 8 bytes of string data: 0 on web responses Actions
Bug #5: Multi-line rules do not work in the OISF engine. Actions
Bug #6: The Logging subsystem does not perform proper bounds checking on msg strings Actions
Bug #7: Unifed* File Rollover Causes Segmentation Fault Actions
Bug #8: engine fails to match when fast_pattern rule is inspecting the same payload as a non-fast_pattern rule Actions
Bug #9: rules containing the same content match do not fire. Actions
Bug #10: flags:0; alerts when it shoudn't Actions
Bug #11: negated content matches don't work when ! is outside of "" Actions
Bug #12: Negated pcre treated as a normal match Actions
Bug #13: Depth is not modified by offset Actions
Bug #16: rand needs to be seeded when used in the engine Actions
Bug #17: Segv inside of chunked http response body parsing Actions
Bug #18: unclear error message when user fails to specify a conf file Actions
Bug #20: Engine segv's when proccessing gzip'd http responses on 64-bit hosts. Actions
Bug #21: Segv when trying processing rule with http_cookie modifier but no cookie header present in packet. Actions
Bug #22: Engine infinitely prints whitespace when processing the smb traffic in the attached pcap. Actions
Bug #23: Segv occurs occasionally inside of DetectHttpCookieMatch Actions
Bug #28: Spaces between content/uricontent: and "match" are not handled properly Actions
Bug #29: Abort inside of StreamTcpSegmentDataReplace when processing the attached pcap Actions
Bug #30: strip newline(s) from signature line before passing it to the parser Actions
Bug #33: We should not abort() inside of the stream handler Actions
Bug #34: Engine lockup inside of DCERPCParse when processing the attached pcap Actions
Bug #41: Processing the attached pcap causes the engine to segv inside of AppLayerHandleMsg Actions
Feature #2: The engine needs the ability to run in daemon mode. Actions

Also available in: TXT