Guide / Information security
Encrypting a file protects its contents from someone who only has a copy. Sharing a confidential document also raises questions about who may open it, whether it was altered, and what happens after access is granted. Close Crate and its Open Crate components address different parts of that problem.
.cc container, content is encrypted in chunks for streaming access.Encryption does not erase a copy that someone has already decrypted. Revocation can restrict future access through supported clients, subject to leases and offline windows.
For a developer who needs to seal JSON, messages or file bytes up to 16 MiB for one X25519 recipient. The OCSB1 envelope is separate from a .cc document. Version 0.0.7 is a preview without a stable compatibility promise or independent audit.
Five source-available Rust libraries cover container format, cryptography, protocol messages, policy evaluation and assembly. Your application supplies file access, keys, randomness, networking, time and enforcement.
The separate service under development combines encrypted .cc documents with a viewer and access workflows. Service availability and commercial terms will be announced separately.
No. Once an authorized application exposes plaintext, a recipient or a compromised device may copy it. Access rules depend on the client and deployment.
No. The SDK seals small arbitrary byte values into OCSB1. The .cc document container uses the separate Open Crate core.
No. A hybrid key slot is selected explicitly; every sufficient path to the document key must meet the chosen profile. Author signatures are a separate mechanism. This is not a FIPS certification claim.
The public repositories include source code, examples and integration notes. Start with the SDK for small application data or read the Open Crate documentation for the .cc format and its trust boundary.