Security posture
What the shipped image does and does not do, stated as commitments.
A KVM has more power over the target machine than any other device on the network: it types as you, sees the screen, and reaches firmware. That is the standard the image is built against, and because the whole stack is open source, every claim here is checkable rather than takeable on faith.
This page states the posture of the shipped image. Where something is still being finished during bring-up, it says so.
No default credentials
The device ships with no accounts. The first visit to the console creates the administrator, and the setup route exists only while the device has zero users. There is no vendor password to look up, on this device or any other, because none exists.
Alongside that, protection against a device being claimed by the wrong person on a shared network is planned: a claim code on the device itself, proving physical possession before setup. Until it lands, the guidance is simple: set the device up when you plug it in, not later.
No baked secrets
Images that ship with pre-generated keys share those keys across every unit sold. The WarpKVM image generates its secrets on the device at first boot: SSH host keys, machine identity, and TLS material. Two kits flashed from the same image have nothing cryptographic in common.
Everything over TLS
The console, the API, and the media stream are served over TLS on port 8443, end to end. The plain-HTTP listener exists only to redirect browsers to the TLS port, and it refuses API requests outright rather than redirecting them, so a credential can never transit in clear even by accident.
Certificates are minted on the device, rotate automatically before expiry without dropping live sessions, and are only minted once the device trusts its clock (see the clock note). Joining your own Tailscale network, with a certificate browsers trust out of the box, is the intended remote-access path and part of the planned guided setup.
Accounts that resist guessing
Passwords are stored with argon2id, a modern memory-hard hash, never reversibly. Sign-in is rate limited: five failures pause attempts from that address for 30 seconds, which makes online guessing impractical without locking you out of your own device. Sessions are cookie-based, scoped to the browser, and expire after 7 days.
Quiet by default
The shipped image runs what the product needs and nothing else:
- No ADB. The stock vendor image ships a debug service that amounts to a root shell on the network; the WarpKVM image removes it.
- SSH is keys-only with root login disabled, and the intent is off entirely until you enable it.
- Inbound is denied by default beyond the console port, with your tailnet as the intended way in from outside the LAN.
- Package sources point at Debian's own mirrors, so updates come from the project, not a third party.
Some of these are the exact items still being closed out during bring-up; they are listed because they are the bar the image must meet to ship, and the open-source image is how you verify it did.
What this page does not claim
No audit of our own daemon by a third party has happened yet. The code is public precisely so that it can be read, and we would rather state that plainly than imply a review that has not occurred.