sagan-dev

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There was a reason for the lack for "if"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If you are using the development branch of Sagan

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, We've released Sagan version 0.2.3. This

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - - Bumped the git tree from verison 0.2.1 to 0.2.2-git

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Crash recovery for SQL (MySQL/PostgreSQL/etc) for when

- Fix a issue with rule "threshold:" and "after:" interfering with each other -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Added the final "new" feature to Sagan. This

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - ----------------------- Had a situation where a

Made some core changes to how Sagan handles threads. Traditionally, there where thread variables for

Pushed up the first 0.2.1 to Githib. - Version bump from 0.2.1 - Fixed small problem with direct SQL

Split sagan.h to sagan.h and sagan-defs.h On Jun 11, 2:15 pm, Da Beave <ch...@softwink.com>

Started rebranding Sagan from Softwink, Inc. to Sagna from Quadrant Information Security Remote the -

Changed the way Sagan handles chroot. The flag now is -c {directory to chroot to}. Also, DrForbin

Fixed with with Sagan not chroot'ing properly.

Drforbin noticed Sagan seg faulted when run as a non-root (non-uid 0) users. This was cause by non-

Just bumped the version in SVN from 0.1.9 to 0.2.0 since I've started working on new code.

Committed small fix for the -f/--config Sagan flag that caused a seg fault (reported by Dr. Forbin).

config classification: successful-user,Successful User Privilege Gain,1 That's from Snort's

Hi, I've finally managed to package sagan with the latest svn trunk (r129) and have uploaded it

> While this may be a good idea for error handling, this cause a problem: > opening a FIFO is