You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Follow-ups from Sasha's 0.8.0 pre-release review (#375) #434
These are the follow-ups from Sasha's pre-release review of #375 (comment 6230061841). Each finding was checked against the code or recorded as unverified. Release-relevant dispositions are on #375. This issue keeps the items that wait until after 0.8.0, so they live in one place.
Sign-in, sign-up and owner-recovery challenge pools: a few IPs can fill them, and behind a proxy every caller shares one quota bucket. Unverified. 0.8.0 does not set up remote or HTTPS Homes, so exposure is local.
Installer trust-root override (Stop Intel Mac before release lookup and pin the verified head CID #398): remove the ELASTOS_MAINTAINER_DID env and flag override in 0.8.1 (option a). The out-of-band check stays as it is documented: compare the installer's printed Maintainer DID: with the README (README "Install from the publisher", docs/INSTALL.md "Compare and change the release signer").
Rollback scope: a normal rollback restores only the five journalled files, not the support binaries or migrated principal roots. Check against the Undo journeys that passed on installed alphas.
Crash recovery: a crash between claim_start and record_started leaves a permanent repair state.
Shutdown: shutdown doesn't stop Runtime process groups it didn't spawn directly.
Fresh source-home setup fails (developer path).
Passkey sign-in for credentials that are not discoverable: if 0.8.0 ships with this as a known issue rather than a fix, add an account-named sign-in fallback in 0.8.1. Irzhy decides the tradeoff that a name lookup could reveal which accounts exist.
Passkey fallback disposition, superseding the last checkbox's "if 0.8.0 ships with a known issue": the fallback ships in 0.8.0. Its disclosure is an accepted 0.8.0 limit, recorded on #375 (decision comment). Before any remote, LAN or HTTPS Home access ships, re-evaluate it: account-first sign-in with stronger limits, or remove the fallback once 0.7.1 credentials are migrated. This includes the case where other OS users on the same machine can call the localhost sign-in route.
Superseding comment 6241284019: the passkey fallback does not ship in 0.8.0. There are no public 0.7.1 users, only Anders's test accounts (#375). The branch fix/080-passkey-named-fallback (e6589f8cc) stays here as the option if a real migration need appears; its disclosure limit would need to be decided then.
Activity
train: merge fix/080-passkey-named-fallback at e6589f8 (0.7.1 passkey…
andersalm commentedon Oct 17, 2026
Passkey fallback disposition, superseding the last checkbox's "if 0.8.0 ships with a known issue": the fallback ships in 0.8.0. Its disclosure is an accepted 0.8.0 limit, recorded on #375 (decision comment). Before any remote, LAN or HTTPS Home access ships, re-evaluate it: account-first sign-in with stronger limits, or remove the fallback once 0.7.1 credentials are migrated. This includes the case where other OS users on the same machine can call the localhost sign-in route.
andersalm commentedon Oct 17, 2026
Superseding comment 6241284019: the passkey fallback does not ship in 0.8.0. There are no public 0.7.1 users, only Anders's test accounts (#375). The branch
fix/080-passkey-named-fallback(e6589f8cc) stays here as the option if a real migration need appears; its disclosure limit would need to be decided then.Revert "train: merge fix/080-passkey-named-fallback at e6589f8 (0.7.1…