If this is happening alot, it might be possible to run tcpdump or
Wireshark until the bare byte alerts show up in BASE and then prune the
pcap down to only include the TCP sessions (and try to include the
entire HTTP conversation) that contain the alerted on packets. Then run
the pcap against Snort to ensure that the pcap generates the alerts.
Julio Cesar Gazquez wrote:
El Jueves 21 Febrero 2008 16:46:08 escribió:
That doesn't really help. There is no indication of any bare byte
encoding here.
Exactly. It also seems to happen with other alerts, where the packet details
I
got don't match the intent of the alert. But bare byte encoding alerts seems
to be the most evident case.
Yet I'm not sure if the alerts are wrong, or I'm getting packets that don't
match the alerts.
The basic check in Snort looks for a byte > 0x7F. It
would be very helpful if you could post a pcap. Make sure it fires on
the bare byte encoding by running it against Snort in read mode.
I just realized I don't have pcap logs, but unified logs, as I'm using
Barnyard, so I can't read the logs back.
I guess I should run an extra snort instance in order to get logs useful for
debugging...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users
