DataReel Reporting Agent for Linux Documentation Downloads

Install the agent

The agent comes as an RPM for RHEL 8, 9 and 10 (and rebuilds such as Rocky Linux, AlmaLinux and Oracle Linux) for x86_64.

What you need

Install the RPM

Download the RPM for your release from the downloads page (el8, el9 or el10) and check it against its .sha256sum file:

$ wget https://datareel.com/downloads/linux_reporting_agent/linux_reporting_agent-1.1.3-1.el9.x86_64.rpm
$ wget https://datareel.com/downloads/linux_reporting_agent/linux_reporting_agent-1.1.3-1.el9.x86_64.rpm.sha256sum
$ sha256sum -c linux_reporting_agent-1.1.3-1.el9.x86_64.rpm.sha256sum
# dnf install ./linux_reporting_agent-1.1.3-1.el9.x86_64.rpm
# dnf install openscap-scanner          # RHEL 8 and 9 vulnerability scans

The RPM installs the agent, its settings, the systemd unit and a logrotate file, and makes the drra-upload group. It does not start the service: set the server first.

Set the server

All settings are in /etc/drra/drra.ini (root only, as it can hold the enrollment token). For a report server at reports.example.com with the pages in /linux/upload/:

[delivery]
methods=https

[https]
host=reports.example.com
upload_path=/linux/upload/upload.php
register_path=/linux/upload/register.php
enrollment_token=     ; from server.ini, or empty to approve by hand

[scan]
enabled=1             ; optional, see Vulnerability scans

See Configuration for every setting.

Start the service

# drra report | less                    # look at a report, nothing is sent
# drra fingerprint                      # key fingerprint for the admin page
# systemctl enable --now drra
# tail /var/log/drra/drra.log

The first cycle registers the host. Without an enrollment token the log says the agent is pending: approve it on the admin page (Approve hosts), and the next report goes through. systemctl reload drra starts the next report now. Settings are read again before every report, so a changed drra.ini needs no restart.

Commands

CommandWhat it does
drra runRuns as a service: a report every report_interval_minutes (systemd uses this)
drra onceWrites and sends one report, scanning first when a scan is due
drra reportPrints a report, nothing is sent
drra scanRuns the vulnerability (and compliance) scan now and sends a report with the results; --no-send only prints them
drra hooksRuns the report hooks and prints their HOOKS section
drra submit --hook <id> [--now] <file>Queues a report from another tool for upload hook <id>; --now asks the service to send it right away
drra send-uploadsSends the queued upload files now, without a report
drra uploadsLists the upload hooks and their state
drra registerRegisters the agent certificate with the report server
drra fingerprintPrints the agent key fingerprint to check on the admin page
drra configPrints the settings in use
drra selftest [URL]Prints the build, OpenSSL, libcurl, FIPS mode and (RHEL 8 openssl35 package) the crypto policy, and checks them; with a URL, connects and prints the TLS version, cipher and key exchange group
drra versionPrints the version

-c <ini file> uses another settings file, for example to test against a development server.

Installed files

PathContents
/usr/sbin/drraThe agent
/etc/drra/drra.iniSettings, with comments (mode 0600)
/etc/drra/report.d/Report hooks, see Hooks
/etc/drra/uploads.d/Upload hook files
/usr/lib/systemd/system/drra.serviceThe systemd unit, hardened (read only /usr, /boot and /etc, private /tmp, no new privileges)
/var/lib/drra/Agent key and certificate, registration state, last report, scan results and feed cache
/var/log/drra/drra.logLog of every report and upload (rotated by logrotate)
/var/spool/drra/uploads/Hook upload spool, writable by the drra-upload group
/usr/share/doc/linux_reporting_agent/README, license, the report server pages (php/) and the DRSM files (drsm/)

Upgrade and remove

dnf install a newer RPM to upgrade: the service restarts and drra.ini, the key and the registration stay. dnf remove linux_reporting_agent stops and removes the service; /var/lib/drra and /var/log/drra stay until you delete them. Delete the host on the admin page too, or a reinstall with a new key gets key_mismatch.

RHEL 8: two packages

RHEL 8's own OpenSSL is 1.1.1, so RHEL 8 has two packages, like DataReel's other products. Install one of them:

PackageOpenSSLUse it when
linux_reporting_agent-<version>.el8RHEL 8's own OpenSSL 1.1.1 and libcurl, so the crypto policy and FIPS mode apply. No ML-KEM.The host is in FIPS mode, or must use Red Hat's FIPS validated OpenSSL
linux_reporting_agent-openssl35-<version>.el8OpenSSL 3.5 and libcurl built in. Follows the system crypto policy (ciphers, signature algorithms, TLS versions, never below TLS 1.2). Hybrid post-quantum key exchange: X25519MLKEM768 first, then X25519 and P-256 and the other classical groups. Not FIPS validated.The host is not in FIPS mode and should get post-quantum TLS

The openssl35 package provides linux_reporting_agent and conflicts with it. Its %pre refuses to install it on a host in FIPS mode (/proc/sys/crypto/fips_enabled is 1), and if FIPS mode is turned on later it refuses to run: it logs why and exits with status 78, which systemd does not restart. Switch between the packages with dnf install --allowerasing; the settings, the key and the registration are kept:

# dnf install --allowerasing ./linux_reporting_agent-openssl35-1.1.3-1.el8.x86_64.rpm   # or the other one
# systemctl restart drra
# drra selftest https://your.server/       # build, OpenSSL, crypto policy, TLS key exchange

How the openssl35 package follows the crypto policy: it reads /etc/crypto-policies/back-ends/opensslcnf.config and applies CipherString, Ciphersuites, SignatureAlgorithms and TLS.MinProtocol/TLS.MaxProtocol to every connection (a minimum below TLS 1.2, as in LEGACY, is raised to TLS 1.2). Groups: [https] tls_groups when set; otherwise the policy's groups with X25519MLKEM768 first when the policy is not FIPS; RHEL 8's policies name no groups, so OpenSSL 3.5's own list is used, with X25519MLKEM768 first (with the FIPS policy: P-256, P-384 and P-521 only). drra selftest and the service log show the policy and any setting OpenSSL 3.5 did not take.

The bundled OpenSSL gets security fixes with new agent releases, not from dnf update openssl. The linux_reporting_agent package gets them from Red Hat.