Menu

ChronoLock: The Anti-SaaS Secret Link
📰

ChronoLock: The Anti-SaaS Secret Link

DEV Community: rust·NueM8·8 days ago
#4SwWCWfV
#devtorust#devto#dev#secret#ciphertext
Long article (576 words) — no AI summary yet.
Reading 0:00
15s threshold

Most “secure share” tools still touch your secret.

They encrypt on their servers, require accounts, log metadata, or retain the ability to decrypt later. ChronoLock does none of that.

It encrypts in the browser. The server only ever sees ciphertext. There is no account and no telemetry. When the lifetime ends or the secret is revealed once (if you choose), it is gone.

The full source is public: github.com/Nuem8/ChronoLock (GPL-3.0).

The core rule

Everything sensitive happens in the browser using the Web Crypto API.

A random 32-byte key and 12-byte IV are generated locally. The secret is encrypted with AES-GCM before anything is uploaded. The server receives only the ciphertext plus a few flags (TTL, burn-after-read, whether it is locked to a public key).

You can verify this in two ways:

Open DevTools → Network while creating a secret. Only ciphertext leaves the browser.

Read the source. The encryption path is in the web client; the server never sees key material.

Two ways to lock a secret

1.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.