Skip to content

TruthBeacon v0.1.5

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Oct 23:36
· 45 commits to main since this release
v0.1.5
c83d91e

TruthBeacon v0.1.5 — Official Release Notes

Bored Polymath Studios — Identity Ground-Truth & Community Stewardship

Overview

TruthBeacon v0.1.5 is a user-experience and interface alignment release that synchronizes both the standalone desktop security console and the official web distribution center with all recent architectural advancements:

  1. Complete UI Alignment with Machine-Bound AES-256-GCM Vault: Modernized all desktop console badges, security enclave pills, input help notes, and interactive FAQ guidance to accurately describe the zero-prompt machine-bound AES-256-GCM credential vault (0600 POSIX) replacing legacy OS keychain references.
  2. Auto-Updater Interface & Version Synchronization: Elevated the desktop header version pill, update polling fallback routines, and website manifests to v0.1.5 with full Minisign Ed25519 cryptographic auto-updater catalog (latest.json) support.
  3. Distribution Portal & Architecture Showcase Refresh: Updated the public website with dedicated highlights and architecture pillars for the zero-prompt vault and auto-updater engine, along with updated download matrices and verification snippets.
  4. Universal 2 Packaging & Cryptographic Integrity Verification: Rebuilt and staged production Universal 2 macOS artifacts (.dmg, .app.tar.gz), updated detached signatures, and verified clean-slate launch with 150 passing unit and integration tests.

What's New & Fixed in v0.1.5

1. Desktop Console Interface Modernization

  • Credential Enclave Status Pill: Replaced the legacy "OS Secure Enclave / Apple Keychain" pill in Discord Settings with the high-visibility "Zero-Prompt AES-256-GCM Vault Active" badge, reflecting local authenticated encryption with hardware entropy binding and strict owner-only (0600) POSIX permissions.
  • Form Field Security Guidance: Clarified token storage security notes to reassure operators that bot credentials are encrypted locally with machine-bound AES-256-GCM and never sent to remote cloud infrastructure.
  • Credential Purge Tooltip: Updated the disconnect button tooltip to explicitly reflect cryptographic zeroization and eradication from the local AES-256-GCM vault.
  • In-App FAQ Guidance: Revised the token storage security FAQ entry to provide precise technical disclosure of the Ring AEAD AES-256-GCM scheme, SHA-256 HKDF key derivation, and zero-telemetry policy.

2. Auto-Updater Engine & Version Bumping

  • Desktop Version Badge: Synchronized the interactive update button in the desktop header to default to v0.1.5.
  • IPC Update Dispatcher: Bumped IPC mock and fallback version values to 0.1.5.
  • Catalog Synchronization: Automated deployment of Tauri 2 latest.json updater catalogs across release directories and website assets.

3. Web Distribution Portal Alignment

  • Feature Highlights & Architecture Pillars: Added dedicated showcase cards for the AES-256-GCM Machine Vault and Cross-Platform Auto-Updater Engine on the official website.
  • Download Catalogs & Verification Snippets: Updated all direct download links, terminal SHA-256 verification instructions, and GPG signature endpoints to point to v0.1.5 deliverables.

Previous Highlights from v0.1.4

1. Resolved Startup Tokio Reactor Panic on Credential Auto-Connect

  • Issue: When bot credentials had been registered and stored in the secure vault, TruthBeacon automatically initiates background connection to the Discord Gateway daemon during startup. In v0.1.3, this async task was spawned using tokio::spawn inside Tauri's synchronous .setup(|app| ...) hook on the main thread. Because Tauri executes setup on the main thread outside of an active Tokio runtime context, tokio::spawn panicked immediately with: 
    there is no reactor running, must be called from the context of a Tokio 1.x runtime
    Because the panic occurred inside macOS's native applicationDidFinishLaunching: Cocoa delegate, Rust's panic unwinding crossed an FFI C/Objective-C runtime boundary, triggering panic_cannot_unwind and causing abort() (SIGABRT).
  • Fix: Replaced direct tokio::spawn calls in src/lib.rs with tauri::async_runtime::spawn. Tauri manages its own background Tokio runtime handle, allowing asynchronous tasks to be safely scheduled from synchronous main-thread setup routines.
  • Defense-in-Depth: Hardened spawn_background_avatar_fetch and start_periodic_avatar_refresh in src/vault/avatar_sync.rs to use tauri::async_runtime::spawn, guaranteeing that background avatar hashing and periodic sync routines can never panic if invoked from synchronous threads.

2. Zero-Prompt Authenticated AES-256-GCM Machine Credential Vault

  • Frictionless Operator Experience: Replaced native OS Keychain integrations (keyring-rs) with an authenticated local vault. Native OS keychains frequently prompt users with modal security dialogues (such as macOS "TruthBeacon wants to access key truth_beacon_secure_vault in your keychain" or system lock prompts), interrupting background sync, headless test suites, and desktop startup.
  • Cryptographic Authenticated Encryption (AES-256-GCM): The vault stores bot credentials using ring::aead::AES_256_GCM with 12-byte cryptographically secure random nonces and 128-bit authentication tags, preventing ciphertext tampering or truncation.
  • Machine-Unique Key Derivation via SHA-256 HKDF: Encryption keys are deterministically derived using SHA-256 HKDF bound to host machine entropy, the current user environment, and application domain salts. Stolen vault files cannot be decrypted on other machines or user accounts.
  • Strict OS Filesystem Security: On Unix and macOS platforms, the vault storage file (~/.truthbeacon/vault.enc) is created with strict 0600 permissions (read/write by owner only), blocking multi-user host inspection.
  • Dual-Tier Zeroized In-Memory Cache: Credential lookups prioritize a thread-safe in-memory cache (RwLock<HashMap<String, Zeroizing<String>>>) wrapped in zeroize::Zeroizing. Lookups achieve sub-millisecond retrieval without disk access, decrypting the on-disk vault only on initial cold-start cache misses.
  • Secure Cryptographic Erasure & System Eradication: Credential deletion and system eradication (purge_all_credentials) overwrite the vault file with zeros before removing it from disk, ensuring no data residue remains.
  • Zero-Plaintext Policy Maintained: Bot tokens remain strictly zeroized in memory, are redacted in all log output ([REDACTED]), and are never serialized to JSON, SQLite, or plain text.

3. Cross-Platform Cryptographic Auto-Updater Engine (macOS, Windows, Linux)

  • Tauri 2 Plugin Updater Integration: Integrated tauri-plugin-updater with cryptographically enforced Minisign Ed25519 signature verification to protect operators against MITM tampering.
  • Passive Background & 1-Click Manual Updates: The desktop client executes a silent background update check 5 seconds after launch and provides an interactive version badge button in the main header.
  • Interactive Update Notification: Operators receive an in-app notification card with release highlights and a 1-click "Download & Install" workflow to seamlessly relaunch the updated application.
  • Full Platform Parity: Staged and verified across macOS (Universal 2 .app.tar.gz), Windows (NSIS .zip), and Linux (AppImage .tar.gz) alongside public latest.json release manifests.

4. Automated Release Pipeline, CI Signing & Artifact Packaging Hardening

  • CI/CD Minisign Key Integration: Configured TAURI_SIGNING_PRIVATE_KEY and automated key decoding in .github/workflows/ci.yml and .github/workflows/release.yml, ensuring production builds generate authentic cryptographically signed manifests.
  • Safe Fallback Signing across Packaging Scripts: Hardened scripts/build_macos_universal.sh, scripts/build_linux_bundle.sh, and scripts/build_windows_bundle.ps1 with fallback signature generation and validation checks, enabling graceful local development builds and offline packaging.
  • Automated Manifest Generator: Added scripts/generate_updater_manifest.py to deterministically assemble and format latest.json catalogs from release builds and signatures.
  • Detached GPG Signatures & Release Manifests: Staged updater tarballs and bundles in RELEASE_MANIFEST.md and SHA256SUMS.txt, verified with detached ASCII-armored GPG signatures (.asc).
  • Clean-Slate Smoke Testing: Updated scripts/smoke_test_clean_slate.py and scripts/verify_packaging_pipeline.py to validate clean-slate environment setup, zero-prompt vault operations, and release bundle integrity.

Previous Highlights from v0.1.3 & v0.1.2

1. Tauri 2 IPC Parameter Normalization

  • Resolved Argument Serialization: Tauri 2 commands expect camelCase argument names by default (guildId). Added automatic bidirectional casing normalization in ui/js/ipc.js to ensure seamless deserialization across all Tauri commands.
  • Resilient Daemon Lifecycle: Hardened background Discord Gateway connection lifecycle and periodic heartbeat transmission.

2. Automated 1-Click Bot Authorization & Pre-Calculated Permissions

  • Instant Client ID Extraction: TruthBeacon automatically extracts and base64-decodes your bot's application snowflake ID directly from segment 1 of your Bot Token upon pasting.
  • Pre-Calculated Permissions Bitfield: Eliminates manual Discord OAuth2 URL Generator calculations:
    $$\text{VIEW_CHANNEL (1024)} \mid \text{KICK_MEMBERS (2)} \mid \text{BAN_MEMBERS (4)} \mid \text{MODERATE_MEMBERS (1099511627776)} = \mathbf{1099511628806}$$
  • 1-Click "Authorize & Invite Bot" Button: Direct 1-click addition of the bot to your Discord server, plus a 1-click "Copy Link" utility.

3. Automated Server Discovery (Zero Snowflake Hunting)

  • Automatic Discord Gateway Server Discovery: Integrated fetch_bot_guilds Tauri IPC command querying Discord v10 REST API (GET /users/@me/guilds).
  • Dynamic Discovered Servers Dropdown: Discovered servers appear in an interactive dropdown with server names and IDs.

4. Credential Architecture Evolution

  • Evolved from system-prompted OS Keychains (keyring-rs) to TruthBeacon's zero-prompt Authenticated AES-256-GCM Vault architecture, preserving strict zero-plaintext security without OS modal interruptions.

Core Security Engine

  1. Deterministic Multi-Script Homoglyph Detection:

    • Sub-50ms deterministic normalization and skeleton decomposition (NFKD).
    • Defeats cross-script lookalike substitutions across Cyrillic, Greek, Mathematical, and Latin lookalikes.
    • De-obfuscates invisible unicode anomalies, zero-width spaces, and bidirectional text overrides.

  2. Perceptual Avatar Clone Defense:

    • Discrete Cosine Transform (DCT) perceptual image hashing (img_hash).
    • Automatically flags unauthorized copies and subtle visual perturbations of moderator and VIP avatars.

  3. Snowflake Cryptographic Account Age Analysis:

    • Parses Discord 64-bit integer IDs directly to extract real account creation epochs.
    • Escalates risk tier when brand-new accounts (< 72 hours old) exhibit visual or naming similarity to benchmark staff.

  4. Zero-Telemetry Local Data Sovereignty:

    • 100% offline-first architecture; all benchmark vaults, audit logs, and incident records are retained exclusively on the operator's machine.

Platform Availability & Supported Operating Systems

  • macOS (Universal 2):
    • Supports Apple Silicon (M1/M2/M3/M4) and Intel Macs (macOS 10.15 Catalina or higher).
    • Packaged as a drag-and-drop .dmg installer with custom Orange Heart backdrop, a standalone portable .app bundle, and an updater archive (.app.tar.gz).
  • Windows (x64):
    • Supports Windows 10 and Windows 11 (64-bit).
    • Packaged via WiX (.msi) for enterprise deployment, NSIS (.exe) for standard setup, a portable executable, and an NSIS updater package (.nsis.zip).
  • Linux (x86_64):
    • Supports Ubuntu 20.04+, Debian 11+, Fedora, and Arch.
    • Packaged as a native Debian .deb package, portable standalone .AppImage, and an AppImage updater archive (.AppImage.tar.gz).

Verification & Checksums

All binaries are verified through GitHub Actions CI and signed with SHA-256 cryptographic checksums. Check SHA256SUMS.txt and RELEASE_MANIFEST.md for verification details.

Assets 18
Loading