What it is
module-sealed.
The server half of Cratefield’s sealed-blob store (issue #757). A client — the @cratefield/sealed TypeScript package — encrypts data in the browser under a content key that is wrapped once per unlock (a passkey PRF output, or an Argon2id recovery code) and posts the result here. This module stores it, serves it back byte-identical, and never learns what it holds. Erasure is crypto-shred: destroying the wrapped key destroys the data, with no delete-the-row path and no backup to restore from.
From the crate’s own README.
Ports
Kms
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 2 versions recorded, newest first. Every published version is on crates.io.
Other
- updated the following local packages: cratefield-core
Other
- updated the following local packages: cratefield-core
Added
- First release, 0.1.0: the server half of client-side sealed blobs. It stores the ciphertext the
@cratefield/sealedclient produces under a server outer wrap, serves it back byte-identical, erases it by crypto-shredding, and has no server-side recovery path (#757).
One of 76 crates in the harness, all of them MIT and all of them in one repository.