Repository navigation
Paranoia 0.5.1 — security release
Paranoia 0.5.1 is a security release. It brings the project in line with the Altumptic Product Security Baseline, product class C (local-first tooling), and is the first release you can verify end to end.
PSB-C · SIGNED · ATTESTED · SBOM · NO-TELEMETRY · LOCAL-FIRST · AUDIT:NONE · DISCLOSURE:OK
Downloads
- Paranoia-Setup-0.5.1.exe: the Windows installer (per-user, no admin rights needed)
- Paranoia-0.5.1-portable.exe: a portable build in a single file
- SHA256SUMS and SHA256SUMS.sigstore.json: the checksums and their Sigstore signature
- paranoia-v0.5.1.cdx.json: the SBOM (CycloneDX). Known gap: it lists the Rust crates but not the npm packages (Electron, React and the other UI libraries), because the scanner skipped development dependencies. The pipeline is fixed for the next release, which will ship separate, complete Rust and npm SBOMs. Until then,
package-lock.jsonat tag v0.5.1 is the exact npm dependency list.
Build-provenance and SBOM attestations are attached to every executable. To check a download, see docs/VERIFY.md:
cosign verify-blob SHA256SUMS --bundle SHA256SUMS.sigstore.json \
--certificate-identity-regexp '^https://github\.com/Altumptic/paranoia/\.github/workflows/ci\.yml@refs/tags/v' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
gh attestation verify Paranoia-0.5.1-portable.exe --repo Altumptic/paranoiaThe executables are not Authenticode-signed yet, so Windows SmartScreen may warn on first launch. This is tracked as exception PSB-EX-1, expiring 2027-04-30.
Security changes
- Electron 38 → 44.9.3. This fixes more than 30 published Electron advisories, including a context-isolation bypass (GHSA-h7rp-cf8h-j98x).
npm auditandcargo auditreport no known vulnerabilities. - IPC sender checks. Every request to the main process must come from the app's own page.
- File allow-list. The engine opens only files you chose: through a dialog, on the command line, by drag and drop, or from the recent list. A compromised page can no longer read arbitrary files.
- Native confirmations. Starting the debugger and running Python scripts now ask in a dialog that the page cannot answer on your behalf.
- No
evalin the page. The Content-Security-Policy no longer allows'unsafe-eval'. JavaScript console scripts run in an isolated worker with no DOM and no access to the desktop bridge. - Electron fuses.
RunAsNode,NODE_OPTIONSand--inspectare disabled, the asar integrity check is enforced, and DevTools are off in packaged builds. - Python hardening. Scripts run from a fresh private temporary folder with
-E, so planted modules or a straypython.exein the working folder are ignored. This applies to both the app andparanoia script. - Engine robustness. Fuzzing found and fixed a crash on a truncated instruction at the end of RISC-V and MIPS code. New noise tests cover the decoders and the
.patand C-type parsers. - Supply chain. CI actions are pinned to commit SHAs, dependency audits block releases, and the release job holds the only write permissions. Signing uses short-lived OIDC credentials, so no long-lived keys are stored.
Fixes
- Decompiler argument order. Stack slots addressed through a copy of
rsp(MSVC'smov rax, rspprologue) now get the same names asrsp-based ones. Arguments of such calls were previously shifted by one slot. - Register saves through
r11/raxare hidden in pseudocode. - Imports by ordinal are named
Ordinal_N.
Changes you may notice
- Local data now lives in
%APPDATA%\Paranoia. The previous folder (%APPDATA%\@paranoia\desktop) is moved there automatically on first start. - The first Python script in each session asks for confirmation.
Documentation
- SECURITY.md: how to report a vulnerability.
- docs/SECURITY-DESIGN.md: trust boundaries, threat model, non-goals, data inventory and known limits.
- docs/VERIFY.md: how to verify a download.
- docs/PSB.md: baseline status and exceptions, each with an expiry date.
No independent security audit has been performed yet (AUDIT:NONE).