Skip to content

v0.1.1 — Signed installers

Choose a tag to compare

View all tags
@trezero trezero released this 07 May 22:47
· 17 commits to main since this release
v0.1.1
d1234f2

Maintenance release — installers are now Authenticode-signed and the auto-signing pipeline is wired into tauri build. No app behavior changes from v0.1.0; this release exists to fix a packaging-level bug.

What changed

  • Both the NSIS .exe and the .msi are signed with the project's self-signed code-signing cert (CN=Local SuperWhisper Dev, O=Workflow Intelligence Nexus, C=US, valid through 2029-05-07). Signing is now automatic on every npm run tauri -- build — no manual signtool step.
  • A new signing/ folder in the repo documents the cert setup, the build-machine import flow (signing/install-signing-cert.ps1), and the end-user trust flow (signing/trust-cert.ps1). See signing/README.md for full detail.
  • manage.ps1 adds an uninstall command (and interactive menu option 9) for clean-slate testing of the installer on a dev box. Tears down PM2, app data, and any prior NSIS install so a fresh installer run starts from zero.

Why this release exists

In v0.1.0 the unsigned .exe and .msi carried a Mark-of-the-Web tag from GitHub Releases (Zone.Identifier:$DATA, ZoneId=3). On default Windows 10/11 configurations, double-clicking either file produced no visible response at all — the installer process never started, no error dialog, no SmartScreen warning, just nothing. The combination of MOTW + unsigned + a hidden UAC consent prompt made the installer look completely broken even though the bits were fine.

Signing the installers (with a cert that's trusted on the target machine) eliminates that silent block: SmartScreen lets the file through, and the UAC prompt now displays a verified publisher name instead of "Unknown publisher." Internal team users can run signing/trust-cert.ps1 once to import the public cert into their machine's Trusted Root + Trusted Publisher stores.

Install (Windows)

  1. Download Local.SuperWhisper_0.1.1_x64-setup.exe below.
  2. First-time only: if your machine doesn't already trust the project's signing cert, you'll see a SmartScreen warning. Either:
    • Click More info → Run anyway (the signature is valid, just not chained to a CA you've imported), OR
    • Get signing/cert.cer from a teammate and run .\signing\trust-cert.ps1 from an elevated PowerShell. After that, future installers run with no warning.
  3. Launch from the Start Menu or system tray.
  4. On first run: pick a hotkey (F9–F12 are most reliable) and configure your Faster-Whisper API endpoint, key, and microphone.

The MSI is also attached for enterprise / Group Policy deployments.

You need a running Faster-Whisper server with an OpenAI-compatible /v1/audio/transcriptions endpoint. See the README for a recommended docker-compose snippet.

Verifying the download

SHA256 (Local.SuperWhisper_0.1.1_x64-setup.exe) = 4EFD3CA84C577459515DF832C7D3CC2B483F119B196F14EED65E1DBAE051BF1F
SHA256 (Local.SuperWhisper_0.1.1_x64_en-US.msi) = 93F07D73324F6C6DDCC898EA64A7A25DE9D8AB73825CC5CEFC1533D50E729EC5

Get-FileHash "Local.SuperWhisper_0.1.1_x64-setup.exe" -Algorithm SHA256
Get-AuthenticodeSignature "Local.SuperWhisper_0.1.1_x64-setup.exe" | Format-List

Get-AuthenticodeSignature should report the publisher as CN=Local SuperWhisper Dev, O=Workflow Intelligence Nexus, C=US and Status: Valid if you've already trusted the cert (or UnknownError if not — the signature is still cryptographically intact, Windows just can't chain it to a Trusted Root).

Carries forward from v0.1.0

The v0.1.0 release notes still apply — reliability fixes (tray click handling, settings window restore, first-run hotkey setup), performance (~0.5–0.7 s warm transcription against a local Faster-Whisper container), and Linux support (Ubuntu 22+, X11). See the v0.1.0 release for the full list.

Known limitations

  • Self-signed cert. Trust is per-machine. For broad public distribution we'd need a commercial OV/EV cert or Azure Trusted Signing — see signing/README.md.
  • Modifier-only hotkeys (Ctrl, Alt, Shift alone) are not supported by tauri-plugin-global-shortcut. Use F-keys or letter+modifier combos.
  • WSL2 / WSLg: the system tray doesn't render under WSLg. Build/run on Windows native or a Linux desktop session for tray-based testing.
Assets 4
Loading