Expand description
HttpEncryptionAdmin: changing a workspace’s encryption through the
server’s API.
What the filesystem does with a journal and renames is one call here:
set-up is enableEncryption, a fresh start freshStart, and a change of
words replaceHeader, each atomic on the server. The data key is made
and wrapped on the device, as for every store; the server keeps only the
wrapped key.
Migrating and rotating run the shared engine, run_rewrite, over the
server’s rewrite session: beginRewrite takes a lease, each copy is an
upload into the staged generation, every copy is read back from there,
and commitRewrite switches generation, header, and key at once. The
server is the journal, so any device with the new words can finish it.
Structs§
- Http
Encryption Admin EncryptionAdminfor a passalong-server workspace.