Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Snort-Users
[Top] [All Lists]

[Snort-users] SEGV fault with Solaris 9/Snort 2.6.0RC1

Subject: [Snort-users] SEGV fault with Solaris 9/Snort 2.6.0RC1
Date: Tue, 25 Apr 2006 09:41:56 -0400
Hi -

I'm just starting to test version 2.6.0RC, and I'm getting a SEGV when trying 
to parse the "output directive" in my snort.conf file.

/var/adm/messages:

Apr 24 16:14:43 outcast snort[11235]: [ID 702911 daemon.notice] ***
Apr 24 16:14:43 outcast snort[11235]: [ID 702911 daemon.notice] *** Snort 
caught a SEGV exception, shutting down.
Apr 24 16:14:43 outcast snort[11235]: [ID 702911 daemon.notice] *** SEGV caught 
while parsing '../rules/snort.conf' at line 684.

Output from `cat -n snort.conf`:

     1  #--------------------------------------------------
     2  #   http://www.snort.org     Snort current Ruleset
     3  #     Contact: snort-sigs@lists.sourceforge.net
     4  #--------------------------------------------------
     5  # $Id: snort.conf,v 1.165 2006/03/15 18:56:59 ssturges Exp $
.
.
.
   679  # database: log to a variety of databases
   680  # ---------------------------------------
   681  # See the README.database file for more information about configuring
   682  # and using this plugin.
   683  #
   684  output database: log, mysql, user=snort password=AbCdE@fGh dbname=snort 
host=localhost
   685  # output database: alert, postgresql, user=snort dbname=snort

This is exact same syntax I've used with version 2.4.3, and I'm using the 
snort.conf file that came with the 2.6.0RC1 tar file.  Changing the password to 
something invalid still results in the SEGV.

What am I missing?


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
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

<Prev in Thread] Current Thread [Next in Thread>