SECURITY

Trust boundaries, made visible.

Nova separates local SSH credentials, encrypted Team payloads, server-side authorization, and signed software delivery.

Local credentials

Saved SSH passwords and private-key passphrases use Windows Credential Manager. Host keys use trust-on-first-use fingerprints and changed keys block automatic reconnection.

Team encryption

Team Vault items, snippets, runbooks, and multiplayer terminal payloads use authenticated client-side encryption. Workspace keys are stored in the operating-system credential store and wrapped into single-use invite envelopes. The backend enforces roles but receives ciphertext rather than secret content.

Important boundary

Endpoint compromise can still expose plaintext while it is displayed or used. Removing a member stops future server and live-session access, but it cannot erase secrets that member already decrypted or copied. Rotate affected SSH credentials after an untrusted member is removed.

Software updates

Nova accepts update artifacts only when their signature verifies against the updater public key embedded in the app. SHA-256 checksums and detached updater signatures are also published on the Downloads page. Authenticode publisher identity is tracked separately from updater integrity.

Payment verification

TON wallet UI success is not trusted. The billing service verifies the destination, exact nanotons amount, exact invoice comment, transaction time window, and unique transaction hash from the blockchain before extending access.

Reporting a vulnerability

Email reproduction steps, affected version, impact, and minimal logs to security@novassh.space. Remove passwords, keys, tokens, and customer data. We will acknowledge a valid report as soon as practical. No public bug-bounty payment is promised unless agreed in writing beforehand.