[Prelude Hybrid IDS] #247: bypass uninsertable alerts

"Prelude Hybrid IDS" <[email protected]>
Newsgroups gmane.comp.security.ids.prelude.devel
Message-ID <[email protected]>
#247: bypass uninsertable alerts
---------------------------------+------------------------------------------
 Reporter:  [email protected]  |       Owner:  yoann
     Type:  defect               |      Status:  new  
 Priority:  normal               |   Milestone:       
Component:  prelude-manager      |     Version:  0.9  
 Severity:  critical             |    Keywords:       
---------------------------------+------------------------------------------
 In some cases Ive seen events where the sudo rule and some of the others
 excide the database field size limitations in this case there is a syslog
 message
 {{{
 could not insert message into database: ERROR:  value too long for type
 character varying(255)
 }}}

 this causes the prelude-manager creates an alert file in /var/spool
 /prelude-manager/failover/db[default]/ then it queues all of the following
 alerts into that directory until it exceeds a quota and starts deleting
 alerts. this causes an outage untill either the offending alert is found
 and manualy deleted of until it automatically deletes the alert and usualy
 several others.

 {{{
  - Plugin db[default]: flushing 16870 message (4321 erased due to
 quota)...
 }}}


 there are two possible ways the prelude-manager could handle this better

 1) in the case of this message or other field constraint errors the
 offending alert could be written to a different directory where it could
 be analyzed latter and an alert generated by the prelude-manager about the
 file created. the prelude-manager could then continue to process alerts
 right away.

 2)The prelude manager could always try to insert newly recived alerts into
 the database first before putting them into the failover directory in the
 case of a faulted database status.

 Since the alerts contain thir own time stamp the order in which they are
 inserted does not need to be preserved so either solution would work
 although the first is preferable as it would notify the user to a problem.

-- 
Ticket URL: <https://trac.prelude-ids.org/ticket/247>
Prelude Hybrid IDS <http://www.prelude-ids.org>
The Prelude Hybrid Intrusion Detection System suite
_______________________________________________
Prelude-devel site list
[email protected]
http://www.prelude-ids.org/mailman/listinfo/prelude-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.