|To:||Pablo Neira <pablo@xxxxxxxxxxx>|
|Subject:||Re: [RFC] textsearch infrastructure et al v2|
|From:||Pablo Neira <pablo@xxxxxxxxxxx>|
|Date:||Sat, 28 May 2005 14:58:51 +0200|
|Cc:||Thomas Graf <tgraf@xxxxxxx>, jamal <hadi@xxxxxxxxxx>, netdev@xxxxxxxxxxx|
|References:||<20050527224725.GG15391@xxxxxxxxxxxxxx> <1117281581.6251.68.camel@xxxxxxxxxxxxxxxxxxxxx> <20050528123542.GR15391@xxxxxxxxxxxxxx> <42986A85.9060001@xxxxxxxxxxx>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105 Debian/1.7.5-1|
Pablo Neira wrote:
Same for my infrastructure with the difference that libqsearch uses a single input buffer so no chance for non-linear data.hm, i don't understand quite well, i bet that libqsearch was already fragment-aware. Anyway the main difference is that libqsearch wasn't designed to be used in user space so, for example, it needed a complete rework to reduce dynamic memory allocations.
sorry, i meant '/s/wasn't/was/g'. libqsearch was designed to be used by snort.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [RFC] textsearch infrastructure et al v2, Pablo Neira|
|Next by Date:||Re: [PATCH] r8169: support restricting speed+duplex in autonegotiation, Richard Dawe|
|Previous by Thread:||Re: [RFC] textsearch infrastructure et al v2, Pablo Neira|
|Next by Thread:||Re: [RFC] textsearch infrastructure et al v2, Thomas Graf|
|Indexes:||[Date] [Thread] [Top] [All Lists]|