This installation package is based on the Debian etch distribution. See the Debian documentation for an explanation of general installation procedures. These instructions are for specifically installing and configuring the Realeyes packages.
There are four Realeyes packages which may be installed together or separately. Some combinations do not make sense, such as the IDS sensor package and the user interface package.
There are three steps to installing the Realeyes packages and one step to deinstallation.
2. Install the appropriate Realeyes packages
3. Configure the Realeyes packages
4. Deinstallation is included and described in the last section
See the README files in /usr/share/doc/package_name for an explanation of each package.
The realeyesDB schema for the PostgreSQL database and the realeyesDBD application may also use significant memory and disk space if there are several realeyes IDS sensors.
To account for these requirements, the recommended disk partitions are as follows (Option 1 will be sufficient for most installations, but Option 2 is described for those that need it):
The /data partition in Option 2 should be defined as follows for the specified packages, BEFORE THE PACKAGES ARE INSTALLED:
During the configuration of the RealeyesIDS package (see the installation instructions below) and set the Spooler directory to /data/ids_spooler.
Edit the PostgreSQL configuration file, which should be found
in /etc/postgresql/
In this case, both interfaces should be defined to use static IP addresses, with the monitoring interface set to 0.0.0.0. It is advisable to establish a site standard for using the first or second interface for monitoring.
If the X window system has been installed, it may be easier to use it than the console screen. Logged in as root, enter the command:
When the descktop (fluxbox if using the default) initialization is complete, right-click the mouse to display the main menu. Select the XShells -> XTerm menu option and an xterm window is displayed.
To configure the database, enter the following command:
There are explanations of what to expect, and many prompts have a preset default, which is selected by pressing Enter.
Several user IDs and passwords are set in this script. If each user ID is given a unique password, be sure to keep track of them.
When the database configuration is complete, it can be tested by logging in to the DBA ID, running the psql program to interact with the database, and displaying Realeyes tables. Note that the configuration defines the alias "rled" to simplify starting the psql program using the realeyesDB database schema.
There is no configuration script for the user interface. However, some initial configuration using the user interface needs to be done before the DBD can be started. The database must be configured and running for the login to be successful. To start the user interface, enter the following command:
The login window will be displayed and all of the fields must be filled in:
If successfully logged in, all fields except the password can be set from the menu selection Edit -> Preferences.
The initial information that must be defined, in the order that it must be defined is found in the following menu selections:
When the Save button is clicked for any entry, the information is immediately saved in the database and available for use. However, windows that build popup menus of selections from database information do not have these automatically refreshed, so each of the above should be opened after the previous one has been completed.
To configure the DBD, enter the following command:
There are explanations of what to expect, and many prompts have a preset default, which is selected by pressing Enter.
Note that some selections must be coordinated with the database configuration and others with the IDS configuration.
In particular, ports may be configured for both connections, but note that if the IDS data and control ports are changed, it affects all IDS sensors.
Encryption between the DBD and the IDS is unnecessary if both are on the same host. Otherwise, it is strongly recommended. The private key and certificate is generated on the DBD and copied to each IDS sensor host during that configuration.
To configure the IDS, enter the following command:
There are explanations of what to expect, and many prompts have a preset default, which is selected by pressing Enter.
NOTE: If the disk partitioning includes an IDS data directory, set the Spooler directory to /data/ids_spooler when prompted.
Note that some selections must be coordinated with the DBD. Especially note that if the data and control ports are changed from the default, all IDS sensors must use the new values.
The memory allocation value is a percentage. Therefore, if there is 1G of memory installed, the 33% default will allocate 333M of memory for the IDS. If the IDS is the only application running on the host, this value can be as high as 90%. The following general rules may be applied:
NOTE: This must be running for either RealeyesDBD or RealeyesGUI to start successfully
NOTE: It has been observed that the first (and possibly second) time the IDS is started, the operating system fails to initialize shared memory. Once it starts working, the problem is not seen again, even after reboots.
Follow the instructions in the README file.