Autobricks True Log Client 0.3.62 — macOS arm64 / x86_64

Autobricks True Log Client 0.3.62 — macOS arm64 / x86_64

This release provides macOS installer packages for ab-truelog-cli. The client
sends logs to a Linux True Log server and queries stored WORM file metadata.
WORM storage remains on Linux; only the client is installed on macOS.

Use a Linux True Log server 0.3.61 or later supporting write and info.
Linux server and client packages
are available in a separate release.

Downloads

File	Target
autobricks-truelog-cli-0.3.62-macos-arm64.pkg	Apple Silicon
autobricks-truelog-cli-0.3.62-macos-x86_64.pkg	Intel Mac
SHA256SUMS	Package SHA-256 checksums

Requires macOS 13 or later.

Installation

1. Download the .pkg matching your Mac's architecture and SHA256SUMS.

2. Verify the checksum in the download directory:

   shasum -a 256 -c SHA256SUMS --ignore-missing

   Confirm that the downloaded package reports OK.

3. Open the .pkg in Installer and install on the running system volume.

4. Open Terminal and run initial setup:

   sudo /usr/local/bin/ab-truelog-cli setup

5. Complete the curses configuration screen:

   Autobricks True Log Client - macOS setup
   
   > SERVER ADDRESS         [logs.example.test]
     PORT                   [5544]
     MODE (Space toggles)   [mtls]
     CLIENT HOSTNAME        [example-client]
     CLI USER               [the local user running sudo]
     PAIRING CODE           [*********]
   
   Tab/Up/Down: move  Enter: Register and start  Esc: Cancel
   

   SERVER ADDRESS is the actual Linux server IP address or DNS name. PORT
   defaults to 5544; change it if the server uses another port. MODE defaults
   to mTLS; use Space or Left/Right to toggle TCP/mTLS. CLIENT HOSTNAME identifies
   the client in server-side log paths. CLI USER is the existing local account
   allowed to write and query logs, defaulting to the account running sudo.
   PAIRING CODE is the server-issued eight-digit code, required only for mTLS and
   masked on screen.

   Use Tab/Up/Down to move, Backspace to edit, Enter to register and start, and
   Esc to cancel. The terminal must have at least 64 columns and 14 rows. Setup
   uses macOS's built-in curses library and requires no Python or Homebrew.

6. In mTLS mode, setup enrolls certificates using the server's Pairing Code and
   checks an authenticated connection. Enrollment, writes and queries all use
   the same configured port. TCP skips enrollment and requires a trusted network.

7. After successful registration, setup saves protected settings and certificates,
   registers the system launchd service and starts it. The service runs as a
   dedicated unprivileged account and starts automatically at boot.

First installation does not start an unconfigured service. Cancellation and
enrollment failures preserve existing connection settings. Activation failures
attempt to restore the previous configuration and service. Setup does not delete
server data.

Usage as a regular user

Administrator privileges are needed only for installation and initial system
setup. Run these commands as the account selected in setup, without sudo or
repeated --host/--port arguments:

/usr/local/bin/ab-truelog-cli --version
/usr/local/bin/ab-truelog-cli --help

# Send one log record to the Linux server.
/usr/local/bin/ab-truelog-cli write --service example-service --data 'application started'

# Query stored metadata for a server-side WORM file.
/usr/local/bin/ab-truelog-cli info --file example-files/example.log

If /usr/local/bin is on PATH, use ab-truelog-cli directly.

write returns the server's before/after checksum receipt after its configured
durability boundary completes. info returns stored WORM metadata as JSON; it
does not read log contents or rehash the entire file. Use the actual server-side
WORM file path or a path relative to the WORM mount, replacing the example with
the file to query. Existing server authorization and path restrictions apply.

Reconfiguration, upgrades and diagnostics

# Edit saved connection settings.
sudo /usr/local/bin/ab-truelog-cli setup

# Inspect the service.
sudo launchctl print system/com.autobricks.truelog.client

mTLS reconfiguration currently requires the Pairing Code again for enrollment.
Installing a newer .pkg preserves settings and certificates and restarts an
already configured service.

Configuration is stored in /etc/autobricks-truelog-cli/client.toml. Private keys
are kept in protected certificate generation directories under the same directory.
The daemon runs as _abtruelog, owns its local socket and grants access to the
selected CLI user. The socket is not world-writable.

The server firewall must allow access to its configured RPC TCP port from the
intended client network. The client package does not modify the server firewall.