# secrets.sgit.ai on public keys: what changed in v1.1.0, sgit.ai > The changes to the article "secrets.sgit.ai on public keys" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [secrets.sgit.ai on public keys](../../secrets-on-public-keys.md) / [Versions](../secrets-on-public-keys.md) / v1.1.0 # secrets.sgit.ai on public keys: what changed in v1.1.0 From v1.0.0 (2026-10-15, `9dede7851`) to v1.1.0 (2026-10-18, this release), paragraph by paragraph. 0 paragraphs added, 0 removed, 1 changed in place, 36 unchanged. About 1 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../secrets-on-public-keys.md) 1 unchanged paragraph Summary: secrets.sgit.ai started on 5 October as the MVP of a password manager unlocked by a passkey, and it is a good example of our non-linear path: its passkey work became the reader's vault on this newsroom, and its own app was never built; its reality page lists 42 claims shipped, all of them the site, the pipeline and the labs, and the app itself as proposed. Now I wantwould like to turn it into a commercial service for one job: moving a secret from A to B. The principle is to stop sharing keys altogether. We tried keys that were easy to use, and the sgit team's own security review found them broken: about 30 bits, a public id that is an unsalted hash of the key, and one precomputed table that opens every one; the command line team disabled creating them in June. So everything moves to public-key cryptography, which the pieces we already have support. Every person, browser and agent has a key pair; the public key is shared freely, by link, QR code, email or WhatsApp; the secret comes back encrypted to it, as a one-time drop, a file or a QR code; and the private key lives in a vault of its own, unlocked by a passkey that Google Password Manager or iCloud Keychain keeps. This site's agent tested the parts that matter: an agent's key pair and a one-time drop, end to end; and a browser key that cannot be exported, which survived a restart and still decrypted. Eight scenarios, what exists for each, what to build, and what to charge for. 35 unchanged paragraphs, under In short {#in-short}, What secrets.sgit.ai is today {#today}, Why no more shared keys {#no-keys}… [all versions](../secrets-on-public-keys.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/secrets-on-public-keys/v1.1.0.html)*