Bluehost.com Web Hosting $6.95

[Snort-users] Snort, remote logging, unified logs, mudpit and me!

This is a discussion on [Snort-users] Snort, remote logging, unified logs, mudpit and me! within the Snort forums, part of the System Security and Security Related category; Hi all, I'm trying to set up what I think is "a normal" system pair: System 1: ...


Go Back   Usenet Forums > System Security and Security Related > Snort

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-02-2004
Russell Packer
 
Posts: n/a
Default [Snort-users] Snort, remote logging, unified logs, mudpit and me!

Hi all,

I'm trying to set up what I think is "a normal" system pair:

System 1: The Snort machine (Devil)
System 2: The log processing / alerting machine (Slackware 9.x)

Having done lots and lots of reading, it seems that the unified (binary) =
output is "best" (as non-unified seems to lead to problems).

[As a side note, I did look at FLoP but patching snort is not an option =
due to the fact that I'm using a pre-built live-CD for system 1]

Now, it seems that I have two options on system 2 - either Barnyard or =
Mudpit. Seeing as I can't get Barnyard to configure (tried MySQL 3.23, =
4.017, my_connect, mysql_real_connect and all those other "fixes" to no =
avail), I'm forced to use Mudpit.

As I'm sure anyone else using mudpit is aware, there isn't a whole lot =
of documentation ;)

I'm currently getting my head round the Mudpit configuration, more =
specifically the Spool section. The section starts like this:

# Spool configurarion. One or more spools should be configured.
# Spool definition contains the absolute path to a spool directory
# (that is, the directory containing Snort's log/alert file pair)
# and parameters for the spool processor.

Seems fair enough. In the Snort confiuration file, there is this =
information:

# Two arguments are supported.
# filename - base filename to write to (current time_t is appended)
# limit - maximum size of spool file in MB (default: 128)
#
# output alert_unified: filename snort.alert, limit 128
# output log_unified: filename snort.log, limit 128

Hm. This raises 2 questions:

1.) How does one specifiy that these two files should actually be sent =
on a remote machine? In the MySQL example, it is obvious that you can =
specify a host, but mudput requires the files :/

2.) As these log files need to reside on a remote system, how would the =
limit work?


I may, of course, also be going along the wrong track, so any pointers =
much appreciated!


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/...fo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.p...st=snort-users
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 11:58 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0