Accounts sync through a server (phase 2, 3.0.0-alpha.3)

README.md

@@ -28,11 +28,11 @@ SecretSpace lives in four repositories:
 
 ## SecretSpace 3 — a test version, not for real passwords yet
 
-`main` is now **3.0.0-alpha.2**, a test step of SecretSpace 3. **For your real
-passwords keep using [2.11.0](https://github.com/usermaneGermane/SecretSpace-Client-Windows/releases/tag/v2.11.0)**,
+`main` is now **3.0.0-alpha.3**, a test step of SecretSpace 3. **For your real
+passwords keep using [2.12.0](https://github.com/usermaneGermane/SecretSpace-Client-Windows/releases/tag/v2.12.0)**,
 which the rest of this README describes. Do not install the test version
 over it: it opens SecretSpace 3 accounts only, so your 2.x vaults would not
-show up (they are not changed or deleted — 2.11.0 opens them again).
+show up (they are not changed or deleted — 2.12.0 opens them again).
 
 What the test version has:
 
@@ -50,15 +50,25 @@ What the test version has:
 - **Importing a 2.x vault.** *Import* lists the 2.x vaults on this PC (or
   takes a `.vault.enc` file) and copies every entry with its history and
   archive state. The 2.x file is only read; its sync settings stay with it.
+- **Sync through your own server** (new in alpha.3). *Settings → Sync →
+  Set up…* puts the account on a SecretSpace Server **2.0** (a test version
+  too) with the server's token as the sign-up code; after that the **Sync**
+  button keeps the vault in step, with the same merge and conflict choices
+  as 2.x. On another device, *Sign in from a server* on the login screen
+  asks for the address, your username and master password and — once per
+  device — the Secret Key. The server stores only what it cannot open: no
+  master password, no Secret Key, no vault key. A master password changed
+  on one device is changed on the server at the same time (it needs the
+  server to be reachable); other devices then sign in again with it.
 - Everything else in the window — entries, archive, history, 2FA codes,
-  generator, plain export — works as in 2.11.
+  generator, plain export — works as in 2.12.
 
-Not in this test version yet: **sync** (the next one adds server accounts),
+Not in this test version yet: more than one vault per account,
 recovering an account with the 12-word phrase (the phrase is made and
-checked now; the screen that uses it comes later), and sharing a vault with
-other people. SecretSpace for Linux has the same test version, 1.0.0-alpha.1.
-Coming next, in this order: sync with accounts on the server, several
-vaults per account, sharing a vault with family or colleagues, and
+checked now; the screen that uses it comes later), sharing a vault with
+other people, and *Sync when I unlock* for accounts. SecretSpace for Linux
+has the same test version, 1.0.0-alpha.3. Coming next, in this order:
+several vaults per account, sharing a vault with family or colleagues, and
 recovering an account with the 12-word phrase.
 
 ## Running it
@@ -252,6 +262,8 @@ SecretSpace-Client-Windows/
     ├── crypto_utils.py  the 2.x container (PMV2), key derivation, encrypt/decrypt
     ├── account_crypto.py  3.0: Argon2id, Secret Key, keyset, PMV3, recovery phrase
     ├── accounts.py      3.0: account folders, unlock, password change, Emergency Kit
+    ├── account_sync.py  3.0: the account on a server (API v2): connect, sync, sign in
+    ├── account_sync_ui.py  3.0: its screens (Set up, Sync, Sign in from a server)
     ├── secret_store.py  3.0: how this PC keeps the Secret Key (DPAPI)
     ├── bip39_words.py   the BIP39 word list for the recovery phrase
     ├── importers.py     CSV/JSON parsing from other password managers