ConfigDeck

How the encryption works

Your server and your browser talk through our relay, but the relay can't read anything. This is the design, in full.

The link

When you run /configdeck edit, the plugin creates a random session id and a random 256-bit link key. The link looks like https://configdeck.net/s/<id>#k=<key>. The key is in the fragment (after #), which browsers never send to any server; the page reads it and removes it from the address bar right away.

The handshake

The browser and the plugin each pick a random nonce and exchange them in a first message encrypted with a key derived from the link key. Both then derive the session key with HKDF-SHA256 (RFC 5869) from the link key and both nonces, and a four-digit verification code from the same material. You compare the code on the page with the one in your chat: if someone tampered with the link or sits in the middle, the codes differ and the page refuses to open.

Every message

Each message is encrypted with AES-256-GCM and a fresh random IV. The session id, direction and a sequence number are authenticated with it, so the relay can't change, reorder or replay messages without the other side noticing. The relay only forwards opaque envelopes and sees their size and timing.

Secrets

Values that look like passwords or tokens are detected on the server and never sent to the browser — not even encrypted. Changing them sends only the new value, and needs the configdeck.sensitive permission.

On the server

The plugin only reads and writes inside the server folder, never follows links out of it, validates every change, keeps a backup, writes atomically and checks the result before reporting success. Reload commands come from signed schemas or your own config and must pass a whitelist.

Found a problem? See Security.