Skip to content

Nomad Launcher v1.0.2

Choose a tag to compare

@cyph3rpuNk-dev cyph3rpuNk-dev released this 12 Jul 01:17
· 12 commits to main since this release

Bug-fix release.

Fixed

  • Silent exit when the status window cannot be created (#27). The launcher's status window requires OpenGL 2.0+. Virtual machines without 3D acceleration (VirtualBox without Guest Additions, Hyper-V's basic display adapter, VMware without "Accelerate 3D graphics") only expose Windows' software GL 1.1, so every launcher appeared to simply not run: no window, no error, just a line in Nomad/nomad.log. Launch failures now surface in an error dialog with VM-specific guidance, and crashes anywhere on the launch path are caught and shown the same way instead of dying silently. The README gained a matching troubleshooting entry.

    Note that this makes the failure diagnosable rather than the VM supported: running Nomad in a VM still requires enabling 3D acceleration in the hypervisor.

Changed

  • pgp 0.14.2 → 0.20.0. The crate that performs GPG signature verification of browser downloads was upgraded six minor versions, and Nomad's verification code was ported to its reworked API. Verification behavior is unchanged: armored-first/binary-fallback signature parsing, primary-key-then-subkeys checking, and the pinned-fingerprint tests for the embedded Mozilla, Mullvad, and gorhill keys all pass unmodified.

Signing key rotated

Access to the previous release signing key (4D92 5DAD 1DB4 405C 99EA 1FD3 9984 5DA3 20CD 1F37) was lost, so it has not been revoked, and releases up to and including v1.0.1 remain verifiable against it. Starting with this release, SHA256SUMS.asc is signed by a new key:

  • New key: Nomad Launcher, fingerprint 4F90 CF11 723D C3A2 E719 8331 FEF9 81E9 09EF 44ED (ed25519, expires 2029-07-11)
  • The updated nomad-release-signing-key.asc ships with this release and in the repository.

Verify

gpg --import nomad-release-signing-key.asc
gpg --verify SHA256SUMS.asc SHA256SUMS
sha256sum -c SHA256SUMS

Signing key: Nomad Launcher, fingerprint 4F90CF11723DC3A2E7198331FEF981E909EF44ED.

The launchers are intentionally not Authenticode-signed; release integrity relies on the GPG-signed SHA256SUMS.