[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ossec-list] Re: POP3 brute force rule not firing

To: ossec-list <ossec-list@xxxxxxxxxxxxxxxx>
Subject: [ossec-list] Re: POP3 brute force rule not firing
From: Jeff Schroeder <jeffschroed@xxxxxxxxx>
Date: Thu, 16 Aug 2007 02:00:10 -0000

Why not something like /var/ossec/etc/decoders.d/*.xml being included
when ossec starts up?

Examples of where this is already used:
SysV init: /etc/init.d/, /etc/rc[2345].d/, or /etc/init.d/rc[2345].d
on suse
Debian's repository listing: /etc/apt/sources.list.d/
vixie-cron: /etc/cron.d/
xinetd: /etc/xinetd.d/
...

This seems like the cleanest solutions for everyone. Daniel, what do
you think?

References:
- [ossec-list] POP3 brute force rule not firing
  - From: Steve West
- [ossec-list] Re: POP3 brute force rule not firing
  - From: Dave Lowe
- [ossec-list] Re: POP3 brute force rule not firing
  - From: Steve West
- [ossec-list] Re: POP3 brute force rule not firing
  - From: Dave Lowe
- [ossec-list] Re: POP3 brute force rule not firing
  - From: Steve West
- [ossec-list] Re: POP3 brute force rule not firing
  - From: Daniel Cid

Prev by Date: [ossec-list] Re: Frequent disconnects of agent on Dell PowerEdge 2950 Windows Storage Server 2003 R2Standard Edition x64, HardwareRAID
Next by Date: [ossec-list] Re: Frequent disconnects of agent on Dell PowerEdge 2950 Windows Storage Server 2003 R2Standard Edition x64, HardwareRAID
Previous by thread: [ossec-list] Re: POP3 brute force rule not firing
Next by thread: [ossec-list] Solaris Installation Problem
Index(es):
- Date
- Thread

OSSEC home | Main Index | Thread Index

OSSEC project: www.ossec.net.
Mailling list information: http://www.ossec.net/en/mailing_lists.html.