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]

Re: [Snort-users] Changing name of alerts log

Subject: Re: [Snort-users] Changing name of alerts log
Date: Mon, 10 Mar 2008 12:02:50 -0400
Thanks Joel.
   Below is a snippet of what I would think is the pertinent area of the 
old snort file. This was snort 2.3.3(14) running on debian.
Fritz

=============== OLD SNORT.CONF SNIPPET ======================
# [Win32 can use any of these formats...]
output alert_syslog: LOG_LOCAL0 LOG_ALERT
# output alert_syslog: host=hostname, LOG_AUTH LOG_ALERT
# output alert_syslog: host=hostname:port, LOG_AUTH LOG_ALERT
# log_tcpdump: log packets in binary tcpdump format
# -------------------------------------------------
# The only argument is the output file name.
#
output log_tcpdump: tcpdump.log



Joel Esler wrote:

Do you have a snort.conf file from your predecessor?

Joel

On Mar 10, 2008, at 10:40 AM, frederick sonnichsen wrote:

I have snort 2.8.0.2 (75) running on Fedora Core 6. It presently  writes
files "alerts" and "snort.log.xxxxxxx".
I want to change the names of these files to fit software/scripts
written by my predecessor. Can someone tell me how to change the:  
alerts
log to "snortlog.log" and the dump logs to "tcpdump.log"

I tried:
in snort.conf
 output alert_syslog: LOG_LOCAL0
in syslog.conf
 local0.*
/var/log/snort/snortlog.log

But this has no affect. Perhaps this is not the way to accomplish  this.

Thanks
Fritz



------------------------------------------------------------------------- 

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



-- 
Joel Esler ï joel.esler@sourcefire.com






-------------------------------------------------------------------------
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

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