[Snort-users] why old libnet?
rjenkins at ...12829...
Mon Mar 28 09:23:54 EST 2005
I have seen that flexresp works very well in blocking outbound P2P and
chat programs. I would like seeing more advancement in this feature.
From: snort-users-admin at lists.sourceforge.net
[mailto:snort-users-admin at lists.sourceforge.net] On Behalf Of Matt
Sent: Monday, March 28, 2005 11:16 AM
To: snort-users at lists.sourceforge.net
Subject: Re: [Snort-users] why old libnet?
Florin Andrei wrote:
>What is the reason why Snort can only use the old, deprecated,
>Since other apps are likely to use already the newer, supported,
>libnet-1.1, there might be conflicts on systems using both types of
Really, the only part of snort that uses libnet is flexresp. If you're
not using flexresp, snort shouldn't be looking for libnet.
As for flexresp itself, it's getting to be a bit on the "aged" side. I
know one of the SF guys (Chris? Jeff?) was working on a "flexresp2", but
it looks like 2.3.2 still only includes the old version.
I also think that while Flexresp is useful, people believe it to be more
useful than it is. Flexresp is really pretty limited. It's useful
against automated probes, but really only acts as a hurdle to jump over
for a skilled manual attack. Even against automated probes, flexresp
isn't 100% effective, since it relies on being able to advance the TCP
sequence number first. Flexresp uses some tricks to give it a major
advantage, but it still boils down to being a race condition.
Now that snort has an official inline module, you really should consider
using it instead of flexresp if inline is feasible in your network and
on your platform.
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Snort-users mailing list
Snort-users at lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
Snort-users list archive:
More information about the Snort-users