[Snort-users] Anyone else seen this?

Kevin Brown Kevin.M.Brown at ...1022...
Mon Jun 18 16:38:51 EDT 2001

I guess from the lack of response that I'm the only one who is having this
problem with snort, or does snort log based on the time the packet has
stored in it and from that I'm getting the weird data (like Alerts from the
year 2041).

-----Original Message-----
From: Kevin Brown [mailto:Kevin.M.Brown at ...1022...]
Sent: Thursday, June 14, 2001 15:43
To: 'snort-users at lists.sourceforge.net'
Subject: [Snort-users] Anyone else seen this?

I currently have just one sensor on the network (that I control) logging to
a Postgresql (7.1) database.  I have been noticing that the dates being put
in the database do not always correspond with the actual time and was
wondering if anyone else is having this problem.

-*> Snort! <*-
Version 1.8-beta5 (Build 24)
on Solaris 8 (Netra T1 AC200, 500MHz Sparc)

Remote Database, Postgresql 7.1 running on RH6.2 kernel 2.2.16
Schema 102
Acid .9.6b10

Attached is a sampling of the output from the following SQL queries

snort=# select sid,cid,timestamp from event ORDER BY timestamp DESC;
snort=# select sid,cid,timestamp from event ORDER BY cid DESC;

Any help would be much appreciated.

Begin Geek Code;
$m=(11,10,116,100,11,122,20,100)[$_/16%8])&110;$t^=(72, at z=(64,72,$a^=12*($_%
-2?0:$m&17)),$b^=$_%64?12:0, at z)[$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$
=5;$_=unxb24,join"", at b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$
(($h>>=8)+=$f+(~$g&$t))for at ...1981...[128..$#a]}print+x"C*", at a}';s/x/pack+/g;eval

More information about the Snort-users mailing list