Bug Tracking System

If you think you found a bug, or if you want to fill a feature request, please use the Prelude Bug Tracking System.

Please make sure that what you’re reporting is actually a BUG and not a problem on your end.

Poll

Developers Area

Follow the Prelude Project

Follow the Prelude development news by consulting the charts below, or by accessing directly to the project management system: Prelude Trac

 

Last Prelude Developments

Feature Notes
Prelude-LML, support mod_security v2 Contributed by Peter Vrabec and Dan Kopecek
Prelude-LML, support FreeBSD su attempts Contributed by Alexander Afonyashin
Easybindings Provide an easy and natural way to use the Prelude interfaces, from high level languages (available for C++, Python, Perl, Ruby, Lua)
Auditd native support Contributed by Steve Grubb
Prelude-LML, support Suhosin Contributed by Sébastien Tricaud

 

Prelude Developments Matrix

Feature Planned Development Notes
ClamAV native support   X  
Prelude-Correlator   X (beta)
PADS native support   X  
Multithreading API independance   X support for posix, solaris, pth, win32 backend

Subversion Access

You can obtain the latest Prelude source tree using the open source version control system Subversion.  Be warned that it contains development code which might be unstable, and may not even compile properly. The advantage of using Subversion, though, is that you can get the latest fixes and updates, without having to wait for the official releases.

The module you wish to check out must be specified as modulename.

  • Checking out the development branch

svn checkout http://svn.prelude-ids.org/modulename/trunk

 

  • Developer Access

Same rules as Anonymous Subversion access apply, but developer need to use https. Subversion will prompt you for a password if you request an operation that require write access to the repository.  

 

Contributing Code

Repository checkin

Contributions to the Prelude code source are greatly appreciated and we are thankful for any patches and new code made for the project.

All change checked in the Prelude repository have to be reviewed. This is done for maintainability reason and to keep the code base clean.

Please send unified diff to the Prelude development mailing list and ask for review. Approval for checking your changes in the main Prelude repository will be granted by Yoann Vandoorselaere.

Of course, this rule does not apply in case you are designated as maintainer of a given repository module.

 

Copyright

When contributing, please keep in mind that we ask you for the copyright of the code. The reason lies in the dual licensed nature of Prelude-IDS.

This means that by contributing code for the Prelude-IDS project or any other PreludeIDS Technologies product, this code will automatically be copyrighted to PreludeIDS Technologies.