From 42c05c50e7a867824b922ce537dfaeed27cca18a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=94=D0=BC=D0=B8=D1=82=D1=80=D0=B8=D0=B9?= Date: Wed, 7 Oct 2026 23:12:31 +0500 Subject: [PATCH] Phase 12: gate results in the control protocol document; label of the preferred-name save button Co-Authored-By: Claude Sonnet 5.5 --- docs/CONTROL_PROTOCOL.md | 22 +++++++++++++++++++++- src/screens/BrowsePage.tsx | 2 +- 2 files changed, 22 insertions(+), 2 deletions(-) diff --git a/docs/CONTROL_PROTOCOL.md b/docs/CONTROL_PROTOCOL.md index e07180d..52664fd 100644 --- a/docs/CONTROL_PROTOCOL.md +++ b/docs/CONTROL_PROTOCOL.md @@ -174,7 +174,27 @@ What is delivered instead: the account and its password in the protected store, ## 11. The Phase-12 gate -See section 13 of this document for results (run 2026-10-07/08 with a Host Manager on the real smoke realm *PT Guest* (a real worldserver, MySQL and RA), three Player Managers with their own data folders and DPAPI stores, and the Coordinator on the VPS). +Run on 2026-10-07 with the final code: a **Host Manager** on the real smoke realm *PT Guest* (a real worldserver with its own MySQL and RA, realm id `01a116d9…`, published to the Registry), **three Player Managers** +(separate processes, separate data folders, their own DPAPI stores, fresh identities) and the **Coordinator on the VPS**; every request went Manager → Internet → Caddy → Coordinator → Manager. The scripts are driven through the real Managers' +own commands (`gate12.mjs`, `gate12b.mjs`: the Tauri commands behind the Join panel). Passwords were never printed: they were checked against the realm's stored SRP6 verifier or compared by hash. + +| | Scenario | Result | +|---|---|---| +| **A** | New player: automatic account, credentials saved, game started | **pass, except native prefill** (section 10). `join` with the preferred name `Dmitry` created `DMITRY` on the real realm (the row is in `acore_auth.account`), the 16-character password is saved in DPAPI and its SRP6 verifier equals the realm's, `launch` wrote the realmlist `127.0.0.1:15724` and started `Ascension.exe` (stopped again; the realmlist was restored). The login window is **not** prefilled: name and password are copied/shown in the Manager | +| **B** | The same player again | pass: `created:false, reset:false`, same name, same password, still one account | +| **C** | Occupied name | pass: a second player asking for `Dmitry` got `DMITRY_7FYD` (stable suffix, valid on the realm); after losing the credentials the same name came back with a new password (`reset:true`), the old one stopped working, no second account | +| **D** | Legacy character claimed | pass: a character on a legacy account was refused while the account was not at character select, refused while the character was in the world, then claimed and stored as **canonical revision 1** in the player's Manager; the Host recorded the `PortableCharacterId ↔ PlayerIdentity` binding as acknowledged; the listing then marks it portable | +| **E** | Another PlayerIdentity is refused | pass: another identity cannot link the bound account even with its name and password (`account_taken`), cannot claim the character (`not_yours`) and does not see it in its listing | +| **F** | Unmapped legacy account: one-time link | pass: a wrong password is refused (`wrong_credentials`), the right one links once, the next joins reuse the mapping and create no account; the Host holds the mapping, not the password | +| **G** | A Host on another PC behaves the same | **pass in effect, not on a second physical PC** (none was available): the Player Managers are separate processes with separate data folders that have no realm descriptor, and neither the realm's database password nor its console password nor a `db_password`/`ra_password` key appears in any file of any Player (53 files); no player's password appears in the Host's data (22 files); the whole run above crossed the Internet through the VPS. A Host elsewhere differs only in the machine | +| **H** | Manager restart keeps identity, mapping, protected credentials | pass: after stopping and starting both the Host and a Player Manager the PlayerId, the linked account (still *linked*), the password (same hash), the Host's mapping and claim and the player's character are intact; the Host re-linked to the Coordinator by itself; joining created nothing new. A Coordinator restart: the Host link came back in 5 s and joining worked at once; a Registry restart did not disturb joining | +| **I** | VPS inspection | pass: the Coordinator's logs, the Registry's logs, Caddy's logs, a full `pg_dump` of the Registry database, the Coordinator container's settings and every non-secret file under `/opt/coa` contain **none** of: the players' passwords, the legacy password, the realm's database password, the account names `DMITRY`/`LEGACYA`, the character's name, the word `payload`, the descriptor key `ra_password`; the Coordinator's role can read `realms.public_key` and cannot read `display_name`, insert or update; the Coordinator container has a read-only root; the node still listens on 22, 80 and 443 only. (The wire itself is covered by `a_new_player_gets_an_account_and_keeps_it` in `services/coa-control-e2e`: a recording tap on the WebSocket sees 500+ bytes of traffic and none of the password, the name, `Provision` or `password`; and by the character-claim test for the payload)| +| **J** | Phases 1–10 still pass | pass: `cargo test --workspace` 595 passed / 0 failed (48 ignored: they need live fixtures); Registry 14, Registry e2e 12, Coordinator 11, control e2e 10; the Phase-9 live suite against a real worldserver (`live_service`: *make portable on a running realm is armed without a restart*, *a restart with nothing to report makes no revision*, *one-click play of a level 80 on a cap 60 realm survives navigation, a restart and the logout*) 3/3; the Phase 10 live gates 1–12 and the restart gates 2/14 re-run against protocol 2. One pre-existing test (`ra::tests::creates_an_account_over_ra_…`, a loopback fake of the console) failed once in a full parallel run and passes alone and on re-run: the flake that was already known | +| K | The owner's choice shows in the public list | pass: *existing accounts only* appears as `{automatic:false, existing_only:true}` in the Registry's record within two heartbeats and back to automatic when switched off | + +**What was simulated.** "At the character-select screen" is what the worldserver records as `account.online = 1` with no `characters.online` row for the account. The gate set `account.online` itself (and the character's `online` +for the in-world refusal) instead of logging in with the game: the Manager must not drive the game's window, and nothing here automates it. The Host's check reads exactly those two facts from the realm's database; a real session sets the first. The claim code path +(listing, ownership, eligibility, export, hash-verified adoption, acknowledgement) was run for real. ## 12. Threat notes diff --git a/src/screens/BrowsePage.tsx b/src/screens/BrowsePage.tsx index cec6fdd..9e10931 100644 --- a/src/screens/BrowsePage.tsx +++ b/src/screens/BrowsePage.tsx @@ -233,7 +233,7 @@ export function BrowsePage() {
{ setPreferred(e.target.value); setPreferredNote(null); }} className="w-44 rounded-md border border-line bg-card px-3 py-1.5" data-testid="preferred-name" /> - + {preferredNote && {preferredNote}}

{t("join.preferredHint")}