| Filename | Latest commit message | Latest commit date |
|---|---|---|
Step 3 of ADR 0044 (D3, D18, D19). A shared space's data keys are sealed on a device to each member's public keys; the instance keeps what devices sealed and never opens it. - halkyon_keys: the safety code of two accounts' public keys (`safetyCode`), 60 digits, the same on both sides. - halkyon_base: the register hands out accounts' public keys (`public-keys-of`, local and remote); the table `shared_space_key` and the endpoint `sharedSpaceKeys` (memberKeys, keysNeeded, seal, mine). Only the Owner and Editors seal, the first key sealed to a member stays, and a member's keys go with their membership. Every host's migration creates the table. - halkyon_app: `ContentCipher` seals a key to another account and opens one sealed by another; `SharedKeys` shares a space's key with its members, seals keys to newcomers and opens the person's own, holding each member to the public keys `KeyPins` pinned on first sight (`key_pins.json` in the person's folder), a change refused until trusted anew. Learn takes them into its `Privacy` in step 4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me> |
||
| .. | ||
| lib | ||
| test | ||
| .gitignore | ||
| analysis_options.yaml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| pubspec.yaml | ||
| README.md | ||
halkyon_base_client
The client of halkyon_base, generated by Serverpod:
what a Halkyon app calls to sign in, to manage its account, and to learn an instance's
basics, under client.base in the app's own client. Never edited by hand; run
serverpod --no-analytics generate in halkyon_base_server instead.
The one exception is SRP-6a's client half (ADR 0017), written by hand beside the
generated code, which the generator leaves alone (it writes only lib/src/protocol/):
package:halkyon_base_client/srp.dart, tested by dart test here. The module's README
says how it pairs with the register's half.
Under the GNU Affero General Public License 3.0 or later.