Removing the : from a lot of titles.

I don't think I like them anymore.

Author: ddpbsd

about/architecture.rst

@@ -4,28 +4,28 @@
 OSSEC Architecture
 ==================
 
-Linux and unix-like systems:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Linux and unix-like systems
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 OSSEC runs as multiple processes, the exact number differing between agent, server, and local installations.
 Most processes communicates through unix sockets under the `queue` directory inside of the OSSEC installation location.
 When possible the OSSEC processes run with limited privileges and chroot to the install location.
 This is modeled after the `Privilege Separation tehniques <https://www.openbsd.org/papers/auug04/mgp00030.html>`_ used in OpenBSD.
 
-Windows:
-^^^^^^^^
+Windows
+^^^^^^^
 
 OSSEC runs as a single service.
 
-Agent/Server Communication:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Agent/Server Communication
+^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 The OSSEC server listens on 1514/udp via `ossec-remoted`.
 Agents send messages to the server via `ossec-agentd`.
 The communication is two-way, but initiated by the agent.
 
-Agentless and Network Devices:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Agentless and Network Devices
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 OSSEC has the ability to communicate with systems that cannot have the agent software installed.
 This is typically done through SSH, and a few pre-made `Expect <https://core.tcl.tk/expect/index>`_
@@ -34,8 +34,8 @@ scripts are provided for a number of systems.
 In addition to the agentless support, OSSEC can receive syslog messages from any number of devices and process them as if the
 messages were delivered via an agent.
 
-User List:
-^^^^^^^^^^
+User List
+^^^^^^^^^
 
 +--------+---------------------------------------------------+
 | User   | Process                                           |
@@ -49,8 +49,8 @@ User List:
 | ossecm | ossec-maild, ossec-csyslogd                       |
 +--------+---------------------------------------------------+
 
-Process List:
-^^^^^^^^^^^^^
+Process List
+^^^^^^^^^^^^
 
 +--------------------+--------------------------------------------------------------------------------+---------------------+
 | Process            | Description                                                                    | Install Type        |

about/supported.rst

@@ -5,8 +5,8 @@ Supported Systems
 =================
 
 
-Operating Systems:
-^^^^^^^^^^^^^^^^^^
+Operating Systems
+^^^^^^^^^^^^^^^^^
 
 The following operating systems are supported by the OSSEC agent:
 
@@ -21,8 +21,8 @@ The following operating systems are supported by the OSSEC agent:
    - Mac OS X 10.x
    - HP-UX 11
 
-Devices Supported via Syslog:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Devices Supported via syslog
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 These systems/devices are also supported via remote syslog:
 
@@ -50,8 +50,8 @@ Using OSSEC agentless options, the following systems are also supported (for log
    - Checkpoint firewall (all versions)
    - All operating systems specified in the “operating systems” section
 
-Notes about support:
-^^^^^^^^^^^^^^^^^^^^
+Notes about support
+^^^^^^^^^^^^^^^^^^^
 
 The OSSEC project is made up of volunteers, mostly working on the project in their free time.
 Some systems will be harder to support due to availability.

configuration/active-response.trst

@@ -2,8 +2,8 @@
 
 .. _active-response_disabled:
 
-disabled:
-^^^^^^^^^
+disabled
+^^^^^^^^
 
    Disables active response if set to `yes`.
    Active response defaults to enabled on Unix-like systems and disabled on Windows.
@@ -12,15 +12,15 @@ disabled:
 
 .. _active-response_command:
 
-command:
-^^^^^^^^
+command
+^^^^^^^
 
    Specifies the command to be run when the active response is triggered.
 
 .. _active-response_location:
 
-location:
-^^^^^^^^^
+location
+^^^^^^^^
 
    Specifies where the active response will be run.
 
@@ -36,46 +36,46 @@ location:
 
 .. _active-response_agent_id:
 
-agent_id:
-^^^^^^^^^
+agent_id
+^^^^^^^^
 
    Specifies the agent ID to run the active response on when using `defined-agent` as the `location`.
 
 .. _active-response_level:
 
-level:
-^^^^^^
+level
+^^^^^
 
    The active response will be executed on any event of the specified level or higher.
 
 .. _active-response_rules_group:
 
-rules_group:
-^^^^^^^^^^^^
+rules_group
+^^^^^^^^^^^
 
    The active response will be executed on any alert with the specified group.
    Multiple groups can be defined, separated with the pipe (`|`) character.
 
 .. _active-response_rules_id:
 
-rules_id:
-^^^^^^^^^
+rules_id
+^^^^^^^^
 
    The active response will be executed on any alert with the specified rule ID.
    Multiple IDs can be specified separated by a comma.
 
 .. _active-response_timeout:
 
-timeout:
-^^^^^^^^
+timeout
+^^^^^^^
 
    Specifies the amount of time, in seconds, before an active response will attempt to reverse its actions.
    For example IPs can be unblocked or entries removed from the `hosts.deny` file.
 
 .. _active-response_repeated_offenders:
 
-repeated_offenders:
-^^^^^^^^^^^^^^^^^^^
+repeated_offenders
+^^^^^^^^^^^^^^^^^^
 
    A comma separated list or increasing timeouts (in minutes) for repeat offenders.
    There can be a maximum of 5 entries.

configuration/agent_conf.rst

@@ -15,8 +15,8 @@ The `agent.conf` file (and the contents of `/var/ossec/etc/shared`) will be push
 Many of the configuration options in the `ossec.conf` can be placed in teh agent.conf.
 If the `agent.conf` is modified, the agent will have to be restarted for the changes to take effect.
 
-Minimal ossec.conf:
-^^^^^^^^^^^^^^^^^^^
+Minimal ossec.conf
+^^^^^^^^^^^^^^^^^^
 
 At a minimum, the `<client>` section is necessary.
 Without this, the agent does not know how to communicate with the server.
@@ -30,8 +30,8 @@ Minimal `ossec.conf` example:
      <server-hostname>ossec.example.com</server-hostname>
    </client>
 
-Settings that will not work:
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Settings that will not work
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 By default the OSSEC agent will not run commands from an `agent.conf`.
 Any `<localfile>` options that require `command` or `full_command` should be configured in the agent's `ossec.conf.`

configuration/agentless.trst

@@ -2,8 +2,8 @@
 
 .. _agentless_type:
 
-type:
-^^^^^
+type
+^^^^
 
    The type of check to be run on the agentless system.
 
@@ -19,15 +19,15 @@ type:
 
 .. _agentless_frequency:
 
-frequency:
-^^^^^^^^^^
+frequency
+^^^^^^^^^
 
    Specifies the time in seconds between each check.
 
 .. _agentless_host:
 
-host:
-^^^^^
+host
+^^^^
 
    Specifies the username and host to be checked.
 
@@ -39,8 +39,8 @@ host:
 
 .. _agentless_state:
 
-state:
-^^^^^^
+state
+^^^^^
 
    Specifies whether the checks are periodic or periodic_diff.
 
@@ -52,8 +52,8 @@ state:
 
 .. _agentless_arguments:
 
-arguments:
-^^^^^^^^^^
+arguments
+^^^^^^^^^
 
    Specifies the arguments passed to the script.
 

configuration/alerts.trst

@@ -2,8 +2,8 @@
 
 .. _alerts_email_alert_level:
 
-email_alert_level:
-^^^^^^^^^^^^^^^^^^
+email_alert_level
+^^^^^^^^^^^^^^^^^
 
    Minimum alert level for email notification.
 
@@ -19,8 +19,8 @@ email_alert_level:
 
 .. _alerts_log_alert_level:
 
-log_alert_level:
-^^^^^^^^^^^^^^^^
+log_alert_level
+^^^^^^^^^^^^^^^
 
    Minimum alert level to record an alert in `alerts.log`.
 
@@ -30,14 +30,12 @@ log_alert_level:
 
 .. _alerts_use_geoip:
 
-use_geoip:
-^^^^^^^^^^
+use_geoip
+^^^^^^^^^
 
    Enable or disable GeoIP lookups.
 
    **Default:** no
 
    **Allowed:** yes/no
 
-
-

configuration/client.trst

@@ -2,26 +2,26 @@
 
 .. _client_server-ip:
 
-server-ip:
-^^^^^^^^^^
+server-ip
+^^^^^^^^^
 
    Specifies the IP address of the OSSEC management server.
 
    **Allowed:** Any valid IP address
 
 .. _client_server-hostname:
 
-server-hostname:
-^^^^^^^^^^^^^^^^
+server-hostname
+^^^^^^^^^^^^^^^
 
    Specifies the hostname of the OSSEC management server.
 
    **Allowed:** Any valid hostname
 
 .. _client_port:
 
-port:
-^^^^^
+port
+^^^^
 
    Specifies the port used by the OSSEC management server.
 
@@ -31,8 +31,8 @@ port:
 
 .. _client_config-profile:
 
-config-profile:
-^^^^^^^^^^^^^^^
+config-profile
+^^^^^^^^^^^^^^
 
    Specifies the profile to be used by the agent.
    The profiles are defined in the `agent.conf` on the OSSEC management server.
@@ -42,8 +42,8 @@ config-profile:
 
 .. _client_notify_time:
 
-notify_time:
-^^^^^^^^^^^^
+notify_time
+^^^^^^^^^^^
 
    Specifies the time in seconds between messages sent to the OSSEC management server.
 
@@ -54,8 +54,8 @@ notify_time:
 
 .. _client_time-reconnect:
 
-time-reconnect:
-^^^^^^^^^^^^^^^
+time-reconnect
+^^^^^^^^^^^^^^
 
    Time in seconds until a reconnection attempt is made.
    This should be set to a number greater than `notify_time`.