Skip to content

Orion-X Phoenix Edition v3.1.0

Choose a tag to compare

@jarocki jarocki released this 27 Oct 03:44
· 146 commits to main since this release
19bd77e

Five operator-requested changes, tracked under the
v3.1.0 milestone (#103–#111)
and defined in MASTER_PLAN.md (DEC-PHASE13-013…022). The release includes the
v3.0.1 and v3.0.2 security patches. Unit, lint and headless GTK tests cover
the source changes. The icon fix was reproduced and verified against the
v3.0.0 squashfs's own GTK. The ISO was built by CI from the tag commit and
booted on an HP Pavilion laptop (identity below).

ISO identity. SHA-256 38ca9d833e93e53fc6e9dd1bcab68207e2ce37d31d6d51702b67985f983ad6c5,
3,151,036,416 bytes (3.15 GB), built 2026-10-25 by the Release Pipeline (Actions
run 40237454360) from 19bd77ea9a99, the tag commit, with a clean chroot (no
stale-stage reuse in the build log). Baked ISO_VERSION=v3.1.0. Gates on this
image: .sha256 sidecar matches; hooks-applied 20/0 against the CI build log;
content-presence in release mode (ORIONX_RELEASE_GATE=1 ORIONX_EXPECT_VERSION=v3.1.0) passed in the same CI run; QEMU BIOS 108 s / UEFI
115 s on the build host. Booted by the owner on an HP Pavilion (8 GB) on
2026-10-26: works, with the hardware findings listed under Known issues. Not
re-tested on the Lenovo reference deck. The CHANGELOG, README and User Guide
copies baked into the image predate this identity line, as every release's must.

Fixed

  • The Orion Workbench, Orion Cockpit and Phoenix icons now render in the menu,
    on the desktop and in the panel. In v3.0.0, gdk-pixbuf rejected their SVGs
    because header comments pushed <svg past the first 256 bytes, which is as
    far as its SVG loader looks. This was reproduced in the v3.0.0 image. Header
    comments now sit inside <svg>, and the desktop-entry test rejects any theme
    icon that breaks the rule (#103). The Cockpit window now uses the gauge
    icon instead of the Phoenix.
  • The Workbench's orionx-logquery card no longer claims journald, Suricata
    and Zeek sources the tool cannot parse. It now names what it reads: NDJSON
    (including the deck's event stream), web access logs and the nftables drop
    log (#111).
  • orionx-logquery no longer appears to hang when run without --path.
    --path defaulted to stdin, so the command that the Workbench card, the
    Attack Map and orionx-help all advertise (orionx-logquery --report summary) sat on an interactive terminal waiting for input and printed
    nothing. Piped input is still read as before. An interactive run without
    --path now reads this deck's event stream (/run/orionx/events.jsonl) and
    says so. If that file is not present, the tool exits at once with examples.

Added

  • The Cockpit's status line (hostname, address, threat posture, clock) is now
    a strip above the tabs and shows on every tab. Its probes keep running when
    LIVE is not the visible tab (#105).
  • Every Cockpit tab now uses LIVE's look: the dark gradient and grid, an
    ember-framed panel titled with the tab's name, Hack type, and ember headings
    and dividers (#106).
  • The Cockpit's Network tab now shows every interface (state, addresses,
    live down/up rates, share of traffic, totals), the default route and DNS,
    and TCP/UDP/ICMP packets per second (#107). It lists NetworkManager VPN and
    WireGuard connections with Connect/Disconnect, and can import a provider's
    WireGuard .conf, with no OpenVPN stack added (#108). It has per-interface
    Start/Stop for the bounded capture, Copy to ~/Captures, and Open in
    Wireshark (#109).
  • orionx-capture export <iface> copies the newest ring file into the
    operator's ~/Captures (mode 0600). It refuses if the destination cannot
    hold the copy.
  • Orion-themed icons for Artifact Analyzer, DJ Deck, Matrix Comms, Matrix
    Setup and Storyboard Generator, which previously used generic theme icons
    (#104).
  • orionx-logquery -v/--verbose narrates each step on stderr, stamped with
    elapsed seconds: the files to be read and their total size, each file as it
    starts and finishes, a heartbeat every 100,000 lines, object-store listing
    and fetch counts, and how long intel loading, enrichment, correlation, the
    SQL engine load and the query took. Report output on stdout is unchanged.

Known issues and release status

  • Booted on an HP Pavilion (8 GB); not re-tested on the Lenovo reference deck.
    The Network tab's VPN connect/import and capture start/stop/export were
    tested against fixtures and a headless GTK session, not against a live
    NetworkManager or a real capture.
  • Found on hardware on 2026-10-26, all present in v3.0.0 as well, tracked under
    the v3.1.1 and v3.2.0 milestones: no display-brightness handler (#119), no volume/battery/brightness panel widgets (#120; #121 asks for the apt evidence), spoken alerts that fail silently when piper fails and are cut at 10 s (#122), acronym pronunciation (#123), no click-through from the Cockpit to the Attack Map (#124), Suricata running with zero signatures (#125), a DEFENSIVE ACTIONS pane that cannot show proposals or active sources (#126), orionx-logquery dropping IDS/Zeek/scan detail (#127) and no scanning-tool attribution (#128).
  • The Workbench still launches as a terminal plus Firefox, so its running
    windows show those programs' icons. The menu, desktop and panel icon are
    fixed.
  • Per-interface protocol counts need capture or Zeek data. The Network tab
    shows protocol traffic for the whole deck and says so (#93).
  • CI builds and verifies the ISO; signing happens on the owner's machine
    (release-process §10). The v3.1.0 release run stopped at Import GPG signing
    key
    because no signing key is provisioned in CI; the staged assets come from
    that run's build artifact.
  • The v3.0.0 known issues listed below remain open unless separately closed.

Download and verify

GitHub caps release assets at 2 GiB per file, so the 3151036416-byte ISO is
published as 16 parts (part-aa … part-ap). Download ALL 16 parts,
SHA256SUMS and SHA256SUMS.asc into one directory.

1. Reassemble (Linux / macOS):

   cat orionx-phoenix-edition-v3.1.0.iso.part-* > orionx-phoenix-edition-v3.1.0.iso

   Windows (cmd, or PowerShell via cmd /c):

   copy /b orionx-phoenix-edition-v3.1.0.iso.part-aa + orionx-phoenix-edition-v3.1.0.iso.part-ab + orionx-phoenix-edition-v3.1.0.iso.part-ac + orionx-phoenix-edition-v3.1.0.iso.part-ad + orionx-phoenix-edition-v3.1.0.iso.part-ae + orionx-phoenix-edition-v3.1.0.iso.part-af + orionx-phoenix-edition-v3.1.0.iso.part-ag + orionx-phoenix-edition-v3.1.0.iso.part-ah + orionx-phoenix-edition-v3.1.0.iso.part-ai + orionx-phoenix-edition-v3.1.0.iso.part-aj + orionx-phoenix-edition-v3.1.0.iso.part-ak + orionx-phoenix-edition-v3.1.0.iso.part-al + orionx-phoenix-edition-v3.1.0.iso.part-am + orionx-phoenix-edition-v3.1.0.iso.part-an + orionx-phoenix-edition-v3.1.0.iso.part-ao + orionx-phoenix-edition-v3.1.0.iso.part-ap orionx-phoenix-edition-v3.1.0.iso

2. Verify. The reassembled ISO MUST hash to:

   38ca9d833e93e53fc6e9dd1bcab68207e2ce37d31d6d51702b67985f983ad6c5

   Linux:   sha256sum -c SHA256SUMS
   macOS:   shasum -a 256 -c SHA256SUMS
   Windows: Get-FileHash orionx-phoenix-edition-v3.1.0.iso -Algorithm SHA256

   SHA256SUMS also lists each part, so a bad download can be pinpointed and
   re-fetched without pulling everything again.

   Then check the signature on the checksums (signing key
   4CB08BD1D0B3281613DD15DB1DCCDF47FEEDEEEF — compare it with the fingerprint published outside this repository):

   gpg --recv-keys 4CB08BD1D0B3281613DD15DB1DCCDF47FEEDEEEF     # or import it from a trusted copy
   gpg --verify SHA256SUMS.asc SHA256SUMS

3. Write to USB (8 GB or larger; the ISO is hybrid: UEFI and legacy BIOS):

   Linux:   sudo dd if=orionx-phoenix-edition-v3.1.0.iso of=/dev/sdX bs=4M status=progress conv=fsync
   macOS:   sudo dd if=orionx-phoenix-edition-v3.1.0.iso of=/dev/rdiskN bs=1m

Do not flash a single .part-* file. It is not bootable on its own.