a216d1b20a
Both entries now describe shipped designs instead of warnings, and both correct a stated fact that turned out to be wrong: - Recovery-phrase desync: the phrase can't reach the partner via the server in plaintext, but it can travel sealed to the key they already hold — and the wrap moves LAST (publish → both ack → re-wrap). The re-introduction note is now about the shortcut, not the feature: never re-wrap and hope the partner catches up, and never trust a client-written "we're consistent now" field without a rule making it unforgeable — the partner's device acts on it. - Single-device ECIES: the old text claimed a second sign-in overwrites the published pubkey. It doesn't — publishes are existence-gated. The real failure was quieter (no local private key) and mislabelled in the UI as "waiting for partner". Escrow under the couple key heals it; the leakage analysis, the rejected alternatives, and the residual case (device dies before escrowing) are all written down. |
||
|---|---|---|
| .. | ||
| brand | ||
| crypto | ||
| qa | ||
| release | ||
| screenshots | ||
| store | ||
| CopyMigration.md | ||
| Engineering_Reference_Manual.md | ||
| NameChange.md | ||
| copy-guide.md | ||
| date-planning-roadmap.md | ||
| standardization-review.md | ||