"Fossies" - the Fresh Open Source Software Archive

Member "libsafe-2.0-16/LIBPRELUDE" (18 Feb 2002, 1280 Bytes) of package /linux/misc/old/libsafe-2.0-16.tgz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 If libsafe is compiled on a system with libprelude installed, libsafe will
    2 additionally emit a stack overflow alert to the Prelude Manager.
    3 
    4 Using libprelude, libsafe becomes a Prelude sensor, and acquires the ability
    5 to issue alerts to the Prelude Manager.  This allows you to centralize
    6 reports from distributed sensors in one place, and allows you to correlate
    7 events detected by different sensors (for more information about the
    8 Prelude Hybrid IDS, please see http://www.prelude-ids.org).
    9 
   10 In order for libsafe to be able to contact the Prelude Manager, you'll
   11 have a little configuration to do first:
   12 
   13     1.  Run the manager-adduser program on the Prelude Manager host.
   14     2.  Run the sensor-adduser program, on the sensor host with the following
   15 	    arguments : sensor-adduser --sensorname libsafe --uid <uid of the
   16 	    libsafe protected program> --manager-addr <address of the Prelude
   17 	    Manager>
   18 
   19 That's all you have to do to enable your libsafe-protected application
   20 to report to Prelude.
   21 
   22 The Libsafe/Prelude configuration is stored in the default sensor configuration
   23 file: /etc/prelude-sensors/sensors-default.conf.
   24 
   25 This configuration file should contain settings like the Prelude Manager
   26 address, so that a given sensor knows where an alert should be emitted.