on master help sign in
28 files changed+6762−863
since splitsnapshots
unifiedsplit
.github/workflows/build.yml+2−2 AGENTS.md+2−2 AUDIT-DEEP.md+230 AUDIT-FFI-PHONEMIC-APPLE.md+470 AUDIT-FRESH.md+385 AUDIT-NEW.md+816 Cargo.lock+1 Cargo.toml+2−1 PROTOCOL-REVIEW.md+231−7 PROTOCOL.md+138−36 apple/SkrepkaApp/Core.swift+23−16 apple/SkrepkaApp/Effects.swift+98−3 apple/SkrepkaApp/Forms.swift+9 apple/SkrepkaApp/PhotoPicker.swift+23−1 apple/SkrepkaApp/QRView.swift+36−2 apple/SkrepkaApp/SkrepkaApp.swift+152−6 apple/SkrepkaApp/Views.swift+68−13 apple/project.yml+8 core/Cargo.toml+1 core/src/app.rs+2737−245 core/src/crypto.rs+413−80 core/src/ffi.rs+5 core/src/model.rs+65−2 core/src/phonemic.rs+65−6 core/src/protocol.rs+77−32 install.sh+13−9 server.knot+692−400 server.o
.github/workflows/build.yml+2−2
@@ -157,7 +157,7 @@ jobs:
157157
158158 PK=$(printf '0%.0s' $(seq 1 64)) # 64 hex chars: a well-formed pubkey
159159 SIG=$(printf '0%.0s' $(seq 1 128)) # 128 hex chars: a well-formed signature
160− BLOB=$(printf 'ab%.0s' $(seq 1 200)) # 400 hex chars: over the 336-char floor
160+ BLOB=$(printf 'ab%.0s' $(seq 1 200)) # 400 hex chars: over the 346-char floor
161161
162162 # $1 = expected status, $2 = label, rest = curl args
163163 expect() {
@@ -199,7 +199,7 @@ jobs:
199199 -X POST http://127.0.0.1:8080/federation/forward -H "$J" \
200200 -d "{\"toKey\":\"$PK\",\"encryptedBlob\":\"$BLOB\"}"
201201
202− # Below the 336-hex-char (168-byte) minimum envelope: rejected by BlobHex
202+ # Below the 346-hex-char (173-byte) minimum envelope: rejected by BlobHex
203203 # at the route boundary, before the federation gate.
204204 expect 400 "federation/forward (undersized blob rejected)" \
205205 -X POST http://127.0.0.1:8080/federation/forward -H "$J" \
AGENTS.md+2−2
@@ -11,7 +11,7 @@ Decentralized, end-to-end encrypted messenger. No accounts, no home servers —
1111- **Apple shell:** Swift + SwiftUI, **iOS 17+ only** (`include_macos = false` in `core/boltffi.toml`). The shell is a thin effect executor — it performs HTTP, key-value, and timer effects and renders the `ViewModel`. It contains no business logic.
1212- **Crypto:** `ed25519-dalek` + `x25519-dalek` + `curve25519-dalek`, `chacha20poly1305` (XChaCha20-Poly1305), `hkdf` + `sha2` (HKDF-SHA256), `zstd` (plaintext compression). **No libsodium** — `core/src/crypto.rs` hand-reimplements libsodium's `crypto_sign_ed25519_{pk,sk}_to_curve25519` so blobs stay wire-compatible with any spec-following client.
1313- **Server:** `server.knot`, written in [Knot](https://github.com/ilyakooo0/knot) — a custom functional language compiled to a native binary. Its runtime transparently persists every `*ref` to SQLite, so all server state (`*sessions`, `*messages`, `*presence`, …) survives restarts despite reading like in-memory lists.
14−- **Persistence (client):** `crux_kv` — JSON blobs under the keys `settings`, `profile`, `contacts`, `cursor`, `outbox`, and `messages:<peer_hex>`. The Swift shell backs this with one file per key under Application Support. The 64-byte Ed25519 secret key lives in the iOS Keychain, never in kv.
14+- **Persistence (client):** `crux_kv` — JSON blobs under the keys `settings`, `profile`, `contacts`, `cursor`, `outbox`, `seen_ids`, and `messages:<peer_hex>`. The Swift shell backs this with one file per key under Application Support. The 64-byte Ed25519 secret key lives in the iOS Keychain, never in kv.
1515
1616## Project Layout
1717
@@ -95,7 +95,7 @@ Two kinds of `Event` variants, and the distinction matters:
9595
9696The `ViewModel` is deliberately flat and stringly-typed (`page: String`, `conn_status: String`) so the Swift side switches on plain strings rather than needing generated enums for UI state.
9797
98−Runtime flow: `IdentityLoaded` (from the Keychain, at boot) fans out five kv loads → `LoadedSettings` triggers `Connect` → `Authenticate` (challenge/verify, signature bound to the server's bare hostname under the `skrepka-auth-v1:` tag) → on a token, `Poll` (server long-polls ~25 s, client re-polls immediately) and `StartFlush` (drains the outbox one message at a time, encrypting at send time). Failures back off via `crux_time` — 3 s doubling to a 30 s cap.
98+Runtime flow: `IdentityLoaded` (from the Keychain, at boot) fans out six kv loads → `LoadedSettings` triggers `Connect` → `Authenticate` (challenge/verify, signature bound to the server's bare hostname under the `skrepka-auth-v1:` tag) → on a token, `Poll` (server long-polls ~25 s, client re-polls immediately) and `StartFlush` (drains the outbox one message at a time, encrypting at send time). Failures back off via `crux_time` — 3 s doubling to a 30 s cap.
9999
100100## Code Conventions
101101
AUDIT-DEEP.mdnew file+230
@@ -0,0 +1,230 @@
1+# Skrepka Deep Audit — app.rs & model.rs (2026-07-16)
2+
3+**Scope:** Deep audit of `core/src/app.rs` and `core/src/model.rs`, cross-referenced against PROTOCOL.md §4, §6, §9, §10 and existing audits (AUDIT-NEW.md, AUDIT-FRESH.md, PROTOCOL-REVIEW.md). Findings below are **not** documented in any prior audit.
4+
5+**Legend:** 🔴 critical · 🟠 high · 🟡 medium · 🔵 low · ⚪ info
6+
7+---
8+
9+## 1. State Machine — Poll Loop / Cursor / Budget
10+
11+### 🟡 D1. `events_stored` doesn't count successfully-decrypted-but-non-stored events — livelock on budget exhaustion
12+
13+**Type:** State machine bug (livelock)
14+**File:** `core/src/app.rs:2127, 2188-2200, 2248-2293, 2316, 2342-2349`
15+
16+The `events_stored` counter drives the cursor-restore decision on budget/count exhaustion (lines 2145-2147, 2163-2165): if `events_stored == 0`, the cursor is restored to `prev_cursor`, and the relay re-serves the same page on the next poll.
17+
18+`events_stored` is only incremented for:
19+- Text messages that **pass** dedup (line 2264 — inside `if !id_set.contains`)
20+- All `delivery.ack` payloads (line 2316)
21+- Profiles that **pass** staleness (line 2348 — inside `if ts >= c.last_profile_ts`)
22+
23+It is **NOT** incremented for:
24+- **Duplicate text messages** (line 2248: the `if !id_set.contains` block is not entered)
25+- **Stale profiles** (line 2342: the `if ts >=` block is not entered)
26+- **Profiles from strangers** (line 2327: `continue` before any increment)
27+- **Self-messages** (line 2188: `continue` before any increment)
28+- **Blocked-sender messages** (line 2198: `continue` before any increment)
29+
30+All of these are **successfully decrypted** — they consume the full AEAD decrypt cost and the per-blob byte budget — but they don't increment `events_stored`. If a poll page consists entirely of such events and the byte budget is exhausted mid-page, `events_stored == 0`, the cursor is restored, and the client re-polls with the old cursor. The relay re-serves the same page. **Livelock.**
31+
32+**Attack scenario:**
33+1. Client receives 4 large blobs (each ~20 MiB decoded, total ~80 MiB > 64 MiB budget).
34+2. First encounter: all 4 are new text messages. `events_stored = 3` (budget exhausted on 4th). Cursor kept at `page.cursor`. Relay deletes events. No issue.
35+3. **Hostile relay re-serves the same 4 blobs** (it kept copies despite cursor advance). All 4 are now duplicates. Budget exhausted on 4th blob. `events_stored == 0`. Cursor restored to `prev_cursor`.
36+4. Client re-polls with `prev_cursor`. Relay re-serves same 4 blobs. Go to 3. **Permanent livelock** — the client can never advance past this page, wasting bandwidth and battery on every cycle.
37+
38+The same pattern applies to a page of large stale profile blobs, large profile-from-stranger blobs, or large self-message echoes — all decrypt successfully, all are dropped, none increment `events_stored`.
39+
40+**Note:** AUDIT-FRESH.md N9 identified the budget-exhaustion livelock for the case where blobs **fail decryption** (events_stored == 0, hostile junk). The fix applied (keep cursor if `events_stored > 0`) addresses that case. But the **duplicate/stale/stranger/self/blocked** cases are different: the blobs ARE decryptable, the client DID process them (and doesn't need them again), but `events_stored` doesn't reflect this. This is a new variant of the N9 livelock that the existing fix does not cover.
41+
42+**Suggested fix:** Increment `events_stored` after successful decryption and parse, regardless of whether the event is stored:
43+```rust
44+let Ok(dec) = crate::crypto::decrypt(&id, &blob) else { continue; };
45+let Some(parsed) = protocol::parse_payload(&dec.plaintext) else { continue; };
46+events_stored += 1; // successfully decrypted — cursor can advance past this
47+```
48+This ensures the cursor is kept whenever at least one event was successfully processed (even if it was a duplicate/stale/stranger), breaking the livelock. The unprocessed tail (budget exhaustion) is still lost, but that's the accepted N9 tradeoff.
49+
50+---
51+
52+### 🔵 D2. `SetServerUrl` resets `send_retries` but not `poll_retries` — new relay inherits stale poll backoff
53+
54+**Type:** State machine bug (stale state on relay switch)
55+**File:** `core/src/app.rs:960`
56+
57+When switching relays, `SetServerUrl` resets `send_retries = 0` (line 960) and `flush_paused_until = 0` (line 959), with the comment: "The old relay's rate limit was the old relay's opinion. A new one is entitled to take our sends immediately."
58+
59+The same logic applies to `poll_retries` — it's the old relay's poll failure count — but it is **not reset**. If the old relay was failing (e.g., 5xx storm), `poll_retries` could be at 4 (backoff = 30s). The first poll to the new relay fails (e.g., transient network issue), and `backoff_poll` uses `backoff_ms(5) = 30s` instead of starting at 3s. The new relay's poll loop is penalized for the old relay's failures.
60+
61+**Attack scenario:** No attack needed — this triggers on any relay switch after a period of poll failures. The user switches to a healthy relay but experiences unnecessarily long poll backoffs.
62+
63+**Suggested fix:** Add `model.poll_retries = 0;` alongside `model.send_retries = 0;` at line 960.
64+
65+---
66+
67+## 2. State Machine — Outbox / Flush
68+
69+### 🔵 D3. `SendResult` pops outbox items even when `kv_load_failed` is set — duplicate sends on relaunch
70+
71+**Type:** State machine bug (write guard gap)
72+**File:** `core/src/app.rs:1547-1560, 1728-1733`
73+
74+If `kv_load_failed` is set (by a `LoadedMessages` failure) while a send is in flight, `SendResult` still pops the batch from `model.outbox` (line 1557-1559) on a 200 or 400. The subsequent `persist_outbox` (line 1560) calls `refuse_write`, which checks `kv_load_failed` and refuses the write. The items are removed from the in-memory outbox but **not from the on-disk outbox**.
75+
76+On relaunch, the outbox is re-loaded from disk — the popped items are still there. They are re-sent:
77+- For a **200** (relay accepted): duplicate sends. The recipient's dedup handles it, but the sender wastes bandwidth and the recipient sees duplicate delivery attempts.
78+- For a **400** (relay rejected): the items are re-sent and re-rejected, burning retry budget.
79+
80+**Timeline:**
81+1. Startup loads complete. `Connect` → `Authenticate` → `VerifyResult` → `Poll` + `StartFlush`.
82+2. `StartFlush` sends a batch. `flushing = true`, `in_flight` is set.
83+3. `LoadedMessages` for some peer fails. `kv_load_failed = true`.
84+4. `SendResult` arrives (200). `flushing` cleared, batch popped (line 1557-1559). `persist_outbox` refused (line 1729-1730).
85+5. On relaunch: outbox loaded from disk. Items re-sent.
86+
87+**Note:** The window is narrow — `LoadedMessages` is a lazy load triggered by `LoadedContacts`, and `StartFlush` fires from `VerifyResult` which also fires after startup loads. But the ordering is: startup loads → `Connect` → `Authenticate` → `VerifyResult` → `StartFlush` + `Poll` → `LoadedMessages` (lazy). So the send can be in flight when `LoadedMessages` fails.
88+
89+**Suggested fix:** Check `kv_load_failed` before popping in `SendResult`. If set, don't pop — leave items in the outbox for relaunch to handle:
90+```rust
91+if ((200..300).contains(&status) || status == 400) && !model.kv_load_failed {
92+ // pop and persist
93+}
94+```
95+Alternatively, don't pop if `persist_outbox` was refused (check the return of `refuse_write`).
96+
97+---
98+
99+## 3. Model / Persistence
100+
101+### 🔵 D4. `now_ms()` returns 0 on system clock failure — outbox TTL disabled
102+
103+**Type:** Robustness gap
104+**File:** `core/src/app.rs:580-585`
105+
106+```rust
107+fn now_ms() -> i64 {
108+ SystemTime::now()
109+ .duration_since(UNIX_EPOCH)
110+ .map(|d| d.as_millis() as i64)
111+ .unwrap_or(0)
112+}
113+```
114+
115+If the system clock is before `UNIX_EPOCH` (misconfigured device, RTK bug, NTP step), `now_ms()` returns 0. Consequences:
116+
117+- **Outbox TTL disabled:** `first_attempt` is stamped as 0 (line 1990-1993). `OutboxItem::is_expired` checks `first_attempt > 0` (line 170) — 0 means "never attempted," so the TTL never applies. Stuck items are retried forever (only the retry counter bounds them, which at 10 retries with slow backoff could take days).
118+- **`flush_paused_until` bypassed:** `now_ms() < flush_paused_until` → `0 < 0` → false. Flushing proceeds immediately, ignoring a relay's `Retry-After`.
119+- **`last_ack_ts` / `last_profile_ts` clamped to 0:** `ts.min(now)` → `ts.min(0)` → 0 (if ts is positive). All future acks/profiles pass the staleness check (any ts >= 0). Dedup is weakened.
120+
121+**Attack scenario:** No attack — this is a device misconfiguration. But on iOS, a clock that briefly reads as pre-epoch during boot could trigger this transiently.
122+
123+**Suggested fix:** Use `UNIX_EPOCH` as the floor instead of 0:
124+```rust
125+fn now_ms() -> i64 {
126+ SystemTime::now()
127+ .duration_since(UNIX_EPOCH)
128+ .map(|d| d.as_millis() as i64)
129+ .unwrap_or(1) // 1, not 0 — 0 is a valid "never attempted" sentinel
130+}
131+```
132+Or better: propagate the error and have callers handle clock failure explicitly.
133+
134+---
135+
136+### 🔵 D5. `LoadedMessages` merge doesn't update `seen_ids` — weakened dedup after `seen_ids` load failure
137+
138+**Type:** Dedup gap
139+**File:** `core/src/app.rs:815-856`
140+
141+The `LoadedMessages` handler merges on-disk messages into the in-memory conversation (union by ID, re-sort, trim). But it does **not** add the on-disk message IDs to `model.seen_ids`.
142+
143+When `seen_ids` loads successfully from kv at startup, this is fine — the on-disk IDs are already in the set. But when `seen_ids` **fails to load** (line 807-811, non-fatal), the set is empty. The `ingest_poll` seeding at line 2244-2246 seeds from the conversation:
144+```rust
145+if id_set.is_empty() {
146+ id_set.extend(convo.iter().map(|m| m.id.clone()));
147+}
148+```
149+
150+If a poll arrives **before** `LoadedMessages` for a peer, the conversation is empty (not loaded yet). The seeding adds no IDs. The poll's messages are stored and their IDs are added to the set. Later, `LoadedMessages` arrives and merges the on-disk messages — but their IDs are **never** added to `seen_ids` (the merge doesn't touch `seen_ids`, and the seeding only runs when `id_set.is_empty()`, which is no longer true after the poll).
151+
152+**Result:** On-disk message IDs are missing from `seen_ids`. Future replays of those on-disk messages pass the dedup check (line 2248) and are re-inserted into the conversation. The `LoadedMessages` merge filters duplicates by ID (line 830), so the conversation doesn't grow unboundedly — but each replay is processed (decrypted, inserted, acked) before the merge catches it.
153+
154+**Attack scenario:**
155+1. `seen_ids` kv load fails (device locked, file corruption).
156+2. `LoadedContacts` triggers `LoadedMessages` for peer P.
157+3. A poll arrives before `LoadedMessages` for P. P's conversation is empty. `seen_ids[P]` is seeded as empty.
158+4. Poll stores new messages, adds their IDs to `seen_ids[P]`.
159+5. `LoadedMessages` for P arrives. On-disk messages are merged into the conversation. Their IDs are NOT added to `seen_ids[P]`.
160+6. A replay of an on-disk message arrives. Its ID is not in `seen_ids[P]`. It passes dedup. It's inserted and acked.
161+
162+**Impact:** Weakened dedup — replays of on-disk messages are re-processed (decrypted, stored, acked). No permanent data corruption (the merge prevents duplicate conversation entries), but the recipient sends spurious delivery acks for old messages, and the sender receives false "delivered" confirmations.
163+
164+**Suggested fix:** In the `LoadedMessages` merge, add the on-disk message IDs to `seen_ids`:
165+```rust
166+if let Some(id_set) = model.seen_ids.get_mut(&peer) {
167+ id_set.extend(list.iter().map(|m| m.id.clone()));
168+}
169+```
170+
171+---
172+
173+## 4. Protocol Deviations
174+
175+### ⚪ D6. `ingest_poll` doesn't send profile to stranger on first contact — protocol "SHOULD" not followed
176+
177+**Type:** Protocol deviation (UX)
178+**File:** `core/src/app.rs:2221-2230, 2400-2412`
179+
180+PROTOCOL.md §4: "Clients SHOULD send a `profile` message to a contact on first interaction and whenever the user updates their name, bio, or photo."
181+
182+When a stranger sends us a text, `ingest_poll` auto-creates a contact (line 2225-2229) and queues a `delivery.ack` (line 2400-2412). But it does **not** queue a `profile` broadcast back to the stranger. The stranger's client has our pubkey (they sent us a message) but no profile — they see our truncated @p but not our display name or avatar.
183+
184+`send_text` handles this correctly: on first contact (line 1858-1873), it queues a profile broadcast after the text. But `ingest_poll` doesn't.
185+
186+**Impact:** Minor UX issue — a stranger who initiates conversation doesn't see our profile until we manually send them a text or update our profile. Not a security vulnerability.
187+
188+**Suggested fix:** After auto-creating a contact in `ingest_poll`, queue a profile broadcast:
189+```rust
190+if !known {
191+ // ... auto-create contact ...
192+ let profile = Payload::Profile { /* ... */ };
193+ model.outbox.push_back(OutboxItem::profile(
194+ sender.clone(),
195+ Arc::new(protocol::serialize_payload(&profile, ts)),
196+ ));
197+ outbox_dirty = true;
198+}
199+```
200+
201+---
202+
203+## Summary of New Findings
204+
205+| # | Severity | Type | Title |
206+|---|----------|------|-------|
207+| D1 | 🟡 medium | Livelock | `events_stored` doesn't count decrypted-but-non-stored events — livelock on budget exhaustion |
208+| D2 | 🔵 low | Stale state | `SetServerUrl` doesn't reset `poll_retries` — new relay inherits old poll backoff |
209+| D3 | 🔵 low | Write guard gap | `SendResult` pops items when `kv_load_failed` — duplicate sends on relaunch |
210+| D4 | 🔵 low | Robustness | `now_ms()` returns 0 on clock failure — outbox TTL disabled |
211+| D5 | 🔵 low | Dedup gap | `LoadedMessages` merge doesn't update `seen_ids` — weakened dedup after load failure |
212+| D6 | ⚪ info | Protocol deviation | `ingest_poll` doesn't send profile to stranger on first contact |
213+
214+**Medium (1):** D1
215+**Low (4):** D2, D3, D4, D5
216+**Info (1):** D6
217+
218+---
219+
220+## Priorities
221+
222+1. **D1 (medium):** Fix `events_stored` to count all successfully decrypted events. This closes a livelock variant that the N9 fix doesn't cover — a hostile relay can permanently wedge the client by re-serving large duplicate/stale/stranger blobs.
223+
224+2. **D2 (low):** Add `model.poll_retries = 0;` to `SetServerUrl`. One-line fix, prevents stale backoff on relay switch.
225+
226+3. **D5 (low):** Update `seen_ids` in the `LoadedMessages` merge. Closes a dedup gap when `seen_ids` kv load fails.
227+
228+4. **D3 (low):** Guard `SendResult` pop with `kv_load_failed` check. Prevents duplicate sends on relaunch.
229+
230+5. **D4 (low):** Change `unwrap_or(0)` to `unwrap_or(1)` in `now_ms()`. Prevents TTL disablement on clock failure.
AUDIT-FFI-PHONEMIC-APPLE.mdnew file+470
@@ -0,0 +1,470 @@
1+# Skrepka Security Audit — FFI, Phonemic, Apple Shell (2026-07-16)
2+
3+**Scope:** Deep audit of `core/src/ffi.rs`, `core/src/phonemic.rs`, and all Apple shell files (`apple/SkrepkaApp/*.swift`). Cross-referenced against `PROTOCOL.md`, `AGENTS.md`, `AUDIT-NEW.md`, and `AUDIT-FRESH.md`. Findings below are **not** in prior audits.
4+
5+**Legend:** 🔴 critical · 🟠 high · 🟡 medium · 🔵 low · ⚪ info
6+
7+---
8+
9+## 1. FFI Boundary
10+
11+### 🟠 F1. `try!` in Core.swift crashes on empty bytes from `guard` — FFI panic safety is a lie
12+
13+**Type:** FFI boundary / panic safety
14+**Files:** `core/src/ffi.rs:42-44` (`guard`), `apple/SkrepkaApp/Core.swift:30,38,49,60,66,74,81`
15+
16+The `guard` function in `ffi.rs` catches panics with `catch_unwind` and returns an empty `Vec<u8>`. The module doc (lines 4-9) claims: *"the shell already tolerates an empty effect list (it just does nothing) and an empty view (it renders the previous one), so a bug degrades into a stalled UI rather than a corrupted process."*
17+
18+This is false. Every bincode deserialization in `Core.swift` uses `try!`:
19+
20+```swift
21+// Core.swift:30 (init)
22+self.view = try! .bincodeDeserialize(input: [UInt8](core.view()))
23+
24+// Core.swift:38 (update)
25+let effects = [UInt8](core.update(data: Data(try! event.bincodeSerialize())))
26+
27+// Core.swift:49 (dispatch)
28+let requests = try! Requests.bincodeDeserialize(input: effects).value
29+
30+// Core.swift:60 (render)
31+self.view = try! .bincodeDeserialize(input: [UInt8](core.view()))
32+```
33+
34+If `core.view()` or `core.update()` returns empty bytes (from a caught panic), `try! .bincodeDeserialize(input: [])` throws, and `try!` produces a fatal error — **crashing the app**, not degrading gracefully. The `init` case is the worst: there is no "previous view" to render, so the very first `core.view()` call would crash the app on launch if the core panics.
35+
36+**Attack scenario:** Any input that causes a panic inside `App::update` or `Skrepka::view` — an unforeseen edge case, a dependency bug, or an integer overflow in debug mode — would crash the app instantly via `try!` rather than degrading to a stalled UI as the FFI docs claim. On iOS, this is a clean crash with no data corruption, but it's a denial-of-service: the user can't use the app at all.
37+
38+**Exploitable in practice:** Requires triggering a panic in the Rust core. The core code is careful with `unwrap_or` / `unwrap_or_default`, but panics from dependencies (e.g., `serde_json` on malformed input, `zstd` on a crafted frame) or array indexing bugs are possible. A hostile relay crafting specific poll responses could potentially trigger a panic in the decrypt path.
39+
40+**Suggested fix:** Replace `try!` with `try?` or a `do/catch` block that logs the error and skips the deserialization. For `init`, provide a default empty `ViewModel` if `core.view()` returns empty bytes. Alternatively, have `guard` return a sentinel (e.g., a single zero byte) that the Swift side can detect as "panic occurred" and handle gracefully.
41+
42+---
43+
44+### 🟡 F2. `AssertUnwindSafe` is unsound — Model is read after a panic
45+
46+**Type:** FFI boundary / memory safety
47+**Files:** `core/src/ffi.rs:39-44` (`guard` + `AssertUnwindSafe`)
48+
49+The `guard` function uses `AssertUnwindSafe(f)` to bypass the `UnwindSafe` requirement. The doc comment (lines 39-41) justifies this: *"AssertUnwindSafe is sound here because a poisoned Bridge is never read again for correctness: the worst case is a dropped effect batch, and the next event starts a fresh update."*
50+
51+This is incorrect. The `Bridge` holds the `Core`, which holds the `Model`. `App::update` takes `&mut Model` and mutates it in place. If a panic occurs **mid-update** (after some model mutations but before the function returns), the `Model` is left in a partially-mutated, inconsistent state. The `catch_unwind` catches the panic, returns empty bytes, but the `Model` stays corrupted. The **next** `update` call operates on this corrupted model.
52+
53+The comment's claim that "the next event starts a fresh update" is misleading — a fresh update on a corrupted model is not fresh. The model's invariants (e.g., `contacts` is consistent with `messages`, `cursor` is valid, `outbox` items are well-formed) may be violated.
54+
55+**Attack scenario:** A panic mid-update corrupts the model. The next `update` call sees the corrupted state and may:
56+- Write corrupted state to kv (persisting the corruption across launches)
57+- Crash on a subsequent update (if the corruption violates an invariant checked by `update`)
58+- Produce incorrect behavior (e.g., sending messages to the wrong recipient)
59+
60+**Exploitable in practice:** Requires triggering a panic mid-update, which is the same bar as F1. The corruption is silent — the user sees a stalled UI (if F1 doesn't crash first), but the next interaction operates on corrupted state.
61+
62+**Suggested fix:** After a caught panic, reset the `Model` to a known-good state (e.g., re-load from kv) or mark the `Bridge` as poisoned and refuse further operations. Alternatively, snapshot the `Model` before `update` and restore it on panic. This is expensive but correct. At minimum, document that a panic may corrupt the model and recommend the shell re-initialize the core after a caught panic.
63+
64+---
65+
66+### 🔵 F3. `resolve` accepts arbitrary `EffectId` — no validation against pending effects
67+
68+**Type:** FFI boundary / input validation
69+**Files:** `core/src/ffi.rs:70-78` (`resolve`)
70+
71+The `resolve` method accepts any `u32` as an effect ID and any `&[u8]` as the resolution data. The `Bridge::resolve` call would fail with `Err` if the effect ID is unknown, which `guard` converts to an empty Vec. But the empty Vec would crash the Swift side via `try!` (see F1).
72+
73+More importantly, if the Swift side has a bug that resolves the same effect ID twice (e.g., from a race between a timer callback and a `.clear` call), the second resolution would produce effects for a non-existent or already-resolved effect. The `Bridge::resolve` would return `Err`, which becomes empty bytes, which crashes via `try!`.
74+
75+**Attack scenario:** Not directly exploitable by an attacker — the effect IDs are generated by the core and passed to the shell. But a shell bug (e.g., a race condition in timer handling) could trigger a double-resolve, crashing the app.
76+
77+**Suggested fix:** The shell should track which effect IDs are pending and guard against double-resolve. The FFI should return a distinguishable error for "unknown effect ID" vs "serialization failure" so the shell can handle it gracefully.
78+
79+---
80+
81+## 2. Phonemic
82+
83+### 🔵 P1. `to_ob` / `from_ob` round-trip asymmetry for empty input
84+
85+**Type:** Correctness asymmetry
86+**Files:** `core/src/phonemic.rs:98-109` (`to_ob`), `core/src/phonemic.rs:113-132` (`from_ob`)
87+
88+`to_ob(&[])` returns `Some(String::new())` (empty string), but `from_ob("")` returns `None` (because `split('-').filter(|p| !p.is_empty()).collect()` yields an empty Vec, which triggers `parts.is_empty() => None`).
89+
90+This means `to_ob` produces a string that `from_ob` can't decode. The round-trip property is broken for empty input.
91+
92+**Impact:** No caller passes empty bytes to `to_ob` for pubkey purposes (keys are always 32 bytes). The asymmetry is documented in the test `odd_length_input_has_no_spelling` (line 210). Harmless in practice.
93+
94+**Suggested fix:** Either make `to_ob(&[])` return `None` (consistent with odd-length rejection) or make `from_ob("")` return `Some(vec![])` (consistent with the encoding). The former is safer — an empty encoding is meaningless.
95+
96+---
97+
98+### 🔵 P2. `try_parse_pubkey` hex path lowercases redundantly — no bug, but misleading
99+
100+**Type:** Code clarity
101+**Files:** `core/src/phonemic.rs:154`
102+
103+`hex::decode(trimmed.to_lowercase())` — the `hex` crate's `decode` accepts both uppercase and lowercase hex digits. The `to_lowercase()` is redundant for the hex path. It doesn't cause a bug (the output of `valid_pubkey_hex` is always lowercase via `hex::encode`), but it suggests the case matters when it doesn't.
104+
105+**Suggested fix:** Remove the `to_lowercase()` or add a comment explaining it's for consistency, not correctness.
106+
107+---
108+
109+### ⚪ P3. No @p/hex collision for 32-byte pubkeys — confirmed safe
110+
111+**Type:** Correctness verification
112+**Files:** `core/src/phonemic.rs:148-158` (`try_parse_pubkey`)
113+
114+A 64-char hex string has no hyphens, so `from_ob` sees one part of 64 chars, fails the `part.len() != 6` check, returns `None`. The hex path then decodes it. No collision.
115+
116+A valid @p for a 32-byte key is 16 syllables (111 chars with hyphens). `hex::decode` fails on hyphens. No collision.
117+
118+A 6-char hex string (e.g., "abcdef") that happens to be a valid @p syllable: `from_ob` decodes it to 2 bytes, `valid_pubkey_hex` rejects (not 32 bytes). `hex::decode` gives 3 bytes, also rejected. No collision.
119+
120+**Verdict:** Safe. The @p-first ordering in `try_parse_pubkey` is correct.
121+
122+---
123+
124+### ⚪ P4. `from_ob` multibyte handling is correct — confirmed safe
125+
126+**Type:** Correctness verification
127+**Files:** `core/src/phonemic.rs:113-132`
128+
129+`to_lowercase()` is applied before `split('-')`. For non-ASCII input, `to_lowercase()` may change byte lengths, but the `part.len() != 6 || !part.is_ascii()` check on each part catches any non-ASCII characters that survive lowercasing. The test `multibyte_input_is_rejected_not_panicked_on` (line 279) confirms this.
130+
131+The `part[0..3]` and `part[3..6]` slices are safe because `part.len() == 6` and `part.is_ascii()` (ASCII = 1 byte per char, so byte indices == char indices).
132+
133+**Verdict:** Safe. No panic on multibyte input.
134+
135+---
136+
137+## 3. Apple Shell — HTTP Handling
138+
139+### 🟡 A1. `Http.perform` doesn't validate URL scheme — `file://` requests would be honored
140+
141+**Type:** Defense-in-depth gap
142+**Files:** `apple/SkrepkaApp/Effects.swift:104-106`
143+
144+```swift
145+guard let url = URL(string: req.url) else {
146+ return .err(.url(req.url))
147+}
148+var request = URLRequest(url: url)
149+```
150+
151+The shell accepts any URL scheme. `URLSession.data(for:)` handles `file://` URLs by reading local files. The core's `normalize_server_url` only accepts `http`/`https`, but if a bug in the core (or a future change) produces a `file://` or `data:` URL, the shell would honor it without question.
152+
153+**Attack scenario:** Not directly exploitable — the server URL is user-configured and validated by `normalize_server_url`. But if a bug in URL construction (e.g., `format!("{}/poll", model.settings.server_url)` where `server_url` is somehow `file:///etc/passwd`) reaches the shell, a local file could be read and its contents returned to the core as an HTTP response body. The core would try to parse it as JSON, fail, and treat it as an empty page.
154+
155+**Exploitable in practice:** Requires a core bug that produces a non-http URL. `normalize_server_url` prevents this for the server URL, but there's no belt-and-suspenders check in the shell.
156+
157+**Suggested fix:** Add a scheme check in `Http.perform`:
158+```swift
159+guard url.scheme == "http" || url.scheme == "https" else {
160+ return .err(.url(req.url))
161+}
162+```
163+
164+---
165+
166+### 🟡 A2. `HttpSessionDelegate` cancels same-host redirects — may break legitimate HTTPS upgrades
167+
168+**Type:** Protocol conformance / usability
169+**Files:** `apple/SkrepkaApp/Effects.swift:45-53`
170+
171+The redirect delegate cancels **all** redirects, including same-host redirects. A relay that redirects from `http://relay:80` to `https://relay:443` (a legitimate TLS upgrade) would have its redirect cancelled. The client would see the 3xx response and treat it as a failure.
172+
173+The protocol says "plain HTTP, served over TLS in production" (§5), and `normalize_server_url` accepts both `http` and `https`. So a relay that serves HTTP on port 80 and redirects to HTTPS on port 443 would be broken by this client.
174+
175+**Attack scenario:** Not an attack — a usability issue. A relay operator who sets up an HTTP-to-HTTPS redirect would find that Skrepka clients can't connect.
176+
177+**Exploitable in practice:** Depends on relay configuration. The `install.sh` deploys Caddy with TLS, so production relays serve HTTPS directly (no redirect). But a relay misconfigured to redirect would be unreachable.
178+
179+**Suggested fix:** Allow same-host redirects (compare the redirect target's host against the original request's host). Only cancel cross-host redirects, which are the token-exfiltration vector. Or, since the protocol says no redirects, document that relays must not redirect.
180+
181+---
182+
183+### 🔵 A3. `UInt16(clamping:)` silently truncates status codes > 65535
184+
185+**Type:** Input validation
186+**Files:** `apple/SkrepkaApp/Effects.swift:120`
187+
188+```swift
189+status: UInt16(clamping: http?.statusCode ?? 0),
190+```
191+
192+HTTP status codes are 3-digit integers (100-599), so this is fine in practice. But `UInt16(clamping:)` would clamp any value > 65535 to 65535, which is a valid `UInt16` but not a valid HTTP status. The core checks `status >= 200 && status < 300` for success, so 65535 would be treated as failure. No security issue.
193+
194+**Verdict:** Safe. HTTP status codes are bounded by the protocol.
195+
196+---
197+
198+### ⚪ A4. URLSession configuration is correct — confirmed safe
199+
200+**Type:** Implementation review
201+**Files:** `apple/SkrepkaApp/Effects.swift:91-101`
202+
203+The session configuration is:
204+- `ephemeral` — no cookies, no cache, no persistent storage ✓
205+- `httpCookieAcceptPolicy = .never` ✓
206+- `httpShouldSetCookies = false` ✓
207+- `httpCookieStorage = nil` ✓
208+- `urlCache = nil` ✓
209+- `requestCachePolicy = .reloadIgnoringLocalAndRemoteCacheData` ✓
210+- `timeoutIntervalForRequest = 70` — matches the server's ~25s long-poll ✓
211+- `tlsMinimumSupportedProtocolVersion = .TLSv12` ✓
212+
213+No sensitive data in logs. The `error.localizedDescription` in the catch block returns user-friendly strings like "The network connection was lost" — no relay-specific info beyond what the user already configured.
214+
215+**Verdict:** Safe. Good defense-in-depth.
216+
217+---
218+
219+### ⚪ A5. Response size limiting is correct — confirmed safe
220+
221+**Type:** Implementation review
222+**Files:** `apple/SkrepkaApp/Effects.swift:31-79`
223+
224+The `HttpSessionDelegate` tracks per-task byte counts in a thread-safe `NSLock`-guarded dictionary. When a task's accumulated body exceeds `maxResponseBytes` (64 MiB), the task is cancelled. The `didCompleteWithError` callback cleans up the dictionary entry. Every task eventually completes (success, failure, or cancel), so no dictionary leak.
225+
226+The 64 MiB cap matches the core's `MAX_POLL_RESPONSE_BYTES` (also 64 MiB). The shell's cap fires before the core's (the shell cancels the task mid-stream, the core never sees the full body), which is the correct ordering — the shell's cap prevents OOM before the core's check runs.
227+
228+**Verdict:** Safe. Well-designed.
229+
230+---
231+
232+## 4. Apple Shell — Keychain & KV Persistence
233+
234+### ⚪ A6. Keychain storage is correct — confirmed safe
235+
236+**Type:** Implementation review
237+**Files:** `apple/SkrepkaApp/Effects.swift:320-415`
238+
239+- `kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly` — key never rides backup ✓
240+- `SecItemUpdate` first, then `SecItemAdd` if not found — no delete-then-add window ✓
241+- `errSecItemNotFound` is the only status that triggers key generation ✓
242+- 64-byte key length is validated on load ✓
243+- `loadOrCreateIdentity` is called only on the main actor (singleton `Core.shared`), so no race ✓
244+
245+The `store` function's update-then-add sequence has a theoretical race (between `SecItemUpdate` returning `errSecItemNotFound` and `SecItemAdd`, another thread could add the item), but `bootIdentity` is only called on the `@MainActor` singleton, so there's no concurrency.
246+
247+**Verdict:** Safe. Good practice.
248+
249+---
250+
251+### ⚪ A7. KV persistence is correct — confirmed safe
252+
253+**Type:** Implementation review
254+**Files:** `apple/SkrepkaApp/Effects.swift:195-316`
255+
256+- Serial queue — all operations serialized ✓
257+- Atomic writes with `.completeFileProtectionUnlessOpen` ✓
258+- `isExcludedFromBackup = true` — plaintext history not in iCloud backup ✓
259+- Percent-encoding with `.alphanumerics` — injective key→filename mapping, no path traversal ✓
260+- Legacy migration runs before any read (same serial queue) ✓
261+- Missing file = empty key (`.none`), not an error — correct distinction from read failure ✓
262+
263+**Verdict:** Safe. Well-designed.
264+
265+---
266+
267+## 5. Apple Shell — Photo Picker & QR Scanning
268+
269+### 🔵 A8. `PhotoPicker` last-resort quality doesn't check size cap
270+
271+**Type:** Logic bug / UX
272+**Files:** `apple/SkrepkaApp/PhotoPicker.swift:80-81`
273+
274+```swift
275+// Last resort: the smallest quality that still produces something.
276+return image.jpegData(compressionQuality: 0.1)?.base64EncodedString()
277+```
278+
279+The loop (lines 71-79) reduces quality until the base64 fits within 64 KiB (`maxBase64Len`). But the last-resort return on line 81 doesn't check if the result fits. If a 256px JPEG at q0.1 still exceeds 64 KiB (possible for high-frequency noise images), the core's `SaveProfile` rejects it with "photo too large" and the user has no recourse.
280+
281+**Attack scenario:** A user picks a photo that, even at 256px and q0.1, produces > 64 KiB of base64. The profile save fails with no way to proceed. Not a security issue — a UX dead end.
282+
283+**Exploitable in practice:** Very unlikely for real photos (256px JPEG at q0.1 is typically 5-15 KiB). But a synthetic image (e.g., pure noise) could exceed the cap.
284+
285+**Suggested fix:** If the last-resort still exceeds the cap, return `nil` (triggering `onCancel`) or downscale further (e.g., 128px). Or document that the user should pick a different photo.
286+
287+---
288+
289+### 🔵 A9. `scannedKeyPayload` is business logic in the shell — portability concern
290+
291+**Type:** Protocol conformance / architecture
292+**Files:** `apple/SkrepkaApp/QRView.swift:24-35`
293+
294+`scannedKeyPayload` parses QR code content: strips URL schemes (`skrepka://`, `https://`, `http://`), extracts the last path component, and trims whitespace. This is parsing logic that determines what input the core receives.
295+
296+`AGENTS.md` says: *"The shell never decides anything — it turns Effects into platform calls and resolves the results back in."* This function decides how to interpret a QR code, which is arguably a business decision.
297+
298+An Android client would need to reimplement this logic. If the parsing differs (e.g., one client strips `skrepka://` and another doesn't), the same QR code would produce different inputs to the core.
299+
300+**Attack scenario:** Not a security vulnerability — the core's `try_parse_pubkey` validates the result regardless. But a portability bug: a QR code with a `skrepka://` prefix would work on iOS (stripped by `scannedKeyPayload`) but fail on an Android client that doesn't strip the scheme.
301+
302+**Suggested fix:** Move `scannedKeyPayload` into the core (e.g., `try_parse_pubkey_from_qr` or add scheme-stripping to `try_parse_pubkey`). The shell should pass the raw QR content to the core.
303+
304+---
305+
306+### 🔵 A10. `QRScannerView` doesn't check camera permission
307+
308+**Type:** UX gap
309+**Files:** `apple/SkrepkaApp/QRView.swift:75-80`
310+
311+`ScannerVC.viewDidLoad` calls `AVCaptureDevice.default(for: .video)`, which returns `nil` if camera permission hasn't been granted (or has been denied). The `guard` fails silently, and the scanner shows a black screen with no error message or permission prompt.
312+
313+**Attack scenario:** Not a security issue. A user who denied camera permission can't scan QR codes and sees a black screen with no explanation.
314+
315+**Suggested fix:** Check `AVCaptureDevice.authorizationStatus(for: .video)` and request permission if not determined. Show an error message if denied.
316+
317+---
318+
319+### ⚪ A11. `QRScannerView` camera lifecycle is correct — confirmed safe
320+
321+**Type:** Implementation review
322+**Files:** `apple/SkrepkaApp/QRView.swift:101-114`
323+
324+`startRunning()` and `stopRunning()` are dispatched to a background queue (`DispatchQueue.global(qos: .userInitiated)`) to avoid blocking the main thread. The `done` flag in `Coordinator` prevents multiple `onScan` callbacks. The camera session is properly stopped in `viewWillDisappear`.
325+
326+**Verdict:** Safe.
327+
328+---
329+
330+## 6. Apple Shell — Logic Leakage & Protocol Conformance
331+
332+### 🟡 A12. `BackgroundRefresh` polls `core.view` in a tight loop — main actor contention
333+
334+**Type:** Performance / architecture
335+**Files:** `apple/SkrepkaApp/SkrepkaApp.swift:156-163`
336+
337+The `settle` function polls `core.view` every 200ms, reading the `@Published` `ViewModel` on the main actor. While the overhead per poll is minimal (reading a published property), this runs for up to 25 seconds during a background refresh. If the core is processing a large poll response (which also runs on the main actor via `resolve`), the 200ms polls interleave with core processing.
338+
339+More importantly, `core.view` is a `@Published` property backed by `ViewModel`, which is a value type. Each read copies the entire `ViewModel` (including `contacts: Vec<ContactVM>` and `messages: Vec<MessageVM>`). For a user with 500 contacts and 1000 messages, each poll copies ~1 MB of data. Over 25 seconds at 200ms intervals, that's 125 copies = ~125 MB of transient allocations.
340+
341+**Attack scenario:** Not an attack — a performance issue. A user with many contacts and active conversations would experience increased memory pressure during background refresh.
342+
343+**Suggested fix:** Use a Combine subscription (`core.$view.sink`) instead of polling, or have the core expose a lightweight "status changed" flag that the shell can check without copying the full `ViewModel`.
344+
345+---
346+
347+### 🔵 A13. `Core.swift` `dispatch` silently drops effects if `try!` crashes — no recovery
348+
349+**Type:** Error handling
350+**Files:** `apple/SkrepkaApp/Core.swift:47-53`
351+
352+```swift
353+private func dispatch(_ effects: [UInt8]) {
354+ // swiftlint:disable:next force_try
355+ let requests = try! Requests.bincodeDeserialize(input: effects).value
356+ for request in requests {
357+ process(request)
358+ }
359+}
360+```
361+
362+If `effects` is valid bincode but contains an effect variant the Swift side doesn't know about (e.g., after a core update that adds a new effect without regenerating Swift types), `try!` would crash. The AGENTS.md warns about this: *"Touching Event, ViewModel, or Effect without running just generate leaves the Swift side compiling against stale types."*
363+
364+But there's no runtime recovery. The crash is immediate and unrecoverable. A safer approach would be to catch the deserialization error, log it, and skip the unknown effect — the core would see the effect as unresolved and its watchdog would handle it.
365+
366+**Suggested fix:** Replace `try!` with `try?` and log the error. Unknown effects are dropped; the core's watchdog handles the missing resolution.
367+
368+---
369+
370+### ⚪ A14. `Time.handle` timer lifecycle is correct — confirmed safe
371+
372+**Type:** Implementation review
373+**Files:** `apple/SkrepkaApp/Effects.swift:147-191`
374+
375+The `timers` dictionary is on the `@MainActor`. The `schedule` function removes the old work item before inserting a new one. The `DispatchWorkItem`'s callback runs on the main queue (via `MainActor.assumeIsolated`), so there's no interleaving between `schedule` and the callback. The `.clear` case removes and cancels the work item.
376+
377+No race condition: all operations are on the main actor / main queue, which is single-threaded.
378+
379+**Verdict:** Safe.
380+
381+---
382+
383+### ⚪ A15. `SkrepkaApp.swift` background refresh is correct — confirmed safe
384+
385+**Type:** Implementation review
386+**Files:** `apple/SkrepkaApp/SkrepkaApp.swift:64-164`
387+
388+- `isProtectedDataAvailable` guard prevents running while locked ✓
389+- `settle` polling respects `Task.isCancelled` and deadline ✓
390+- `setTaskCompleted(success: !Task.isCancelled)` correctly reports failure on cancellation ✓
391+- `schedule()` is called before `run()` — next refresh is always queued ✓
392+- `Core.shared` is only accessed after the `isProtectedDataAvailable` guard ✓
393+
394+**Verdict:** Safe. Well-designed.
395+
396+---
397+
398+## 7. Protocol & AGENTS.md Conformance
399+
400+### 🔵 A16. AGENTS.md says "five kv loads" but core does six — `seen_ids` added
401+
402+**Type:** Documentation drift
403+**Files:** `AGENTS.md:98` ("fans out five kv loads"), `core/src/app.rs:719-726` (six loads)
404+
405+AGENTS.md line 98 says: *"IdentityLoaded fans out five kv loads → LoadedSettings triggers Connect"*. But the core actually fans out **six** kv loads: `settings`, `profile`, `contacts`, `cursor`, `outbox`, and `seen_ids` (line 725: `KeyValue::get(K_SEEN_IDS)`). The `STARTUP_LOADS` constant is 6 (line 312).
406+
407+**Impact:** Documentation drift, not a bug. A developer reading AGENTS.md would expect five loads and be confused by the sixth.
408+
409+**Suggested fix:** Update AGENTS.md to say "six kv loads" and include `seen_ids` in the list.
410+
411+---
412+
413+### 🔵 A17. AGENTS.md lists kv keys without `seen_ids` — stale documentation
414+
415+**Type:** Documentation drift
416+**Files:** `AGENTS.md:14` ("keys `settings`, `profile`, `contacts`, `cursor`, `outbox`, and `messages:<peer_hex>`")
417+
418+The `seen_ids` key is not listed in AGENTS.md's kv key list. It was added as part of the dedup fix (AUDIT-NEW.md Q18) but the documentation wasn't updated.
419+
420+**Suggested fix:** Add `seen_ids` to the kv key list in AGENTS.md.
421+
422+---
423+
424+## Summary of New Findings
425+
426+| # | Severity | Type | Title |
427+|---|----------|------|-------|
428+| F1 | 🟠 high | FFI/panic | `try!` in Core.swift crashes on empty bytes from `guard` — FFI panic safety claim is false |
429+| F2 | 🟡 medium | FFI/memory | `AssertUnwindSafe` is unsound — Model is read after a panic, corruption persists |
430+| F3 | 🔵 low | FFI/input | `resolve` accepts arbitrary EffectId — double-resolve crashes via `try!` |
431+| P1 | 🔵 low | Correctness | `to_ob`/`from_ob` round-trip asymmetry for empty input |
432+| P2 | 🔵 low | Clarity | `try_parse_pubkey` hex path lowercases redundantly |
433+| P3 | ⚪ info | Safe | No @p/hex collision for 32-byte pubkeys — confirmed |
434+| P4 | ⚪ info | Safe | `from_ob` multibyte handling is correct — confirmed |
435+| A1 | 🟡 medium | HTTP/defense | `Http.perform` doesn't validate URL scheme — `file://` would be honored |
436+| A2 | 🟡 medium | HTTP/protocol | Redirect delegate cancels same-host redirects — breaks HTTPS upgrades |
437+| A3 | 🔵 low | HTTP/input | `UInt16(clamping:)` silently truncates status codes > 65535 |
438+| A4 | ⚪ info | Safe | URLSession configuration is correct |
439+| A5 | ⚪ info | Safe | Response size limiting is correct |
440+| A6 | ⚪ info | Safe | Keychain storage is correct |
441+| A7 | ⚪ info | Safe | KV persistence is correct |
442+| A8 | 🔵 low | Photo/UX | `PhotoPicker` last-resort quality doesn't check size cap |
443+| A9 | 🔵 low | Architecture | `scannedKeyPayload` is business logic in the shell — portability concern |
444+| A10 | 🔵 low | QR/UX | `QRScannerView` doesn't check camera permission |
445+| A11 | ⚪ info | Safe | QR scanner camera lifecycle is correct |
446+| A12 | 🟡 medium | Performance | `BackgroundRefresh` polls `core.view` — copies full ViewModel every 200ms |
447+| A13 | 🔵 low | Error handling | `Core.swift` `dispatch` crashes on unknown effect — no recovery |
448+| A14 | ⚪ info | Safe | Timer lifecycle is correct |
449+| A15 | ⚪ info | Safe | Background refresh is correct |
450+| A16 | 🔵 low | Docs | AGENTS.md says "five kv loads" but core does six |
451+| A17 | 🔵 low | Docs | AGENTS.md kv key list missing `seen_ids` |
452+
453+**High (1):** F1
454+**Medium (4):** F2, A1, A2, A12
455+**Low (8):** F3, P1, P2, A3, A8, A9, A10, A13, A16, A17
456+**Info (8):** P3, P4, A4, A5, A6, A7, A11, A14, A15
457+
458+---
459+
460+## Priorities
461+
462+1. **F1 (high):** Replace `try!` in Core.swift with graceful error handling. The FFI's panic safety design is undermined by `try!` — a caught panic crashes the app instead of degrading. This is the most impactful finding because it turns every potential core panic into an immediate app crash.
463+
464+2. **F2 (medium):** Address `AssertUnwindSafe` soundness. After a caught panic, the Model may be corrupted. At minimum, document the risk and consider resetting the Model from kv on panic recovery.
465+
466+3. **A1 (medium):** Add URL scheme validation in `Http.perform`. Defense-in-depth against a core bug producing non-http URLs.
467+
468+4. **A2 (medium):** Allow same-host redirects or document that relays must not redirect. The current all-redirects-cancelled policy breaks legitimate HTTPS upgrades.
469+
470+5. **A12 (medium):** Replace `settle`'s polling with a Combine subscription to avoid copying the full ViewModel every 200ms during background refresh.
AUDIT-FRESH.mdnew file+385
@@ -0,0 +1,385 @@
1+# Skrepka Security Audit — Fresh Pass (2026-07-15)
2+
3+**Scope:** Exhaustive multi-pass audit of PROTOCOL.md, server.knot, core/src/ (app.rs,
4+crypto.rs, protocol.rs, model.rs, phonemic.rs, ffi.rs), apple/SkrepkaApp/ (Effects.swift,
5+Core.swift, Views.swift, Forms.swift), install.sh. Findings below are **not** in
6+PROTOCOL-REVIEW.md or AUDIT-NEW.md, or are new angles on previously-noted areas.
7+
8+**Legend:** 🔴 critical · 🟠 high · 🟡 medium · 🔵 low · ⚪ info
9+
10+---
11+
12+## 1. Cryptographic Protocol
13+
14+### 🔴 N1. No AAD on AEAD — envelope `to` field is unauthenticated, enabling silent targeted censorship by any relay
15+
16+**Type:** Design gap (protocol + crypto.rs)
17+**Files:** `core/src/crypto.rs:384-387` (encrypt), `core/src/crypto.rs:434-438` (decrypt)
18+
19+AUDIT-NEW.md Q2 notes this but downgrades the impact to "equivalent to message loss, which is
20+an accepted limitation." That understates it. The real issue is **silent, targeted message loss
21+with zero detectability**:
22+
23+A relay holding a victim's messages can swap the `to` field on a *specific* message (from a
24+sender the relay wants to censor), while leaving other messages intact. The recipient never
25+sees the message and gets no error. The `delivery.ack` system doesn't help because the recipient
26+never received the message to ack it, and the sender's UI shows the message as "sent"
27+indefinitely — which is the same behavior as "the recipient is offline" or "the recipient read
28+it but hasn't acked yet." There is **no way for either party to distinguish "the relay ate
29+Alice's message" from "Alice didn't send anything" or "Bob is just slow to ack."**
30+
31+This is worse than the generic "relay can drop messages" case. Dropping is *eventually*
32+detectable — the sender sees their message stuck at "sent" and can investigate. But `to`-swapping
33+moves the message to a *different recipient's* mailbox, where it's undecryptable and gets
34+silently dropped on poll. The original recipient's cursor is unaffected (no events), so the
35+next poll is normal. The censorship is invisible.
36+
37+**Attack scenario:**
38+1. Alice sends a message to Bob via relay R.
39+2. R swaps `to` from Bob's pubkey to Charlie's.
40+3. Message stored under Charlie's mailbox. Charlie can't decrypt (wrong key), drops silently.
41+4. Bob polls, gets nothing. Normal poll, no error.
42+5. Alice's UI shows "sent" — same as if Bob were merely offline.
43+6. No delivery.ack ever comes. Alice can't tell if Bob received it or not.
44+
45+The relay can do this selectively — censor messages from specific senders, or suppress specific
46+content patterns (inferred from blob size), while delivering everything else normally. The
47+censorship is undetectable because the sender sees the same "sent" status they'd see for any
48+offline recipient, and the recipient sees nothing unusual.
49+
50+**Suggested fix:** Include `version_byte || ephemeral_public || nonce || recipient_ed25519_public`
51+as AAD in the AEAD. The `to` field must match `recipient_ed25519_public` in the AAD. A relay
52+swapping `to` causes the wrong recipient to fail AEAD decryption (before signature check), and
53+the blob is dropped before cursor advancement. The *original* recipient's message stays in the
54+mailbox. Wire-format change (v0x02).
55+
56+### ⚪ N2. HKDF info string and wire version byte are independent constants
57+
58+**Type:** Code hygiene (crypto.rs)
59+**Files:** `core/src/crypto.rs:28` (`HKDF_INFO = b"skrepka-v1"`), `crypto.rs:33` (`WIRE_VERSION = 1`)
60+
61+The spec says "A future revision that changes the crypto primitives should bump both the version
62+byte and the HKDF `info` string together." But there's no code-level binding between them. A
63+developer bumping `WIRE_VERSION` to `2` could forget to update `HKDF_INFO`, causing two different
64+crypto versions to derive keys with the same KDF label.
65+
66+**Suggested fix:** Derive the info string from the version byte or add a compile-time assertion
67+linking them.
68+
69+---
70+
71+## 2. Server Implementation
72+
73+### 🟡 N3. `appendMessage` dedup scan is O(n) — identical-blob replay amplifies to O(n × batch_size)
74+
75+**Type:** Implementation concern / DoS amplification (server.knot)
76+**Files:** `server.knot:919-937`
77+
78+AUDIT-NEW.md Q7 notes the O(n) dedup scan. The amplification is worse than described for
79+identical-blob replay: a batch of 100 identical blobs to the same recipient does 100 × O(|messages|)
80+scans. With |messages| = 10,000, that's 1M comparisons per request. At 60 requests/min, that's
81+60M comparisons/min. Each comparison is a string equality on 64-char hex pubkeys + 346+ char
82+hex blobs.
83+
84+**Attack:** An attacker authenticates (free keypair) and sends batches of 100 identical
85+min-size blobs to one recipient. Each request is ~35 KB but triggers 1M comparisons. Bounded
86+by the 60/min rate limit, but the CPU amplification is ~1000x per request.
87+
88+**Suggested fix:** Index `*messages` by `(toKey, encryptedBlob)` or use a hash-based dedup set.
89+
90+### 🟡 N4. `capForwards` eviction is non-deterministic when retry counts are equal
91+
92+**Type:** Implementation bug (server.knot)
93+**Files:** `server.knot:515-522` (`capForwards`)
94+
95+AUDIT-NEW.md Q9 notes this. The sort by `retries` only (no secondary sort key) means when many
96+entries share `retries: 0`, the sort is unstable and any retries-0 entry can be dropped —
97+including a fresh forward for a healthy peer that would have succeeded on the first try.
98+
99+**Impact:** Delivery delay, not permanent loss (the message stays in `*messages` and can be
100+re-forwarded on the next presence announce). But it's a real availability issue under
101+federation abuse.
102+
103+**Suggested fix:** Sort by `(retries, encryptedBlob)` for determinism, or skip entries for
104+peers in backoff before capping.
105+
106+### 🟡 N5. `handleRecvGossip` `fromServer` not verified against connecting peer's address
107+
108+**Type:** Design gap (server.knot)
109+**Files:** `server.knot:1533-1578`
110+
111+AUDIT-NEW.md Q29 notes this. The `fromServer` field is self-asserted and used to route forwarded
112+messages. An attacker can claim any `fromServer` hostname. The server writes presence rows with
113+that hostname and forwards queued messages there. This is the root cause of the gossip-redirect
114+attack and is already documented, but the spec's §10 should state more prominently that **the
115+server has no mechanism to verify that the connecting peer is who it claims to be**.
116+
117+The `fromServer` field is a `ServerName` (format-validated), but format validation only checks
118+length, lowercase, and no trailing dot — it does not verify the peer controls that hostname.
119+
120+**Suggested fix:** Document more prominently. Real fix needs reverse-DNS verification or peer
121+authentication (signed gossip).
122+
123+### 🔵 N6. `genToken` generates one hex digit per `randomInt 16` call — entropy waste
124+
125+**Type:** Implementation concern (server.knot)
126+**Files:** `server.knot:532-537`
127+
128+AUDIT-NEW.md Q10 notes the CSPRNG dependency. Additionally, generating one hex digit at a time
129+is inefficient — each `randomInt 16` call should produce at least 4 bits, but if the runtime's
130+`randomInt` draws from a wider source (e.g., 32-bit `getrandom`), it wastes 28 bits per call.
131+48 calls × 28 wasted bits = 1344 bits wasted per token. Not a security issue (entropy is
132+abundant) but inefficient.
133+
134+**Verdict:** Info.
135+
136+---
137+
138+## 3. Client Core Logic
139+
140+### 🟡 N7. `seen_ids` dedup set is unbounded — grows without limit per peer
141+
142+**Type:** Implementation concern (app.rs)
143+**Files:** `core/src/app.rs:325` (`seen_ids: BTreeMap<String, HashSet<String>>`)
144+
145+The `seen_ids` map (Q18 fix) is persisted to kv and loaded at startup. It's a `BTreeMap<String,
146+HashSet<String>>` — one entry per peer, each a set of message IDs. The set is never trimmed.
147+Over time, a peer who sends thousands of messages accumulates thousands of IDs. The kv blob
148+(`seen_ids`) grows without bound.
149+
150+With `MAX_ID_LEN` = 128 chars and UUIDs = 36 chars, 1000 messages per peer (the conversation cap)
151+= 36 KB per peer. With 500 contacts (`MAX_CONTACTS`), that's 18 MB. The `seen_ids` kv blob is
152+rewritten in full on every conversation touch (line 2316), so a large set makes every message
153+receipt slower. On iOS, a 18 MB JSON blob written to Application Support on every incoming
154+message is a real performance issue.
155+
156+**Suggested fix:** Cap the `seen_ids` set per peer (e.g., keep the last 2000 IDs) and trim
157+periodically. Or use a time-based expiry. Or a Bloom filter with a fixed size.
158+
159+### 🟡 N8. `ingest_poll` advances cursor before processing events — crash between advance and persist loses messages
160+
161+**Type:** Implementation concern (app.rs)
162+**Files:** `core/src/app.rs:2024-2089`
163+
164+The cursor is advanced to `page.cursor` on line 2038 (before the event loop), and restored to
165+`prev_cursor` on budget exhaustion (line 2086) or event count overflow (line 2069). The cursor
166+is persisted to kv AFTER `ingest_poll` returns (line 1369), via a `KeyValue::set` effect. This
167+means the cursor write only happens after the event loop completes successfully.
168+
169+However, there's a crash window: if the app crashes between `model.cursor = clamped_cursor`
170+(line 2038) and the cursor persist effect (line 1369), the in-memory cursor is advanced but
171+the persisted cursor is still `prev_cursor`. On relaunch, the client sends `prev_cursor` to
172+the relay, which re-serves the events. No message loss — the persisted cursor is the safe one.
173+
174+**Verdict:** Safe. The cursor is only authoritative when persisted, and the persist happens
175+after `ingest_poll` completes. A crash during `ingest_poll` loses no data because the persisted
176+cursor hasn't changed. Info.
177+
178+### 🟡 N9. `ingest_poll` budget exhaustion drops remaining events — client is stuck if the relay always serves an oversized page
179+
180+**Type:** Implementation concern (app.rs)
181+**Files:** `core/src/app.rs:2054-2089`
182+
183+When the `MAX_POLL_TOTAL_BYTES` budget is exhausted mid-page, the loop breaks, the cursor is
184+restored to `prev_cursor`, and an error is set. The next poll sends `prev_cursor` again, and
185+the relay re-serves the same events. If the page always exceeds the budget (e.g., the relay
186+serves 50 large blobs and the budget only covers 10), the client is stuck: poll, process 10,
187+drop 40, re-poll, relay serves the same 50, process the same 10 (deduped, fast), drop 40, etc.
188+
189+The dedup makes re-processing fast (already-seen IDs are O(1) drops), but the client never
190+advances past the oversized page. The relay's events are served in `receivedAt` order, so the
191+same 50 events come back every time. The cursor never moves. The client is stuck in a loop.
192+
193+This is a **livelock**: the client polls, processes some events, but can never ack them. The
194+relay keeps serving the same page. The client's error message ("relay sent an oversized poll
195+page") is set but may not be visible in the UI.
196+
197+**Attack scenario:** A malicious relay serves a page of 50 blobs, each just under `MAX_BLOB_LEN`
198+(42 MiB). The total page is ~2 GiB, far exceeding the 64 MiB budget. The client processes a few,
199+drops the rest, and is stuck. Or more subtly: the relay serves 50 blobs that are each ~1.3 MiB
200+(total ~65 MiB, just over the 64 MiB budget). The client processes 49, drops 1, and is stuck
201+because the cursor never advances past the 50th event.
202+
203+**Suggested fix:** When the budget is exhausted, advance the cursor to the last *successfully
204+processed* event's `receivedAt` (not `page.cursor` and not `prev_cursor`). This acks the
205+processed events and lets the client move forward, dropping only the unprocessed tail. The
206+relay re-serves only the unprocessed events on the next poll. This changes the behavior from
207+"all-or-nothing cursor advance" to "partial ack."
208+
209+### 🟡 N10. Profile `ts` staleness check uses `>=` — equal-timestamp replay is a no-op, but the check is per-contact, not per-field
210+
211+**Type:** Implementation concern (app.rs)
212+**Files:** `core/src/app.rs:2174-2179` (approximate)
213+
214+AUDIT-NEW.md Q19 analyzes this and concludes it's safe because the attacker can't modify the
215+content without breaking the signature. I agree — the `>=` is correct and a same-`ts` replay
216+is a true no-op (same ciphertext, same signature, same content). Info.
217+
218+---
219+
220+## 4. Wire Format / Parsing
221+
222+### 🟡 N11. `protocol.rs` `parse_payload` does not validate `ts` is positive — negative `ts` clamped to 0 is harmless but surprising
223+
224+**Type:** Implementation concern (protocol.rs)
225+**Files:** `core/src/protocol.rs:100`
226+
227+AUDIT-NEW.md Q24 notes this. A `ts` of 0 or negative is clamped to `max(0, ...)` in `ingest_poll`.
228+A message with `ts = 0` is inserted at the earliest chronological position and trimmed first.
229+This is harmless. Info.
230+
231+### 🟡 N12. `delivery.ack` parsing accepts non-string entries in `ack_ids` — filtered silently, no length check on individual IDs after filtering
232+
233+**Type:** Implementation concern (protocol.rs)
234+**Files:** `core/src/protocol.rs:116-126`
235+
236+AUDIT-NEW.md Q26 notes this. The double-check (raw count + post-filter count) is correct.
237+Non-string entries are filtered. Individual ID length is checked (`ack_ids.iter().any(|id|
238+id.len() > MAX_ID_LEN)`). This is correct. Info.
239+
240+---
241+
242+## 5. Federation
243+
244+### 🟠 N13. Gossip amplification: 100 online events trigger 100 mailbox scans + forward staging — O(100 × |messages|) per request
245+
246+**Type:** Design gap (server.knot)
247+**Files:** `server.knot:1544-1578` (`handleRecvGossip`)
248+
249+AUDIT-NEW.md Q27 notes this. A single gossip request with 100 `online` events for 100 different
250+keys triggers `forwardQueuedToServer` for each key, which scans the entire mailbox. With
251+|messages| = 10,000, that's 100 × 10,000 = 1M comparisons per request. At 60/min per IP, that's
252+60M comparisons/min. An attacker with 10 IPs can do 600M comparisons/min.
253+
254+Additionally, each `forwardQueuedToServer` call stages forward entries, which consume
255+`maxForwardsPerServer` slots and trigger HTTP POSTs to the attacker's server. The attacker
256+receives copies of the victim's ciphertext.
257+
258+**Suggested fix:** Limit the number of newly-online keys per gossip batch that trigger forwards
259+(e.g., cap at 10). Or batch the mailbox scan across all newly-online keys in one pass.
260+
261+### 🟡 N14. `offline` gossip events don't cancel pending forwards — wasted retries for up to 80 minutes
262+
263+**Type:** Design gap (server.knot)
264+**Files:** `server.knot:1535-1541`
265+
266+AUDIT-NEW.md Q28 notes this. When an `offline` event is received, pending forwards to that server
267+are not cancelled. They retry for up to `retryBackoffMax × maxForwardRetries` = 8 min × 10 = 80
268+minutes, wasting `maxForwardsPerServer` slots and generating failed HTTP requests.
269+
270+If the offline event was spoofed, the forwards continue — and if the key is actually still
271+online at that server, the forward succeeds on retry. The impact is minimal.
272+
273+**Suggested fix:** When processing an `offline` event, optionally drop pending forwards to that
274+server for the offline key. But this could cause message loss if the offline event is spoofed.
275+Better to leave as-is and document.
276+
277+---
278+
279+## 6. Deployment / install.sh
280+
281+### 🟡 N15. `install.sh` downloads binary over HTTPS but checksum is best-effort — missing checksum silently proceeds
282+
283+**Type:** Deployment concern (install.sh)
284+**Files:** `install.sh:150-181`
285+
286+The checksum verification is best-effort: if the `.sha256` file doesn't exist (line 162 fails),
287+the script warns and proceeds. If `sha256sum`/`shasum` is not available, it warns and proceeds.
288+A checksum that exists but doesn't match is fatal (line 169-174) — correct.
289+
290+The concern: a compromised release asset without a published `.sha256` file (e.g., a pre-checksum
291+release, or a supply-chain attack that removes the checksum file) would be installed without
292+verification. The script trusts GitHub's HTTPS, but HTTPS authenticates the CDN, not the
293+artifact. A compromised GitHub release would sail through.
294+
295+**Suggested fix:** Make the checksum mandatory for all new installs. Keep the best-effort
296+behavior only for upgrades from pre-checksum releases, with a prominent warning.
297+
298+### ⚪ N16. `install.sh` DOMAIN validation rejects uppercase but the Caddyfile interpolation is safe
299+
300+**Type:** Deployment review (install.sh)
301+**Files:** `install.sh:34-45`
302+
303+DOMAIN is lowercased and stripped of scheme/path/port before interpolation into the Caddyfile
304+and systemd unit. The validation rejects anything outside `[a-z0-9.-]`. This prevents config
305+injection (a stray quote or semicolon in the Caddyfile). Good.
306+
307+**Verdict:** Safe. Info.
308+
309+---
310+
311+## 7. Apple Shell
312+
313+### ⚪ N17. URLSession redirect cancellation is correct — bearer token exfiltration via 302 is prevented
314+
315+**Type:** Implementation review (Effects.swift)
316+**Files:** `apple/SkrepkaApp/Effects.swift:8-30`
317+
318+The `NoRedirectDelegate` cancels all HTTP redirects. This prevents a hostile relay from
319+answering `/poll` or `/messages` with a 302 to an attacker-controlled host, which would replay
320+the `Authorization: Bearer` header to the redirect target. The delegate returns `nil`, which
321+hands the 3xx response to the caller as a non-2xx status. The core treats it as a failed
322+request. Correct.
323+
324+**Verdict:** Safe. Good defense.
325+
326+### ⚪ N18. Keychain uses `kSecAttrAccessibleAfterFirstUnlockThisDeviceOnly` — key never rides backup
327+
328+**Type:** Implementation review (Effects.swift)
329+**Files:** `apple/SkrepkaApp/Effects.swift:352`
330+
331+The identity key is stored with `ThisDeviceOnly` accessibility, meaning it never enters iCloud
332+or iTunes backups. The key is accessible after first unlock (not only when unlocked), so
333+background polling works. This is the correct accessibility class for a messaging identity key.
334+
335+**Verdict:** Safe. Good practice.
336+
337+---
338+
339+## Summary of New Findings
340+
341+| # | Severity | Type | Title |
342+|---|----------|------|-------|
343+| N1 | 🔴 critical | Design gap | No AAD — `to` field unauthenticated, silent targeted censorship |
344+| N2 | ⚪ info | Code hygiene | HKDF info and wire version byte are independent constants |
345+| N3 | 🟡 medium | DoS | appendMessage dedup O(n) — identical-blob replay amplifies to O(n × batch) |
346+| N4 | 🟡 medium | Impl bug | capForwards non-deterministic eviction when retry counts equal |
347+| N5 | 🟡 medium | Design gap | fromServer not verified against connecting peer address |
348+| N6 | 🔵 low | Info | genToken entropy waste (one digit per call) |
349+| N7 | 🟡 medium | Impl concern | seen_ids dedup set unbounded — grows without limit |
350+| N8 | ⚪ info | Safe | Cursor crash window — persisted cursor is safe |
351+| N9 | 🟡 medium | Impl concern | Budget exhaustion livelock — client stuck if relay always serves oversized page |
352+| N10 | ⚪ info | Safe | Profile ts >= replay is a no-op |
353+| N11 | ⚪ info | Safe | Negative ts clamped to 0 is harmless |
354+| N12 | ⚪ info | Safe | ack_ids non-string filtering is correct |
355+| N13 | 🟠 high | Design gap | Gossip amplification 100x — O(100 × |messages|) per request |
356+| N14 | 🟡 medium | Design gap | Offline events don't cancel pending forwards |
357+| N15 | 🟡 medium | Deploy | install.sh checksum is best-effort — missing checksum silently proceeds |
358+| N16 | ⚪ info | Safe | install.sh DOMAIN validation is correct |
359+| N17 | ⚪ info | Safe | Redirect cancellation prevents token exfiltration |
360+| N18 | ⚪ info | Safe | Keychain ThisDeviceOnly is correct |
361+
362+**Critical (1):** N1
363+**High (1):** N13
364+**Medium (6):** N3, N4, N5, N7, N9, N14, N15
365+**Low (1):** N6
366+**Info (7):** N2, N8, N10, N11, N12, N16, N17, N18
367+
368+---
369+
370+## Priorities
371+
372+1. **N1 (critical):** Add AAD to AEAD. This is the most impactful finding — it enables
373+ undetectable censorship by any relay. Requires wire-format change (v0x02).
374+
375+2. **N13 (high):** Document or limit gossip amplification. A single request triggers 100
376+ mailbox scans. Cap newly-online keys that trigger forwards per batch.
377+
378+3. **N9 (medium):** Fix budget exhaustion livelock. Advance cursor to last processed event
379+ instead of restoring to pre-page cursor. This prevents a malicious relay from permanently
380+ wedging the client with oversized poll pages.
381+
382+4. **N7 (medium):** Bound `seen_ids` set. An unbounded dedup set that's rewritten on every
383+ message receipt will degrade performance over time.
384+
385+5. **N3 (medium):** Index `*messages` for dedup. The O(n) scan is a CPU amplification vector.
AUDIT-NEW.mdnew file+816
@@ -0,0 +1,816 @@
1+# Skrepka Security Audit — New Findings (2026-07-15)
2+
3+**Scope:** Exhaustive multi-pass audit of PROTOCOL.md, server.knot, and core/src/ (app.rs, crypto.rs, protocol.rs, model.rs, phonemic.rs, ffi.rs). Findings below are **not** documented in PROTOCOL-REVIEW.md.
4+
5+**Legend:** 🔴 critical · 🟠 high · 🟡 medium · 🔵 low · ⚪ info
6+
7+---
8+
9+## 1. Cryptographic Protocol Weaknesses
10+
11+### 🔴 Q1. HKDF salt omits sender identity — KCI/UKS not prevented by construction
12+
13+**Type:** Design gap (protocol + crypto.rs)
14+**Files:** `core/src/crypto.rs:276-290` (`derive_key`), PROTOCOL.md §3 step 3
15+
16+The HKDF salt is `ephemeral_public || recipient_x25519_public` — both public values, neither identifying the sender. The encryption key is derived entirely from the ephemeral X25519 exchange and the recipient's public key. While the Ed25519 signature inside the AEAD binds the sender, the *key derivation* itself has no sender contribution.
17+
18+This means anyone who knows the recipient's private key can compute the same shared secret from a captured ephemeral public key — there's no sender contribution to the KDF. The signature is the only thing binding the sender, and it's verified *after* AEAD decryption. An attacker who obtains the recipient's private key can decrypt all captured blobs (already noted as "no forward secrecy" in §10), but additionally, because the KDF has no sender binding, an attacker can *replace* the sender identity and signature inside a captured ciphertext by re-encrypting with the same ephemeral key — wait, no, they can't re-encrypt without the shared key. However, if the attacker *has* the recipient's private key, they can decrypt, strip the original sender, forge a new inner buffer with their own sender key + signature over the same `recipient || compressed_len || compressed || padding`, re-encrypt with the derived key, and re-send. The recipient sees a valid message from a different sender. This is a *key compromise impersonation (KCI)* vector: compromising the recipient's key lets an attacker re-attribute captured messages.
19+
20+**Attack scenario:** An attacker records ciphertext between Alice and Bob. Later they compromise Bob's private key. They decrypt the blobs, replace Alice's identity with Mallory's (signing under Mallory's key), re-encrypt, and deliver to Bob. Bob sees messages apparently from Mallory.
21+
22+**Exploitable in practice:** Requires recipient key compromise, which the protocol already considers catastrophic. The KCI vector is an *additional* consequence of that compromise, not a standalone attack. Still, including the sender's public key in the HKDF salt or info would close it by construction.
23+
24+**Suggested fix:** Include `sender_ed25519_public` in the HKDF salt or info: `salt = ephemeral_public || recipient_x25519_public || sender_ed25519_public`. Since the sender pubkey is inside the AEAD, a decryptor already has it before verification, but the key derivation would need it — so the sender pubkey would need to be *outside* the AEAD (as associated data or in the blob header), which changes the wire format. Alternatively, accept this as a documented limitation of v0.1 (the signature already prevents forgery without key compromise).
25+
26+### 🟡 Q2. No associated data (AAD) on AEAD — ciphertext is malleable across contexts
27+
28+**Type:** Design gap (protocol + crypto.rs)
29+**Files:** `core/src/crypto.rs:384-387` (encrypt), `core/src/crypto.rs:434-438` (decrypt)
30+
31+XChaCha20-Poly1305 is used with **no associated data**: `cipher.encrypt(nonce, inner)` and `cipher.decrypt(nonce, ciphertext)`. The version byte, ephemeral public key, and nonce are all in the clear and not authenticated. An attacker who can modify the blob in transit (a malicious relay, or a network attacker without TLS) can flip the version byte or corrupt the ephemeral key without any AEAD failure — the AEAD only protects the ciphertext body.
32+
33+While corrupting these fields will cause decryption/verification to fail downstream (wrong key derivation, wrong version), there's no *cryptographic binding* between the outer envelope fields and the inner ciphertext. A relay could, for example, swap the ephemeral public key from one blob with that of another (keeping the same nonce + ciphertext), and the recipient would get a decryption failure rather than an authentication failure — a distinction that matters for error handling and oracle analysis.
34+
35+More importantly, the `to` field in the envelope is **not** authenticated by the AEAD. A relay can change the `to` field on a stored message, redirecting it to a different recipient. That recipient can't decrypt it (wrong key), but the *original* recipient's message is now gone from the mailbox. This is a denial-of-service vector that doesn't require breaking encryption.
36+
37+**Attack scenario:** A malicious relay swaps the `to` field on Alice's message to Bob, replacing it with Charlie's pubkey. Bob never receives the message. Charlie receives garbage (can't decrypt). Neither side gets an error from the protocol.
38+
39+**Exploitable in practice:** Yes — any relay can do this. However, a relay can already drop messages, so this is equivalent in impact to message loss, which is an accepted limitation.
40+
41+**Suggested fix:** Include `version_byte || ephemeral_public || nonce` as AAD in the AEAD. For the envelope-level `to` field, consider including `recipient_ed25519_public` as AAD (it's already in the signed inner buffer, but AAD would make the envelope integrity-checked too). This is a wire-format change (v0x02).
42+
43+### 🟡 Q3. compressed_len field is attacker-controllable and trusted for slicing
44+
45+**Type:** Implementation concern (crypto.rs)
46+**Files:** `core/src/crypto.rs:449-459`
47+
48+During decryption, `compressed_len` is read from the AEAD-decrypted inner buffer and used to slice the `compressed` region: `let compressed = &inner[100..100 + compressed_len]`. The AEAD protects the integrity of the inner buffer, so this field is authenticated — but only *after* decryption. The check `100 + compressed_len > inner.len()` prevents an out-of-bounds read, but a `compressed_len` that points into the padding region (i.e., `compressed_len < actual_compressed_data_len`) would silently feed truncated zstd data to the decompressor, which would fail. Conversely, `compressed_len > actual_compressed_len` would include padding bytes in the zstd frame, which the decompressor might or might not reject.
49+
50+Since the signature is over `recipient_pub || compressed_len_bytes || compressed || padding`, the signed region includes the `compressed_len` field. A tampered `compressed_len` would break the signature. So this is actually well-protected. The concern is that the signature is verified *after* the `compressed_len` is already used for slicing — but since the slice is only used for decompression *after* signature verification (`crypto.rs:472`), this is safe.
51+
52+**Verdict:** Not a bug after careful analysis — the signature covers `compressed_len` and the decompression happens after verification. Downgraded to info.
53+
54+### ⚪ Q4. zstd decompression bomb window before content-size cap
55+
56+**Type:** Implementation defense-in-depth (crypto.rs)
57+**Files:** `core/src/crypto.rs:303-322`
58+
59+The decompressor caps `window_log_max(21)` (2 MiB window) and output at `MAX_PLAINTEXT_LEN + 1` (1 MiB + 1 byte). This is solid. However, a crafted zstd frame with a small window but very long output (many small blocks) could still cause significant CPU consumption before the 1 MiB + 1 byte limit triggers. The `take(MAX_PLAINTEXT_LEN + 1)` read will read one byte past the cap, forcing a full decompression attempt up to that point. This is bounded at ~1 MiB of output, so CPU is bounded too. This is fine.
60+
61+### 🟡 Q5. CRIME/BREACH surface is wider than documented for profile messages
62+
63+**Type:** Spec gap / design weakness (PROTOCOL.md §3)
64+**Files:** PROTOCOL.md §3, §4; `core/src/protocol.rs:73-91`
65+
66+The spec warns about CRIME/BREACH but says "an attacker cannot make the client re-encrypt a chosen variant of a secret on demand." However, `profile` messages compress `display_name`, `bio`, and `photo` together in one zstd frame. If an attacker can influence part of the profile (e.g., the user sets their display name based on something an attacker controls, like a contact's name echoed back), and the profile is broadcast to contacts, the compressed size could leak information. The attacker would need to:
67+
68+1. Influence part of the plaintext that is compressed alongside a secret
69+2. Observe the resulting blob size (which is bucket-padded, so only the bucket boundary leaks)
70+
71+The padding buckets (256, 512, 1024, ...) are coarse enough that the leak is minimal in practice. But the spec's claim that "an attacker cannot make the client re-encrypt a chosen variant of a secret on demand" is too strong: if an attacker sends messages that cause the user to change their display name or bio (e.g., "change your name to match mine"), the re-broadcast compresses attacker-influenced text alongside the user's photo (which is base64 and thus high-entropy/incompressible). The photo being base64 limits the CRIME surface since it's already nearly random.
72+
73+**Exploitable in practice:** Very unlikely given bucket padding and the difficulty of controlling what text gets compressed alongside secrets.
74+
75+**Suggested fix:** Clarify in the spec that the CRIME/BREACH surface extends to profile broadcasts (where attacker-influenced text and user-controlled secrets are compressed together), not just text messages.
76+
77+---
78+
79+## 2. Server Implementation Bugs
80+
81+### 🟠 Q6. `ackPolledMessages` is called before `doPoll` — races with concurrent sends to the same mailbox
82+
83+**Type:** Implementation bug (server.knot)
84+**Files:** `server.knot:1258-1287` (`handlePoll`), `server.knot:1343-1351` (`ackPolledMessages`)
85+
86+In `handlePoll`, the cursor-ack (`ackPolledMessages`) runs inside the setup atomic block, *before* `doPoll` collects events. If a concurrent `/messages` request arrives between the ack and the collect, the new message is appended with a fresh `receivedAt` that is strictly greater than the acked cursor — so it will be picked up by `doPoll`'s collect. This is actually correct behavior.
87+
88+However, there's a subtler issue: the cursor is clamped to `max(0 (min (max t curSeq) cursor))` before the ack. If the client sends a cursor that is *ahead* of `curSeq` (e.g., from a different relay), the clamp to `max t curSeq` could *lower* the cursor, which means `ackPolledMessages` acks less than the client intended. But this is intentional (the comment explains it).
89+
90+After deeper analysis, the ordering here is actually correct — the ack happens first (deleting old messages), then the collect picks up what's left that's newer than the cursor. The race with concurrent sends is handled by STM: the new message gets a fresh `receivedAt > cursor`, so it's picked up.
91+
92+**Verdict:** Not a bug after careful analysis. Downgraded to info.
93+
94+### 🟡 Q7. `appendMessage` dedup is O(n) per message — quadratic under burst
95+
96+**Type:** Implementation performance issue (server.knot)
97+**Files:** `server.knot:919-937` (`appendMessage`)
98+
99+`appendMessage` checks `any (\\m -> m.toKey == toKey && m.encryptedBlob == encryptedBlob) msgs` — a full scan of `*messages` — on every call. For a batch of 100 messages to different recipients, this is 100 × |messages| comparisons. With `maxMessagesPerRecipient = 10000` and many recipients, this can be tens of thousands of comparisons per message. Under sustained throughput this is quadratic.
100+
101+This is documented in the file header ("Everything is intentionally O(n) over flat lists; performance is sacrificed for clarity"), so it's a known design choice, not a security finding per se. But it creates a **DoS amplification** vector: an authenticated sender can send 100 messages per request (up to 60 requests/min = 6000/min), each triggering a full scan of the mailbox. With 10,000 messages per recipient and many recipients, each scan is O(total_messages), making the CPU cost per request proportional to the entire mailbox size.
102+
103+**Attack scenario:** An attacker authenticates (free — just generate a keypair) and sends 100-message batches of junk to many recipients. Each message in the batch triggers a full `*messages` scan for dedup. With a large mailbox, this can consume significant CPU per request.
104+
105+**Exploitable in practice:** Bounded by rate limits (60/min per IP) and the fact that the attacker must be authenticated. The CPU amplification is real but modest.
106+
107+**Suggested fix:** Index `*messages` by `(toKey, encryptedBlob)` or use a hash-based dedup set.
108+
109+### 🟠 Q8. `maxMessagesPerRecipient` eviction destroys genuine mail under flood
110+
111+**Type:** Design gap (server.knot)
112+**Files:** `server.knot:156-182`, `server.knot:926-937`
113+
114+This is documented in the code comments as a "trade, not a fix," but it constitutes a real attack: an authenticated sender (pubkeys are free to mint) can flood a recipient's mailbox with 10,000 junk messages, pushing out all genuine undelivered messages. The recipient's client only sees junk. The comment says "at least the newest messages always land" — but the newest messages are the *attacker's junk*, not the genuine messages that were already queued.
115+
116+The `MAX_POLL_TOTAL_BYTES` client-side budget (64 MiB) means the client processes a bounded amount per poll, but the server has already destroyed the genuine messages by eviction. The client never sees them.
117+
118+**Attack scenario:**
119+1. Victim is offline for a day. Attacker sends 10,000 messages to victim's pubkey.
120+2. Each message is a valid encrypted blob (attacker generates a keypair and encrypts real messages to the victim — they don't need to be decryptable by the victim, just valid blobs).
121+3. Victim comes online, polls, and gets a page of junk. Their genuine messages were evicted.
122+
123+**Exploitable in practice:** Yes — the attacker needs to be authenticated (free) and send 10,000 messages. At 60 requests/min × 100 messages = 6,000/min, this takes ~2 minutes. The rate limit is per-IP, so the attacker needs multiple IPs or time.
124+
125+**Suggested fix:** This is an accepted design tradeoff in the current implementation. A real fix requires per-sender quotas or pricing. Document it in PROTOCOL.md §10 as a DoS vector, not just a capacity concern.
126+
127+### 🟡 Q9. `capForwards` evicts by retry count, not by age — fresh forwards can be dropped
128+
129+**Type:** Implementation bug (server.knot)
130+**Files:** `server.knot:515-522` (`capForwards`), `server.knot:109-110` (`maxForwardsTotal`)
131+
132+`capForwards` keeps the lowest-retry entries (`take maxForwardsTotal (sortBy (\\f -> f.retries) fwds)`). When the outbox exceeds `maxForwardsTotal = 50000`, the *highest-retry* entries are dropped. The comment says these are "closest to `maxForwardRetries` (about to be abandoned anyway)."
133+
134+But there's a subtle issue: a fresh forward (retries: 0) for a *healthy* peer could be dropped if the outbox is full of fresh forwards (all retries: 0) for *failing* peers. The sort is by `retries` only, not by `retries` then by age or destination health. When many entries share `retries: 0`, the `sortBy` is unstable (Knot's sort may not be stable), so *any* retries-0 entry could be dropped — including one for a healthy peer that would have succeeded on the first try.
135+
136+**Attack scenario:** An attacker floods the forwards outbox by gossipping many fake "online" events, causing `forwardQueuedToServer` to stage forwards for many fake servers. Each fails and increments retries. When `maxForwardsTotal` is reached, genuine forwards for healthy peers may be evicted alongside the junk.
137+
138+**Exploitable in practice:** Requires federation to be enabled and the attacker to be able to reach `/federation/gossip`. The genuine forward would be re-staged on the next presence announce, so the impact is a delivery delay, not permanent loss.
139+
140+**Suggested fix:** Sort by `(retries, age)` or skip entries for peers in backoff before capping.
141+
142+### 🟡 Q10. `genToken` entropy is 4 bits per call — collision-resistant but timing-leaky
143+
144+**Type:** Implementation concern (server.knot)
145+**Files:** `server.knot:532-537`
146+
147+`genToken` generates one hex character per recursive call, drawing from `randomInt 16`. Each call to `randomInt` produces 4 bits. For 48 chars (192 bits), this is 48 calls to `randomInt`. The concern is that `randomInt` on the Knot runtime may not be a CSPRNG — the function signature is `IO {random}` which suggests a runtime-provided random source, but the implementation is not visible here.
148+
149+If `randomInt` uses a non-cryptographic PRNG (e.g., a LCG), the 192-bit tokens would be predictable. The auth challenge tokens and session tokens both use `genToken`. If predictable, an attacker could predict future session tokens after observing some.
150+
151+**Exploitable in practice:** Depends on the Knot runtime's `randomInt` implementation, which is not in this codebase. If it uses `/dev/urandom` or equivalent, this is fine. If it uses a userspace PRNG seeded from a low-entropy source, this is critical.
152+
153+**Suggested fix:** Verify that the Knot runtime's `randomInt` uses a CSPRNG. Document the assumption.
154+
155+### 🟡 Q11. `handleVerifyAuth` challenge lookup is O(n) — timing varies with challenge pool size
156+
157+**Type:** Implementation concern (server.knot)
158+**Files:** `server.knot:1210-1214`
159+
160+The challenge verification does `any (\\c -> same c && c.expiresAt > t && matchIp clientIp c.ip) ch` — a linear scan of `*challenges`. With `maxChallenges = 10000`, this is up to 10,000 comparisons per verify. The timing varies with the position of the matching challenge in the list, which could be observable.
161+
162+Combined with the already-documented token comparison timing side-channel (finding B), this adds another timing channel: the time to find the matching challenge leaks its position in the list, which leaks when it was inserted (roughly when the `/auth/challenge` was called).
163+
164+**Exploitable in practice:** Very low impact — the challenge is consumed immediately after verification, and the timing difference is small relative to network jitter.
165+
166+**Suggested fix:** Index challenges by `(pubkey, challenge)` for O(1) lookup.
167+
168+### 🟡 Q12. `handleVerifyAuth` computes signature verification outside atomic — TOCTOU on challenge
169+
170+**Type:** Implementation gap (server.knot)
171+**Files:** `server.knot:1196-1214`
172+
173+The `sigValid` computation is done outside the atomic block (line 1204-1209), but the challenge lookup is inside the atomic (line 1213). Between computing `sigValid` and the atomic block, the challenge could be consumed by a concurrent `/auth/verify` with the same challenge. But the atomic block re-checks: `any (\\c -> same c && ... && c.expiresAt > t && matchIp clientIp c.ip) ch && sigValid`. The `sigValid` is pre-computed, so the check is: challenge exists AND signature is valid. If the challenge is consumed between the pre-compute and the atomic, the `any` returns false, and the verify fails. This is safe — no TOCTOU.
174+
175+But there's a subtler issue: the `clientIp` for the challenge (set at `/auth/challenge` time) and the `clientIp` for the verify (set at `/auth/verify` time) must match (`matchIp clientIp c.ip`). If the client's IP changes between challenge and verify (mobile network change), the verify fails. This is documented as expected behavior. But if `trustForwardedFor` is true and the client can spoof `X-Forwarded-For`, they could set a different IP on the challenge and verify requests — but they'd need to match, so they'd just set the same spoofed IP on both. This is already documented (finding 8).
176+
177+**Verdict:** Not a new bug. The pre-compute is safe because the atomic block re-validates the challenge's existence.
178+
179+### 🟠 Q13. `revokeOthers` race — concurrent sessions for same pubkey can race on revoke
180+
181+**Type:** Implementation bug (server.knot)
182+**Files:** `server.knot:1219-1231`
183+
184+When `revokeOthers: true`, the handler does:
185+```
186+let pruned = if revokeOthers
187+then filter (\\s -> s.pubkey != pubkey) ses
188+else capPerKey ses pubkey maxSessionsPerKey
189+```
190+
191+This drops *all* other sessions for this pubkey. But if a concurrent `/auth/verify` for the same pubkey is in flight (without `revokeOthers`), it could install a new session between the `filter` and the `union`:
192+
193+1. Verify A (revokeOthers=true) reads `*sessions`, filters out all pubkey sessions → `pruned`
194+2. Verify B (revokeOthers=false) reads `*sessions` (still has the old sessions), adds a new one → commits
195+3. Verify A commits `pruned + newSession` → Verify B's session is lost
196+
197+But wait — both are inside `atomic` blocks, and STM guarantees serializability. If Verify A's atomic block retries after Verify B commits, Verify A re-reads `*sessions` (now including B's session) and re-applies the filter — so B's session would be dropped. This is actually the *intended* behavior of `revokeOthers`: it should drop all other sessions. The "race" is really just STM serializing correctly.
198+
199+**Verdict:** Not a bug. STM handles this correctly. Downgraded to info.
200+
201+### 🟡 Q14. `pruneExpired` presence offline gossip may miss peers that expired in a prior sweep
202+
203+**Type:** Implementation concern (server.knot)
204+**Files:** `server.knot:1614-1633` (`backgroundPrune`)
205+
206+The prune loop snapshots peers *before* the sweep (`prePeers`) and unions with *post-sweep* peers. But `pruneExpired` returns only locally-expired keys that have no other live local session. If a key expired in a *previous* sweep (and was already removed from `*presence`), the current sweep has nothing to return for it. The offline gossip for that key was already sent in the previous sweep. This is correct — each key gets exactly one offline event.
207+
208+**Verdict:** Not a bug. The pre/post union handles the edge case correctly.
209+
210+### 🟡 Q15. `forwardQueuedToServer` budget check reads `*forwards` count but doesn't reserve atomically
211+
212+**Type:** Implementation concern (server.knot)
213+**Files:** `server.knot:1140-1151`
214+
215+`forwardQueuedToServer` computes `budget = max 0 (maxForwardsPerServer - existing)` where `existing = countWhere (\\f -> f.toServer == server) fwds`, then takes `take budget` candidates and unions them into `*forwards`. The whole thing is inside one `atomic` block, so it's serializable — two concurrent calls would serialize, and the second would see the first's additions. This is correct.
216+
217+**Verdict:** Not a bug. STM handles concurrency correctly.
218+
219+---
220+
221+## 3. Client Core Logic Bugs
222+
223+### 🟠 Q16. `ingest_poll` cursor clamping uses `now_ms() + 60_000` — relay can advance cursor beyond actual messages
224+
225+**Type:** Implementation concern (app.rs)
226+**Files:** `core/src/app.rs:1967-1975`
227+
228+The cursor is clamped to `page.cursor.min(now_ms().saturating_add(60_000))`. If a hostile relay sends `cursor = now_ms() + 59_000`, the client accepts it, writes it to disk, and the next poll sends this cursor to the relay. If the client later switches to a *different* relay, the cursor is reset to 0 (line 868) — so this is per-relay and not cross-relay. But on the *same* relay, a hostile relay can send an artificially high cursor, causing the client to ack (delete) all messages up to that cursor on the next poll — even messages the client hasn't seen yet.
229+
230+Wait — the cursor is what the *client* sends to the *server*. The server uses it to ack (delete) messages ≤ cursor. If a relay sends a high cursor in the poll response, the client adopts it and sends it back on the next poll. The relay then deletes everything ≤ that cursor. If there were messages the client never received (because the relay withheld them), they're now permanently lost.
231+
232+But the relay already controls what messages it sends to the client — it could simply withhold messages and never show them. The cursor doesn't give the relay any new power it doesn't already have. The relay can always just not send events. So this is not a new attack vector.
233+
234+However, there's a subtler issue: the cursor is persisted to disk. If the relay sends a high cursor and the client adopts it, then the client reconnects to the same relay after a network interruption, the cursor is still high. Any messages that arrived at the relay during the interruption (with `receivedAt` ≤ the poisoned cursor) are automatically acked and deleted.
235+
236+**Attack scenario:** A malicious relay sends `cursor = now_ms() + 59000` in an empty poll response. The client adopts it and persists it. Later, legitimate messages arrive at the relay with `receivedAt` values below the poisoned cursor. The client's next poll sends the poisoned cursor, and the relay deletes those messages.
237+
238+But wait — the relay assigns `receivedAt` using its own monotonic sequence. If the relay is malicious, it can just not deliver messages. If it's honest but was briefly compromised, the poisoned cursor could cause message loss after recovery. This is a real concern for the "briefly compromised relay" scenario.
239+
240+**Exploitable in practice:** A compromised relay can cause permanent message loss for messages that arrive during the compromise window. The 60-second clamp limits the window, but the cursor persists across reconnections.
241+
242+**Suggested fix:** Only adopt the cursor if the poll response contained events. If `events` is empty and `cursor > model.cursor`, don't advance the cursor — the relay has nothing to tell us, and a cursor advance from an empty page is suspicious.
243+
244+### 🟡 Q17. Delivery ack staleness check uses `ts` not `last_ack_ts` watermark for ordering — race with clock skew
245+
246+**Type:** Implementation concern (app.rs)
247+**Files:** `core/src/app.rs:2116-2134`
248+
249+The ack staleness check compares `ts < c.last_ack_ts`. If two acks arrive in the same poll page from the same sender, with `ts_A = 100` and `ts_B = 200`, and `last_ack_ts = 50`:
250+- Ack A (ts=100): not stale (100 >= 50), applies, sets `last_ack_ts = min(100, now)`
251+- Ack B (ts=200): not stale (200 >= 100), applies, sets `last_ack_ts = min(200, now)`
252+
253+This is correct. But if the page order is reversed (B before A), and `last_ack_ts = 50`:
254+- Ack B (ts=200): not stale, applies, sets `last_ack_ts = min(200, now)`
255+- Ack A (ts=100): stale (100 < min(200, now)), dropped!
256+
257+This means an older ack in the same page as a newer one is dropped if it's processed after the newer one. Since the events are processed in page order (not sorted), a relay could reorder events to cause an older ack to be dropped. The impact is minimal — the older ack would have acked fewer or the same messages.
258+
259+**Exploitable in practice:** A malicious relay could reorder events to suppress a specific ack, but it could also just drop the event entirely. Low impact.
260+
261+**Suggested fix:** Process acks in `ts` order within a page, or collect all acks from a sender and apply the highest-ts one.
262+
263+### 🟡 Q18. `seen_ids` dedup set is built lazily from conversation — misses messages trimmed by `MAX_MESSAGES_PER_PEER`
264+
265+**Type:** Implementation bug (app.rs)
266+**Files:** `core/src/app.rs:2086-2092`
267+
268+The dedup set is built from the current conversation: `convo.iter().map(|m| m.id.clone()).collect()`. But `trim_history` may have aged out older messages (keeping only the most recent 1000). A replayed message whose `id` matches an aged-out message would pass the dedup check and be re-inserted into the conversation. The message would appear as a new message (with its original `ts`), potentially at the top of the conversation list if `ts` is high.
269+
270+**Attack scenario:** An attacker captures a message blob (by being a relay, or by gossip redirect), waits until the recipient's conversation has been trimmed past that message (1000+ messages later), then replays the blob. The dedup check misses it (the `id` is no longer in the trimmed conversation), and the message is re-inserted. The message appears as a new old-dated message.
271+
272+**Exploitable in practice:** Requires the attacker to have captured the blob and to wait for 1000+ messages. The replayed message would be inserted at its original `ts` position, so it wouldn't appear at the bottom of the chat — it would appear in its chronological position. The user might not notice. The impact is minimal — it's an old message reappearing, not new content.
273+
274+**Suggested fix:** Maintain a persistent dedup set (not derived from the trimmed conversation), or store the set of seen IDs separately from the message history.
275+
276+### 🟡 Q19. Profile `ts` staleness check uses `>=` — equal-timestamp replay overwrites with identical content (harmless) but also overwrites with *different* content if sender crafts it
277+
278+**Type:** Implementation concern (app.rs)
279+**Files:** `core/src/app.rs:2174-2179`
280+
281+The profile staleness check uses `ts >= c.last_profile_ts`, meaning a replayed profile at the *same* `ts` is accepted. The comment says "a replayed profile at the same `ts` overwrites with identical content, which is a no-op in practice." But this assumes the replayed blob has the same content. An attacker who captures a profile blob can modify the *inner* content (display_name, bio, photo) and re-encrypt it with the same `ts` — but they'd need to sign it, and they can only sign with their own key. The recipient would see it coming from the same sender (the original profile sender), but the signature would be from the original sender's key... wait, no. The attacker can't re-sign with the original sender's key unless they have it.
282+
283+Actually, the attacker *replays the exact same blob* — same ciphertext, same inner content, same signature. The `ts` is the same, and the content is the same. So it's truly a no-op. The attacker can't modify the content without breaking the signature. This is safe.
284+
285+**Verdict:** Not a bug. The `>=` is correct and the replay is a true no-op.
286+
287+### 🟡 Q20. `flush_next` batch-building skips items for different recipients — outbox may have interleaved items stuck behind a large batch
288+
289+**Type:** Implementation concern (app.rs)
290+**Files:** `core/src/app.rs:1818-1853`
291+
292+The batch stops at the first recipient change (`if recipient.as_ref().is_some_and(|r| r != &item.recipient) { break }`). If the outbox has items for recipient A followed by items for recipient B, and A's batch is being built, B's items wait. This is by design (FIFO fairness). But if A's send fails repeatedly, B's items are stuck behind A's retries. The `retry_batch` function charges retries and eventually drops A's items (after `MAX_OUTBOX_RETRIES` or `OUTBOX_TTL_MS`), unblocking B.
293+
294+This is correct behavior, not a bug. The FIFO ordering ensures fairness at the cost of head-of-line blocking, which is the right tradeoff for a messaging app (you don't want a failed send to one peer to reorder sends to another).
295+
296+**Verdict:** Not a bug. Downgraded to info.
297+
298+### 🟡 Q21. `encrypt_for` uses `OsRng` — no deterministic test path, but also no RNG failure handling
299+
300+**Type:** Implementation concern (app.rs)
301+**Files:** `core/src/app.rs:2227-2231`
302+
303+`encrypt_for` uses `let mut rng = rand_core::OsRng;` and passes it to `crypto::encrypt`. If `OsRng` fails (e.g., the OS entropy pool is exhausted on a freshly booted device), `rng.fill_bytes` would panic or return an error. `crypto::encrypt` calls `rng.fill_bytes` in multiple places (`eph_priv`, `padding`, `nonce`), and these would propagate the error up as `CryptoError::Encrypt` (since `fill_bytes` on `OsRng` infallibly fills — it uses `/dev/urandom` which never blocks on modern systems).
304+
305+**Verdict:** `OsRng` is infallible on iOS/macOS (it uses `SecRandomCopyBytes` which always succeeds). Not a bug.
306+
307+---
308+
309+## 4. Wire Format / Parsing Issues
310+
311+### 🟠 Q22. `isValidHex` uses `chars` (set semantics) — deduplication hides length-based attacks
312+
313+**Type:** Implementation bug (server.knot)
314+**Files:** `server.knot:542-545`
315+
316+```knot
317+isValidHex = \s ->
318+ let n = length s in
319+ n > 0 && n / 2 * 2 == n && all (\c -> contains c "0123456789abcdef") (chars s)
320+```
321+
322+`chars s` returns the **distinct** character set (relations dedupe). So for a string like `"aaaa"`, `chars` returns `{"a"}`, and the `all` check passes. The `length` check (`n / 2 * 2 == n`) ensures even length. But `chars` deduplication means the `all` check is O(distinct chars) not O(string length), which is a performance optimization, not a correctness issue — the set membership test covers all characters.
323+
324+This is actually correct: if all *distinct* characters are in the hex alphabet, then all characters are in the hex alphabet. The dedup just makes it faster.
325+
326+**Verdict:** Not a bug. The set semantics are correct for membership checking.
327+
328+### 🟡 Q23. `PubkeyHex` type accepts non-curve-point 32-byte hex values at the route boundary
329+
330+**Type:** Implementation gap (server.knot)
331+**Files:** `server.knot:322` (`type PubkeyHex = Text where isValidExactHex 64`)
332+
333+The `PubkeyHex` type only checks that the string is 64 lowercase hex characters — it doesn't verify the decoded bytes form a valid Ed25519 public key (a valid curve point). The client's `try_parse_pubkey` (`phonemic.rs:140-144`) does check this via `VerifyingKey::from_bytes`, but the server accepts any 64-hex-char string as a valid `PubkeyHex`.
334+
335+This means a client can send a message to a `to` address that is 32 bytes of hex but not a valid Ed25519 public key. The server stores and forwards the blob. The "recipient" can never decrypt it because `ed25519_pk_to_x25519` would fail on the invalid key. The blob sits in the mailbox until TTL expiry, consuming storage.
336+
337+**Attack scenario:** An attacker sends 100 messages per batch to invalid pubkeys. Each is stored for 30 days. With 60 requests/min × 100 = 6000/min, after 1 hour that's 360,000 junk messages. Each counts against `maxMessagesPerRecipient` for the target — but the target is a non-existent key, so nobody is affected. The real concern is storage consumption: 360,000 × minBlobLen bytes = ~62 MB per hour per attacker IP.
338+
339+**Exploitable in practice:** The rate limit (60/min per IP) bounds the rate. The 30-day TTL bounds the total. `maxMessagesPerRecipient = 10000` per non-existent key limits per-key. The total storage impact is bounded.
340+
341+**Suggested fix:** The server could optionally validate that `to` is a valid curve point, but this adds CPU cost and the spec doesn't require it (the server can't decrypt anyway). Document as accepted.
342+
343+### 🟡 Q24. `parse_payload` `ts` field defaults to 0 when missing — allows pre-epoch ordering manipulation
344+
345+**Type:** Implementation concern (protocol.rs)
346+**Files:** `core/src/protocol.rs:100`
347+
348+`let ts = v.get("ts").and_then(|t| t.as_i64()).unwrap_or(0);`
349+
350+If a peer omits the `ts` field (or sets it to a non-integer), it defaults to 0. In `ingest_poll`, `ts` is clamped: `parsed.ts.max(0).min(now.saturating_add(MAX_FUTURE_SKEW_MS))`. A `ts` of 0 passes the `max(0)` check and is used as-is. A message with `ts = 0` would be inserted at position 0 in the conversation (earliest), and `trim_history` would age it out first. This is harmless.
351+
352+But a peer could set `ts` to a very large negative number (e.g., `i64::MIN`), which would be clamped to 0. Same result. Or a peer could set `ts` to a float (e.g., `1.5`), which `as_i64()` returns `None` for, defaulting to 0. All of these are harmless because the clamping handles them.
353+
354+**Verdict:** Not a bug. The clamping in `ingest_poll` handles all edge cases.
355+
356+### 🟡 Q25. JSON parsing of poll response uses `unwrap_or_default()` — malformed JSON silently produces empty page
357+
358+**Type:** Implementation concern (app.rs)
359+**Files:** `core/src/app.rs:1309`
360+
361+`let parsed: PollResp = serde_json::from_slice(&bytes).unwrap_or_default();`
362+
363+If the relay sends malformed JSON (or a valid JSON with wrong types), this silently defaults to an empty `PollResp` (empty events, cursor 0). The cursor of 0 would be adopted (clamped), and the next poll would re-fetch from the beginning — re-receiving all messages the client has already seen. The client's dedup (by `id` for text, by `ts` for acks and profiles) would handle the duplicates, but it wastes bandwidth and CPU.
364+
365+A hostile relay could exploit this by sending malformed JSON instead of a real response, forcing the client to re-poll from cursor 0 repeatedly. But the client would just re-process old messages (all deduped) and eventually get the real cursor from a subsequent response. The impact is wasted bandwidth, not data loss.
366+
367+**Suggested fix:** If JSON parsing fails, don't adopt the cursor and back off instead of treating it as an empty page.
368+
369+### 🟡 Q26. `delivery.ack` ack_ids filtering silently drops non-string entries — count vs. filtered count mismatch
370+
371+**Type:** Implementation concern (protocol.rs)
372+**Files:** `core/src/protocol.rs:116-126`
373+
374+The ack_ids parsing filters non-string entries: `raw.iter().filter_map(|x| x.as_str().map(str::to_string)).collect()`. The raw count check (`raw.len() > MAX_ACK_IDS`) happens before filtering, but the post-filter check (`ack_ids.len() > MAX_ACK_IDS`) also happens. However, between the two checks, a peer could pack an array with `MAX_ACK_IDS` entries, some of which are non-strings (e.g., numbers). The raw check passes (`MAX_ACK_IDS` entries), the filter drops some, and the post-check passes (fewer than `MAX_ACK_IDS` strings). This is correct — the filtered count is what matters.
375+
376+But there's a subtlety: a peer could pack `MAX_ACK_IDS + 1` raw entries, all non-strings. The raw check fails (`MAX_ACK_IDS + 1 > MAX_ACK_IDS`), and the payload is dropped. But if the peer packs `MAX_ACK_IDS` raw entries, all non-strings, the raw check passes, the filter drops all of them, and `ack_ids` is empty. The empty ack is then sent to the sender, who processes it (marking nothing as delivered). This is harmless.
377+
378+**Verdict:** Not a bug. The double-check handles this correctly.
379+
380+---
381+
382+## 5. Federation Protocol Issues
383+
384+### 🟠 Q27. Gossip amplification — single `online` event triggers forward of *all* queued messages for a key
385+
386+**Type:** Design gap (server.knot)
387+**Files:** `server.knot:1522-1556` (`handleRecvGossip`)
388+
389+When a `online` event arrives for a key, `forwardQueuedToServer` sweeps the entire mailbox for messages to that key and stages them for forwarding. An attacker can send a single gossip request with 100 `online` events for 100 different keys, each triggering a full mailbox scan and forward staging. This is O(100 × |messages|) per request.
390+
391+More importantly, the attacker can repeatedly send `online` events for the same key. Each time, `forwardQueuedToServer` checks `notYetForwarded` and `notYetDelivered` to avoid duplicates, so re-sending the same event is a no-op for already-forwarded messages. But if the forward failed (404 from the attacker's own server, which doesn't actually have the key online), the forward entry stays in `*forwards` with `retries: 0`. A re-announce doesn't re-stage it (it's already in `*forwards`), but `retryPendingForwards` will retry it on the next sweep.
392+
393+The amplification is: one gossip request (100 events) → 100 mailbox scans + potentially 100 forward entries. Each forward entry triggers an HTTP POST to the `fromServer`. If the `fromServer` is the attacker, they receive 100 forwarded blobs — each a copy of the victim's ciphertext. This is the same as the documented gossip-redirect attack (#2), but the amplification factor (100 events per request) is not documented.
394+
395+**Exploitable in practice:** Same as finding #2, but with 100× amplification per request. The rate limit (60/min per IP) bounds the rate to 6,000 redirected keys per minute per IP.
396+
397+**Suggested fix:** Document the amplification factor. Consider limiting the number of newly-online keys per gossip batch that trigger forwards.
398+
399+### 🟡 Q28. Federation `offline` events don't trigger cleanup of pending forwards
400+
401+**Type:** Design gap (server.knot)
402+**Files:** `server.knot:1535-1541`
403+
404+When an `offline` event is received, the presence row for that `(pubkey, fromServer)` is removed, but pending forwards to that server are *not* cancelled. The forwards stay in `*forwards` and will be retried by `retryPendingForwards` until they either succeed (unlikely — the key is offline at that server), fail 10 times, or the message TTL expires.
405+
406+If the offline event was legitimate (the key actually went offline at that server), the forwards will waste retry attempts for up to `retryBackoffMax × maxForwardRetries` = 8 min × 10 = 80 minutes. During that time, the forwards occupy slots in `maxForwardsPerServer` and `maxForwardsTotal`.
407+
408+If the offline event was spoofed by an attacker (to clear a presence row), the forwards are still retried — and if the key is actually still online at that server, the forward succeeds on retry (the `no_presence` gate would pass because the key has a local session). But the presence row was removed, so `hasLocalPresence` at the peer would fail... wait, the presence row is on *our* side. The peer's presence is independent. The forward goes to the peer, and the peer checks its own local presence. If the key is still online at the peer, the forward succeeds. If not, it gets 404 and is retried.
409+
410+**Exploitable in practice:** An attacker can send fake `offline` events to clear presence rows, but the forwards continue independently. The impact is minimal — presence rows and forwards are decoupled.
411+
412+**Suggested fix:** When processing an `offline` event, optionally drop pending forwards to that server for the offline key (they'll never succeed if the key is truly offline there). But this could cause message loss if the offline event is spoofed. Better to leave as-is.
413+
414+### 🟡 Q29. `fromServer` in gossip events is not verified against the connecting peer's actual address
415+
416+**Type:** Design gap (server.knot)
417+**Files:** `server.knot:1511-1556` (`handleRecvGossip`)
418+
419+The `fromServer` field is a `ServerName` (validated for format), but it's not verified against the actual IP address of the connecting peer. An attacker can connect from IP `1.2.3.4` and claim `fromServer: "legit-relay.example.com"`. The server writes presence rows with `server: "legit-relay.example.com"` and forwards queued messages there. This is the same as the documented gossip-redirect attack (#2), but with a twist: the attacker can claim to *be* a legitimate relay, poisoning the presence table with the legitimate relay's hostname.
420+
421+When the *real* `legit-relay.example.com` later gossips, its events update the presence rows. But the attacker's rows may still be present (different `expiresAt`), and the server has multiple presence rows for the same key on different servers — which is by design. The attacker's row points to `legit-relay.example.com`, so forwards go to the legitimate relay, which doesn't have the key online — and returns 404. The legitimate relay gets junk forward requests.
422+
423+**Exploitable in practice:** This is a variant of the documented gossip-redirect, but with the attacker impersonating a legitimate relay. The legitimate relay receives spurious forward requests (bounded by `forwardRateLimit`).
424+
425+**Suggested fix:** Verify that the connecting peer's IP resolves to the claimed `fromServer` hostname (reverse DNS + forward DNS). This is the standard check for SMTP-like protocols. Blocked on `fetch` not exposing DNS.
426+
427+---
428+
429+## 6. Rate Limiting / DoS Vectors
430+
431+### 🟠 Q30. `/auth/challenge` has no per-pubkey rate limit beyond `maxChallengesPerKey = 5`
432+
433+**Type:** Design gap (server.knot)
434+**Files:** `server.knot:1166-1188` (`handleChallenge`)
435+
436+The challenge pool is globally capped at `maxChallenges = 10000` and per-key at `maxChallengesPerKey = 5`, with per-IP rate limiting at `authRateLimit = 60/min`. An attacker with many IPs (or behind a proxy with XFF spoofing when `trustForwardedFor = true`) can fill the challenge pool with challenges for random pubkeys. Each challenge is 60 seconds, and the pool LRU-evicts. But 10,000 challenges × 60 seconds means the pool is always full, and legitimate challenges are evicted.
437+
438+The comment says this is handled by LRU eviction: "an abandoned challenge may be dropped before its 60 s window elapses, which costs the affected client one retry." So the attacker can cause clients to retry their challenge/verify flow, adding latency but not blocking authentication.
439+
440+**Exploitable in practice:** With XFF spoofing (finding 8), the attacker gets unlimited rate-limit buckets. 60/min per IP × many IPs = thousands of challenges per minute. The pool (10,000) fills in ~3 minutes. After that, legitimate challenges are evicted, and clients must retry. This is a soft DoS — authentication still works but with extra latency.
441+
442+**Suggested fix:** Add a global rate on challenge creation (not just per-IP). Or cap the challenge creation rate per second regardless of source.
443+
444+### 🟡 Q31. `/messages` batch of 100 × 40 MiB would be rejected by body cap, but the rate limit counts requests not messages
445+
446+**Type:** Design gap (server.knot)
447+**Files:** `server.knot:233-234` (`sendRateLimit`), `server.knot:454` (`sendLimit`)
448+
449+The send rate limit is 60 requests/min per IP. Each request can carry up to 100 messages (bounded by the body cap). So the effective message rate is 60 × (body_cap / avg_blob_size) per minute. With a 42 MiB body cap and 42 KiB blobs, that's ~1000 messages per request × 60 = 60,000 messages/min. With 173-byte minimum blobs, it's ~251,000 messages/min per IP.
450+
451+This is documented in the code comment ("the effective message ceiling is higher"), but it means the per-IP rate limit is much less protective than it appears. An attacker with 10 IPs can send millions of messages per minute.
452+
453+**Exploitable in practice:** Bounded by the body cap (42 MiB) and the rate limit (60/min). The total data rate per IP is ~42 MiB × 60 = 2.5 GiB/min, which is significant.
454+
455+**Suggested fix:** Consider a per-message rate limit in addition to the per-request rate limit. Or reduce `maxBatchSize` for unauthenticated senders (but all senders are "authenticated" — they just have free keypairs).
456+
457+### 🟡 Q32. `maxSessions = 10000` LRU eviction is Sybil-floodable — documented but not in PROTOCOL.md §10
458+
459+**Type:** Design gap (server.knot)
460+**Files:** `server.knot:117-126`
461+
462+The code comment documents this: "global LRU eviction is Sybil-floodable: an attacker with enough IPs can evict live users' sessions." But it's not mentioned in PROTOCOL.md §10 as a DoS vector. An attacker with enough IPs can:
463+1. Generate 10,000 keypairs
464+2. Authenticate each one (60/min per IP, so ~167 IPs needed for one batch)
465+3. Fill the session pool
466+4. Legitimate users' sessions are evicted (they get 401 and must re-authenticate)
467+
468+This is a soft DoS — users re-authenticate automatically. But it adds latency and load.
469+
470+**Suggested fix:** Document in PROTOCOL.md §10. Consider per-IP session caps (rejected in the code comment as "collapses without XFF, punishes carrier-NAT") or a global session creation rate limit.
471+
472+### 🟡 Q33. `maxPresence = 100000` — gossip can fill presence table with fake keys
473+
474+**Type:** Design gap (server.knot)
475+**Files:** `server.knot:139-155`
476+
477+An attacker can send gossip with 100 fake `online` events per request (60/min per IP). Each event adds a presence row. With `maxPresencePerServer = 5000` per peer, a single attacker IP can add 5000 rows. With `maxPresence = 100000` globally, it takes 20 distinct attacker hostnames to fill the pool. Once full, legitimate presence rows are evicted by `capList` (LRU by `expiresAt`).
478+
479+Since gossip rows have `onlineGossipTtl = 90 min` and local rows have `sessionExpiry = 60 min`, local rows are evicted first (they expire sooner). The code handles this by exempting local rows from the cap:
480+
481+```
482+let localRows = filter (\\p -> isLocalServer p.server) merged
483+let remoteRows = filter (\\p -> not isLocalServer p.server) merged
484+*presence = union localRows (capList (capPerServer remoteRows from maxPresencePerServer) maxPresence)
485+```
486+
487+So local rows are always kept, and only remote (gossiped) rows are capped. An attacker can fill the remote pool, but local users' presence is never evicted. The impact is that legitimate *remote* presence (from honest peers) is evicted, causing forwards to those peers to fail.
488+
489+**Exploitable in practice:** Requires federation to be enabled and many distinct attacker hostnames (each passing `isBadServerName`). Bounded by `maxPresencePerServer = 5000` per hostname.
490+
491+**Suggested fix:** Document in PROTOCOL.md §10. Consider a per-request limit on newly-added presence rows (currently capped at `maxGossipEvents = 100` per request, which is already a bound).
492+
493+---
494+
495+## 7. Authentication / Session Management
496+
497+### 🟠 Q34. Session token is not bound to the pubkey — token theft grants full impersonation
498+
499+**Type:** Design gap (server.knot)
500+**Files:** `server.knot:356` (`type Session = {token: Text, pubkey: PubkeyHex, expiresAt: Timestamp, ip: Text}`)
501+
502+The session token is a bearer token — anyone who has it can use it. It's bound to `(pubkey, ip, expiry)`, but the `pubkey` binding is only used for *authorization* (e.g., rejecting self-sends), not for *authenticating the request*. The `authedPubkey` function looks up the token and returns the associated pubkey — it doesn't verify that the requester is the same entity that originally authenticated.
503+
504+If an attacker steals a bearer token (e.g., from a compromised proxy's access log), they can use it from the same IP (or any IP if `trustForwardedFor = false` or IP binding is disabled) to poll the victim's mailbox and send messages as the victim.
505+
506+The IP binding (`matchIp`) is the only thing preventing token replay from a different IP. But:
507+- If `trustForwardedFor = false`, IP binding is disabled (empty IP → wildcard).
508+- If the attacker is behind the same NAT/proxy as the victim, they share the IP.
509+- The token is sent in `Authorization: Bearer ***` over HTTP (TLS in production), so it's only protected by TLS.
510+
511+**Attack scenario:** A compromised proxy logs the `Authorization` header. The attacker uses the token from the same IP (or any IP if XFF is off) to poll the victim's mailbox and read their (encrypted) messages. The attacker can also send messages as the victim.
512+
513+**Exploitable in practice:** Requires token theft (compromised proxy, log exposure, or MITM without TLS). The E2E encryption means the attacker can't read message content, but they can send messages as the victim (the server doesn't verify the sender's identity on `/messages` — it only uses the bearer token's pubkey for self-send rejection).
514+
515+**Suggested fix:** This is inherent to bearer-token auth. The spec should document that a stolen bearer token grants full impersonation (modulo IP binding) until it expires (1 hour). Consider shorter token lifetimes or per-request signing.
516+
517+### 🟡 Q35. `revokeOthers: true` doesn't revoke challenges — stale challenge can be used to create a new session after revocation
518+
519+**Type:** Implementation gap (server.knot)
520+**Files:** `server.knot:1217-1221`
521+
522+When `revokeOthers: true`, the handler drops all other sessions for the pubkey, but it does *not* drop outstanding challenges for the pubkey. A challenge issued before the `revokeOthers` call is still valid for 60 seconds. An attacker who captured a challenge (e.g., by observing the `/auth/challenge` response) can still complete the `/auth/verify` flow and get a new session — after the `revokeOthers` call.
523+
524+But wait — the `/auth/verify` handler also checks the challenge's IP binding (`matchIp clientIp c.ip`). If the attacker is on a different IP, the verify fails. If they're on the same IP (NAT/proxy), it succeeds. And the new session is *not* revoked by the `revokeOthers` call (it was made after the call).
525+
526+**Attack scenario:**
527+1. Alice requests a challenge (IP 1.2.3.4)
528+2. Attacker captures the challenge response (from a compromised proxy)
529+3. Alice calls `/auth/verify` with `revokeOthers: true` (to log out other devices)
530+4. Attacker uses the captured challenge to call `/auth/verify` from IP 1.2.3.4 (same NAT)
531+5. Attacker gets a new session — not revoked by step 3
532+
533+**Exploitable in practice:** Requires the attacker to be on the same IP as the victim and to have captured the challenge. The 60-second challenge expiry limits the window.
534+
535+**Suggested fix:** When `revokeOthers: true`, also drop outstanding challenges for the pubkey.
536+
537+### 🟡 Q36. Challenge IP binding uses `clientIpOf` which reads XFF — same spoofing surface as session IP binding
538+
539+**Type:** Implementation gap (server.knot)
540+**Files:** `server.knot:1180-1188` (`handleChallenge`), `server.knot:781-784` (`clientIpOf`)
541+
542+The challenge's `ip` is set to `clientIpOf xForwardedFor`, which is the last XFF hop when `trustForwardedFor` is true. If the attacker can spoof XFF (finding 8), they can set any IP on the challenge, and then use the same spoofed IP on the verify — bypassing the IP binding entirely.
543+
544+This is the same XFF spoofing issue already documented (finding 8), but it applies to the challenge IP binding as well. The challenge IP binding is supposed to prevent a challenge obtained by a relay from being used by a different client — but with XFF spoofing, this protection is nullified.
545+
546+**Verdict:** Same as finding 8. Not a new issue, but the challenge IP binding is an additional affected surface.
547+
548+### 🟡 Q37. No rate limit on `/auth/verify` failures — unlimited signature verification attempts
549+
550+**Type:** Design gap (server.knot)
551+**Files:** `server.knot:475` (`authLimit = 60/min`)
552+
553+The `/auth/verify` route shares the `authLimit` (60/min per IP) with `/auth/challenge`. An attacker can attempt 60 signature verifications per minute per IP. Each verification is an Ed25519 signature check, which is relatively expensive (~0.1ms). 60/min = ~0.01 CPU-seconds/min — negligible.
554+
555+But the attacker doesn't need to *succeed* at verification to cause work. Each `/auth/verify` call triggers:
556+1. Hex decode of pubkey (32 bytes) and signature (64 bytes)
557+2. Ed25519 signature verification (expensive: ~0.1ms)
558+3. Linear scan of `*challenges` (up to 10,000 entries)
559+
560+The challenge scan only happens if the signature is valid (short-circuit), so a failed signature still costs the Ed25519 verification. With 60/min per IP and many IPs, the attacker can cause non-trivial CPU load.
561+
562+**Exploitable in practice:** Bounded by rate limits. The Ed25519 verification is fast. Not a practical DoS vector.
563+
564+**Suggested fix:** Consider returning 401 immediately if no matching challenge exists (before verifying the signature), to save the expensive verification when the challenge is invalid. Currently the order is: check challenge exists AND signature valid, with `sigValid` pre-computed. If the challenge doesn't exist, the `any` short-circuits and `sigValid` is never used — but `sigValid` was already computed outside the atomic. So the CPU cost is paid regardless. Move the signature verification inside the atomic block, after the challenge existence check, to short-circuit on missing challenges.
565+
566+Wait, actually looking at the code more carefully:
567+
568+```knot
569+let sigValid = case bytesFromHex pubkey of ... -- computed OUTSIDE atomic
570+result <- atomic (do
571+ ...
572+ let valid = any (\\c -> same c && ...) ch && sigValid -- sigValid used here
573+```
574+
575+`sigValid` is pre-computed, so the Ed25519 verification happens on every `/auth/verify` call regardless of whether a matching challenge exists. This is a CPU waste. If the challenge doesn't exist, the `any` returns false and `sigValid` is irrelevant — but the CPU was already spent.
576+
577+**Suggested fix:** Move the signature verification inside the atomic block, after the challenge existence check. Or compute it lazily (only if the challenge exists).
578+
579+### 🟡 Q38. `handleVerifyAuth` logs session eviction count but not the attacker — no audit trail for Sybil floods
580+
581+**Type:** Implementation gap (server.knot)
582+**Files:** `server.knot:1240`
583+
584+The handler logs `logWarn ("session pool full: evicted N session(s)...")` but doesn't log the pubkey or IP of the request that caused the eviction. An operator investigating a Sybil flood would see warnings but not know which pubkeys or IPs are responsible. This makes it hard to block the attacker.
585+
586+**Suggested fix:** Include the requesting pubkey and IP in the log message.
587+
588+---
589+
590+## 8. Spec Gaps
591+
592+### 🟡 Q39. Spec doesn't specify behavior for empty `encryptedBlob`
593+
594+**Type:** Spec gap (PROTOCOL.md §4)
595+**Files:** PROTOCOL.md §4 (Envelope), `server.knot:319-320` (`isValidBlobHex`)
596+
597+The spec says `encryptedBlob` is "Hex-encoded blob from §3" but doesn't say what happens if it's empty or shorter than `minBlobLen`. The server enforces `isValidBlobHex` (min 346 chars = 173 bytes), but the spec doesn't mention this minimum. An independent implementation might accept shorter blobs and store garbage.
598+
599+**Suggested fix:** Add the minimum blob length to PROTOCOL.md §4 or §5.
600+
601+### 🟡 Q40. Spec doesn't specify JSON encoding requirements (UTF-8, key ordering, whitespace)
602+
603+**Type:** Spec gap (PROTOCOL.md §4, §5)
604+**Files:** PROTOCOL.md §4, §5
605+
606+The spec shows JSON examples but doesn't specify:
607+- Whether keys must be in a specific order (the server uses `GossipEvent` with `eventType` and `pubkey` — order matters for some JSON parsers)
608+- Whether whitespace is allowed in the JSON (a client could send pretty-printed JSON)
609+- Whether UTF-8 is required (JSON spec allows UTF-16/UTF-32, but the server likely only handles UTF-8)
610+- Whether duplicate keys are allowed (JSON allows them, but behavior is undefined)
611+
612+These could cause implementation divergence. For example, a client that sends `{"encryptedBlob": "...", "to": "..."}` (keys reversed) would work with most JSON parsers but might confuse a strict implementation.
613+
614+**Suggested fix:** Specify that all JSON is UTF-8, keys are unordered, whitespace is allowed, and duplicate keys are undefined behavior (last one wins).
615+
616+### 🟡 Q41. Spec doesn't specify what `cursor: 0` means vs absent cursor
617+
618+**Type:** Spec gap (PROTOCOL.md §6)
619+**Files:** PROTOCOL.md §6 (`POST /poll`)
620+
621+The spec says `cursor` is "the maximum `receivedAt` value the client has already seen (`0` on first poll)." But what if the client sends `cursor: -1` or omits the field? The server's `handlePoll` clamps to `max 0 (...)`, so negative cursors become 0. But the spec doesn't say this.
622+
623+**Suggested fix:** Specify that cursor must be ≥ 0, and that 0 means "first poll" (no messages acked).
624+
625+### 🟡 Q42. Spec doesn't specify `to` field validation requirements
626+
627+**Type:** Spec gap (PROTOCOL.md §4, §6)
628+**Files:** PROTOCOL.md §4 (Envelope), PROTOCOL.md §6 (`POST /messages`)
629+
630+The spec says `to` is "Recipient's Ed25519 public key (64 lowercase hex)" but doesn't say:
631+- Must it be a valid Ed25519 public key (a valid curve point)?
632+- Is the server required to validate it?
633+- What happens if it's the sender's own key? (The server rejects this as `self_send`, but the spec doesn't say the server should check this — it's an implementation detail)
634+
635+**Suggested fix:** Specify that `to` must be 64 lowercase hex chars (the server validates format only), and that the server rejects self-sends with `400 self_send`.
636+
637+### 🟡 Q43. Spec doesn't specify the format of `challenge` in auth
638+
639+**Type:** Spec gap (PROTOCOL.md §6)
640+**Files:** PROTOCOL.md §6 (Authentication)
641+
642+The spec says the challenge is "a random challenge string" but doesn't specify:
643+- Its length or entropy
644+- Its format (hex? base64? raw text?)
645+- Whether it must be unique per challenge request
646+
647+The server uses `genToken 48` (48 hex chars, 192 bits). The client signs it as part of the auth message. If an independent implementation uses a shorter challenge (e.g., 8 chars), it would be brute-forceable.
648+
649+**Suggested fix:** Specify minimum challenge length (e.g., 32 hex chars / 128 bits) and format (lowercase hex).
650+
651+### ⚪ Q44. Spec doesn't specify `revokeOthers` semantics precisely
652+
653+**Type:** Spec gap (PROTOCOL.md §6)
654+**Files:** PROTOCOL.md §6 (Authentication step 3)
655+
656+The spec says `revokeOthers: true` "invalidates every other live session for this pubkey" but doesn't specify:
657+- Whether it also invalidates challenges (it doesn't — see Q35)
658+- Whether the revocation is immediate or eventual (it's immediate within the atomic block)
659+- What happens to in-flight requests using a revoked session (they get 401 on the next request)
660+
661+**Suggested fix:** Clarify that only sessions (not challenges) are revoked, revocation is immediate, and revoked sessions get 401 on their next request.
662+
663+---
664+
665+## 9. Privacy / Metadata Leaks
666+
667+### 🟠 Q45. Blob size reveals message type to the server
668+
669+**Type:** Privacy leak (protocol + design)
670+**Files:** PROTOCOL.md §3 (Length Padding), `core/src/protocol.rs:60-91`
671+
672+The padding buckets (256, 512, 1024, ...) obscure the exact compressed size, but the bucket boundaries still leak information about the message type:
673+- A `delivery.ack` with a single ID is tiny (~50 bytes JSON) → compresses to ~40 bytes → inner buffer ~233 bytes → blob ~233 + 16 (AEAD) = 249 → rounds to 256 bucket
674+- A `text` message with a short body is ~100 bytes JSON → compresses to ~80 bytes → inner buffer ~273 bytes → blob ~289 → rounds to 512 bucket
675+- A `profile` with a 64 KiB photo → compresses poorly (base64 is high-entropy) → inner buffer ~65 KiB → rounds to 65536 bucket
676+
677+So the server can distinguish:
678+- A `delivery.ack` (256 bucket) from a `text` (512 bucket) from a `profile` with photo (65536 bucket)
679+- A short text (512) from a long text (1024+)
680+
681+This is a metadata leak beyond what's documented. The spec says "message length is only ever obscured *upward*" and "blob size still distinguishes a one-word reply from a pasted document" — but it doesn't mention that blob size reveals the *message type* (text vs ack vs profile).
682+
683+**Attack scenario:** A relay observes that Alice sends Bob a 256-bucket blob → it's a delivery.ack (Alice received Bob's message). Then Alice sends a 65536-bucket blob → it's a profile update. The relay learns the *pattern* of communication (who acks whom, who updates their profile) without decrypting anything.
684+
685+**Exploitable in practice:** The bucket boundaries are coarse but sufficient to distinguish message types. This is a real metadata leak for a "metadata-privacy-focused messenger."
686+
687+**Suggested fix:** Use a single minimum padding bucket (e.g., always pad to at least 1024 bytes) to make all small messages indistinguishable. Or add random padding within the bucket to add noise. Or pad all messages to the same size (expensive but maximally private).
688+
689+### 🟡 Q46. `receivedAt` timing reveals sender-recipient correlation to the relay
690+
691+**Type:** Privacy leak (server.knot)
692+**Files:** `server.knot:919-925` (`appendMessage`)
693+
694+The server assigns `receivedAt` at message arrival time. If Alice sends a message to Bob via relay R, R records the arrival time. If Bob polls R shortly after, R records the poll time. The correlation between arrival and poll times reveals that Bob was online and received the message — even though the server doesn't know who sent it.
695+
696+This is inherent to the relay model (the server must see the recipient and timing), and is documented in §10 ("Recipient metadata exposure"). But the spec understates the leak: it says "servers see the recipient pubkey and arrival time" — it doesn't mention that the server can correlate arrival and poll times to infer delivery.
697+
698+**Suggested fix:** Document in §10 that the relay can infer delivery by correlating message arrival with recipient poll times.
699+
700+### 🟡 Q47. Poll cursor reveals the recipient's last-seen position to the relay
701+
702+**Type:** Privacy leak (server.knot)
703+**Files:** `server.knot:432-433` (cursor), `server.knot:1265-1275` (cursor clamping)
704+
705+The client sends its cursor (last-seen `receivedAt`) on every poll. This tells the relay exactly how far behind the recipient is — how many messages they haven't read yet. A relay can use this to:
706+- Determine if the recipient is actively reading (cursor advances each poll) or just polling (cursor stays the same)
707+- Estimate the recipient's reading speed (how fast the cursor advances)
708+- Detect when the recipient switches devices (cursor jumps backward)
709+
710+This is inherent to the long-poll model but not documented in §10.
711+
712+**Suggested fix:** Document in §10 that the cursor reveals the recipient's reading progress to the relay.
713+
714+---
715+
716+## 10. TOFU and Key Management
717+
718+### 🟠 Q48. No key change detection — TOFU silently accepts key changes without warning
719+
720+**Type:** Design gap (protocol + app.rs)
721+**Files:** PROTOCOL.md §2 (Trust Model), `core/src/app.rs:2043-2045` (sender check)
722+
723+The spec says "the first time a client encounters a public key, it is accepted and cached" and "Warn users when a contact's public key changes (TOFU violation)." But the implementation doesn't have a mechanism for key changes — because the protocol has no key rotation (§11 is future work).
724+
725+However, there's a subtler issue: the sender's identity is *inside* the AEAD ciphertext. If an attacker sends a message to Bob encrypted to Bob's key, signing with Mallory's key, Bob's client will:
726+1. Decrypt the blob (it's encrypted to Bob's key, so it decrypts successfully)
727+2. Recover the sender's pubkey (Mallory's)
728+3. Check if Mallory is in Bob's contacts
729+4. If not, auto-create a contact for Mallory and display the message
730+
731+This is by design (anyone can send you a message). But if the attacker can somehow get Bob to add Mallory's key as a contact (e.g., by social engineering), and then later send messages that appear to come from Mallory, there's no mechanism to detect that "Mallory" has changed keys — because the key IS the identity.
732+
733+The real TOFU weakness is: if Bob adds Alice's key, and Alice's key is later compromised, an attacker with Alice's key can send messages that appear to come from Alice. There's no way for Bob to detect this without out-of-band verification. The spec acknowledges this ("TOFU only" in §10), but the implementation doesn't provide a UI for out-of-band verification (comparing @p syllables).
734+
735+**Exploitable in practice:** This is the fundamental TOFU weakness, already acknowledged in the spec. The implementation gap is the lack of a verification UI, but that's a product feature, not a protocol bug.
736+
737+**Suggested fix:** Add a UI for fingerprint verification (showing @p syllables for comparison) and a warning when a new contact's key hasn't been verified.
738+
739+### 🟡 Q49. `Identity::from_secret_bytes` validates the keypair but doesn't check for weak keys
740+
741+**Type:** Implementation gap (crypto.rs)
742+**Files:** `core/src/crypto.rs:150-166`
743+
744+`from_secret_bytes` re-derives the public key from the seed and checks it matches. But it doesn't check for weak Ed25519 keys (e.g., keys where the X25519 derived key is a low-order point). The `x25519` function checks for all-zero shared secrets (low-order point detection), but this only fires during encryption/decryption, not at key load time.
745+
746+If the user's Ed25519 key happens to produce an X25519 public key that is a low-order point, every encryption to them would fail with `InvalidEphemeralKey` (because `x25519(eph_priv, recip_x)` would return all-zero). The user would be unable to receive messages but wouldn't know why.
747+
748+The probability of this is negligible (low-order points are extremely rare on Curve25519), but the code doesn't check for it at key generation time.
749+
750+**Suggested fix:** Check `x25519_public` is not a low-order point at key generation/load time. Report an error if it is.
751+
752+### 🟡 Q50. No mechanism to revoke or invalidate a compromised identity key
753+
754+**Type:** Design gap (PROTOCOL.md §11)
755+**Files:** PROTOCOL.md §11 (Future Extensions — Key Rotation)
756+
757+The spec acknowledges this in §11 (future work): "a user who loses or wants to retire a key has no in-protocol way to say so." There's no key revocation, no key rotation, and no mechanism to tell contacts that a key is compromised.
758+
759+If a user's key is stolen, the attacker can:
760+1. Decrypt all captured messages (no forward secrecy)
761+2. Send messages as the user (no revocation)
762+3. Poll the user's mailbox (if they know the server)
763+4. Receive messages intended for the user (if they redirect presence)
764+
765+The only defense is out-of-band communication ("my key was compromised, don't talk to the old key anymore"), which requires every contact to manually re-add the new key.
766+
767+**Suggested fix:** This is acknowledged as future work. Document the impact more prominently in §10: a stolen identity key is a full takeover with no in-protocol recovery.
768+
769+---
770+
771+## Summary of New Findings
772+
773+| # | Severity | Type | Title |
774+|---|----------|------|-------|
775+| Q1 | 🟡 medium | Design gap | HKDF salt omits sender identity — KCI vector |
776+| Q2 | 🟡 medium | Design gap | No AAD on AEAD — envelope fields unauthenticated |
777+| Q5 | 🟡 medium | Spec gap | CRIME/BREACH surface wider than documented for profiles |
778+| Q7 | 🟡 medium | Perf/DoS | appendMessage dedup O(n) — CPU amplification |
779+| Q8 | 🟠 high | Design gap | maxMessagesPerRecipient eviction destroys genuine mail |
780+| Q9 | 🟡 medium | Impl bug | capForwards evicts by retry count only, not destination health |
781+| Q10 | 🟡 medium | Impl concern | genToken entropy depends on Knot runtime CSPRNG |
782+| Q11 | 🟡 medium | Impl concern | Challenge lookup O(n) — timing varies with pool size |
783+| Q16 | 🟠 high | Impl concern | Cursor clamping allows relay to poison cursor → message loss |
784+| Q17 | 🟡 medium | Impl concern | Ack staleness check affected by page ordering |
785+| Q18 | 🟡 medium | Impl bug | seen_ids dedup misses trimmed messages → replay after 1000 msgs |
786+| Q23 | 🟡 medium | Impl gap | PubkeyHex accepts non-curve-point keys at route boundary |
787+| Q25 | 🟡 medium | Impl concern | Malformed poll JSON silently produces empty page |
788+| Q27 | 🟠 high | Design gap | Gossip amplification: 100 online events = 100 mailbox scans + forwards |
789+| Q28 | 🟡 medium | Design gap | Offline events don't cancel pending forwards |
790+| Q29 | 🟡 medium | Design gap | fromServer not verified against connecting peer's address |
791+| Q30 | 🟠 high | Design gap | /auth/challenge pool floodable — soft DoS via XFF spoofing |
792+| Q31 | 🟡 medium | Design gap | Rate limit counts requests not messages — effective rate much higher |
793+| Q32 | 🟡 medium | Design gap | maxSessions Sybil-floodable (documented in code, not in spec) |
794+| Q33 | 🟡 medium | Design gap | maxPresence fillable with fake keys (documented in code, not in spec) |
795+| Q34 | 🟠 high | Design gap | Session token not bound to pubkey — theft = full impersonation |
796+| Q35 | 🟡 medium | Impl gap | revokeOthers doesn't revoke challenges |
797+| Q37 | 🟡 medium | Design gap | Signature verification CPU wasted on missing challenges |
798+| Q38 | 🟡 medium | Impl gap | No audit trail (pubkey/IP) for Sybil eviction |
799+| Q39 | 🟡 medium | Spec gap | Spec doesn't specify min blob length |
800+| Q40 | 🟡 medium | Spec gap | Spec doesn't specify JSON encoding requirements |
801+| Q41 | 🟡 medium | Spec gap | Spec doesn't specify cursor validation |
802+| Q42 | 🟡 medium | Spec gap | Spec doesn't specify `to` field validation |
803+| Q43 | 🟡 medium | Spec gap | Spec doesn't specify challenge format/entropy |
804+| Q44 | ⚪ info | Spec gap | Spec doesn't specify revokeOthers semantics precisely |
805+| Q45 | 🟠 high | Privacy leak | Blob size reveals message type (ack vs text vs profile) to relay |
806+| Q46 | 🟡 medium | Privacy leak | receivedAt timing reveals delivery correlation |
807+| Q47 | 🟡 medium | Privacy leak | Poll cursor reveals reading progress to relay |
808+| Q48 | 🟠 high | Design gap | No key change detection — TOFU has no verification UI |
809+| Q49 | 🟡 medium | Impl gap | No weak key check at identity load time |
810+| Q50 | 🟡 medium | Design gap | No identity key revocation mechanism (acknowledged future work) |
811+
812+**High-severity findings (7):** Q8, Q16, Q27, Q30, Q34, Q45, Q48
813+**Medium-severity findings (24):** Q1, Q2, Q5, Q7, Q9, Q10, Q11, Q17, Q18, Q23, Q25, Q28, Q29, Q31, Q32, Q33, Q35, Q37, Q38, Q39, Q40, Q41, Q42, Q43, Q46, Q47, Q49, Q50
814+**Info (1):** Q44
815+
816+Note: Several findings marked as "not a bug" during analysis were downgraded to info or omitted from the final table. The table includes only findings that represent genuine new issues.
Cargo.lock+1
@@ -1797,6 +1797,7 @@ name = "skrepka_core"
17971797version = "0.1.0"
17981798dependencies = [
17991799 "anyhow",
1800+ "base64",
18001801 "boltffi",
18011802 "chacha20poly1305",
18021803 "clap",
Cargo.toml+2−1
@@ -28,7 +28,7 @@ crux_kv = "0.13"
2828crux_time = "0.17"
2929boltffi = "0.26"
3030facet = { version = "=0.44", features = ["chrono"] }
31−serde = { version = "1.0", features = ["derive"] }
31+serde = { version = "1.0", features = ["derive", "rc"] }
3232serde_json = "1.0"
3333
3434# crypto
@@ -43,6 +43,7 @@ rand_core = { version = "0.6", features = ["getrandom"] }
4343rand_chacha = "0.3"
4444uuid = { version = "1", features = ["v4"] }
4545hex = "0.4"
46+base64 = "0.22"
4647zeroize = { version = "1", features = ["derive"] }
4748url = "2"
4849
PROTOCOL-REVIEW.md+231−7
@@ -139,15 +139,11 @@ So a batch can carry one max-size blob or many small ones, but total ≤ 42 MiB.
139139
140140---
141141
142−## ❌ 7. No crypto / wire-format version negotiation
142+## ✅ 7. No crypto / wire-format version negotiation — fixed
143143
144−**Severity: low — open.**
144+**Severity: low — fixed.**
145145
146−`HKDF_INFO = "skrepka-v1"` is hardcoded (`core/src/crypto.rs`), and neither the
147−envelope nor the plaintext payload carries a version field. "Ignore unknown
148−`type`" (`protocol::parse_payload`) gives payload-type agility but no path to
149−rotate the AEAD/KDF/curve. Recommend a stated version field or an explicit "no
150−crypto agility in v0.1" note.
146+`HKDF_INFO = "skrepka-v1"` is hardcoded (`core/src/crypto.rs`), and the plaintext payload carries no version field. The wire format now carries a leading version byte (`WIRE_VERSION = 0x01`, `core/src/crypto.rs`): `encrypt` prepends it, and `decrypt` reads and checks it before any other processing, returning `CryptoError::Decrypt` on mismatch. `MIN_BLOB_LEN` includes the extra byte (169 bytes). "Ignore unknown `type`" (`protocol::parse_payload`) gives payload-type agility; the version byte gives the same for the wire format, AEAD, KDF, and curve choices. A future revision that changes crypto primitives should bump both the version byte and the HKDF `info` string.
151147
152148---
153149
@@ -181,6 +177,36 @@ protection without the proxy caveat. Recommend documenting it.
181177
182178---
183179
180+## 🟡 9. Federation retry loop can starve the prune sweep
181+
182+**Severity: low — design tradeoff, not a code bug.**
183+
184+`backgroundRetryForwards` runs `retryPendingForwards` inline (not via `fork`),
185+so a sweep that hits many slow or timing-out peers blocks until every
186+`fetch` in the batch resolves. Each `fetch` has no explicit timeout — the
187+runtime's HTTP client holds the connection — so a sweep over N unreachable
188+peers can take N × (TCP connect timeout) before returning. During that time
189+`backgroundPrune` (on its own `fork`) is free to run, but its writes to
190+`*messages` and `*forwardFailures` conflict with `retryPendingForwards`'s
191+`atomic` blocks, so `pruneExpired`'s atomic retries lose to the retry loop
192+and are effectively starved: expired messages, sessions, and challenges
193+pile up until the retry sweep finishes.
194+
195+In practice this only matters under federation with many dead peers and a
196+low `retryBackoffMax` — the `shouldRetryServer` gate skips peers in backoff,
197+so after one failed sweep most peers are gated out of the next one. The
198+first sweep after a network partition is the worst case.
199+
200+**No fix applied.** The deliberate design (inline, not forked) prevents two
201+concurrent `retryPendingForwards` from seeing the same `*forwards` snapshot
202+and double-counting `recordFailure`. Forking it would reintroduce that race.
203+A real fix would either (a) give `fetch` a deadline and bound the sweep
204+time, or (b) run `retryPendingForwards` in a transaction that yields
205+`*messages`/`*forwardFailures` to `pruneExpired` between per-peer batches.
206+Both need runtime support the current `fetch` does not expose.
207+
208+---
209+
184210## Suggested follow-ups
185211
1862121. **Spec edits (safe, no behavior change):** fold #2, #4, #6, #8 caveats into
@@ -190,3 +216,201 @@ protection without the proxy caveat. Recommend documenting it.
190216 guard) are **done**.
1912173. #2 and #4 are inherent to open, unauthenticated federation — decide whether to
192218 document-as-accepted or add peer authentication.
219+4. **#9** is a design tradeoff; document as accepted until `fetch` supports a
220+ deadline.
221+
222+---
223+
224+## Findings blocked on runtime/protocol support (2026-07-13 audit)
225+
226+These findings are documented here for tracking. Each is blocked on a capability
227+the current runtime or protocol does not expose, so no code fix is possible
228+today.
229+
230+### ❌ A. `now_ms()` impurity breaks MVU replayability
231+
232+**Severity: medium — blocked on `crux_time` refactor.**
233+
234+`now_ms()` reads the system clock from inside `update()` (app.rs:427), which is
235+supposed to be a pure function of `(Event, Model)`. This affects `SendText`,
236+`SaveProfile`, `ingest_poll`, `flush_next` (first_attempt stamping), and ack
237+timestamping. The state machine cannot be replayed deterministically, and tests
238+cannot pin "now".
239+
240+The fix is to take the time as a `crux_time` effect and feed it back as an
241+event — but every timestamped path would become a two-step round-trip through
242+the shell. A TODO comment is in place at the call site. This refactor is worth
243+doing but is not a drive-by fix.
244+
245+### ❌ B. Token comparison timing side-channel
246+
247+**Severity: medium — blocked on Knot runtime.**
248+
249+`s.token == token` is plain string equality, which short-circuits on the first
250+differing byte (server.knot:761). An attacker who can time the response learns
251+how many leading characters of a guess were correct. Bounded by the 192-bit
252+token and per-IP rate limit. The correct fix is a `constantTimeEquals` primitive
253+in the Knot runtime. Documented in PROTOCOL.md §6 and in-code comments.
254+
255+### ❌ C. Open federation — gossip redirect & forward injection
256+
257+**Severity: high — accepted v0.1 limitation, blocked on peer authentication.**
258+
259+Both `/federation/*` endpoints are unauthenticated. An attacker can redirect a
260+victim's queued ciphertext or inject blobs into an online recipient's mailbox.
261+Fully documented in PROTOCOL-REVIEW.md #2, #4 and PROTOCOL.md §10. The fix
262+requires signed presence gossip and authenticated forward requests, which needs
263+a key-to-home-server binding the protocol does not yet define.
264+
265+### ❌ D. SSRF deny-list is lexical only
266+
267+**Severity: medium — blocked on `fetch` exposing DNS resolution.**
268+
269+`isBadServerName` inspects the hostname string, never the resolved address.
270+DNS-rebinding TOCTOU bypasses it. The fix needs resolve-then-pin (fuse DNS
271+resolution with connection), which `fetch` does not expose. Documented in
272+PROTOCOL-REVIEW.md and in-code comments at `isBadServerName`.
273+
274+### ❌ E. Federation retry sweep can starve the prune sweep
275+
276+**Severity: low — design tradeoff, blocked on `fetch` deadline support.**
277+
278+`backgroundRetryForwards` runs inline, so a sweep over many unreachable peers
279+blocks until every `fetch` resolves. The prune sweep's writes conflict with the
280+retry loop's atomic blocks. A fix needs either a `fetch` deadline or a
281+transaction that yields between per-peer batches, neither of which the current
282+`fetch` supports. Documented in PROTOCOL-REVIEW.md #9.
283+
284+---
285+
286+## Fixed in third-pass audit (2026-07-13)
287+
288+### ✅ F. Cursor advanced before budget check — message loss on oversized poll page
289+
290+**Severity: high — fixed.**
291+
292+`ingest_poll` advanced `model.cursor` to `page.cursor` before the event loop.
293+If the `MAX_POLL_TOTAL_BYTES` budget was exhausted mid-page, the loop broke
294+but the cursor stayed at `page.cursor`. The next poll acked the whole page to
295+the relay, which deleted every event the client never processed — permanent
296+message loss. A relay serving 4+ large blobs (each up to 20 MiB) in a single
297+50-event page was enough to trigger this.
298+
299+**Fix:** Save the pre-page cursor and restore it when the budget is exhausted.
300+
301+### ✅ G. `send_text` did not check if peer is blocked
302+
303+**Severity: medium — fixed.**
304+
305+Blocking was documented as cutting a peer off in both directions, and the
306+ingest side correctly dropped blocked peers' messages. But `send_text` had no
307+block check, so a user could keep sending messages to a blocked contact. The
308+Swift `ChatView` composer was also not disabled for blocked peers.
309+
310+**Fix:** `send_text` now refuses with an error when the active peer is blocked.
311+The Swift composer disables both the text field and the send button when
312+`activePeerBlocked` is true.
313+
314+### ✅ H. `compressed` and `signed` intermediates not zeroized in `crypto::encrypt`
315+
316+**Severity: low — fixed.**
317+
318+The `inner` buffer was correctly `Zeroize`d after encryption, but the
319+`compressed` (compressed plaintext) and `signed` (signature input containing
320+recipient_pub + compressed + padding) intermediates were plain `Vec<u8>`s
321+that retained sensitive data in freed memory. Both are now `Zeroizing<Vec<u8>>`.
322+
323+### ✅ I. PROTOCOL.md §10 "No cryptographic agility" contradicted §3
324+
325+**Severity: spec only — fixed.**
326+
327+The §10 risk table said "The wire format has no version field" but §3 had
328+been updated to describe a version byte (`0x01`) and a "Cryptographic
329+Versioning" section. The table entry now accurately reflects the version
330+byte's existence and its limitations.
331+
332+### ✅ J. PROTOCOL.md §4 "Blocking" didn't match implementation
333+
334+**Severity: spec only — fixed.**
335+
336+The spec said blocked senders' messages "are still received and decrypted but
337+are not displayed." The implementation drops them after decryption (the sender
338+identity is inside the AEAD ciphertext, so decryption is necessary to learn who
339+the message is from). The spec now accurately describes the implementation:
340+messages are decrypted to recover the sender identity, then dropped without
341+storage, display, or ack, and blocking is bidirectional.
342+
343+---
344+
345+## Fixed in sixth-pass audit (2026-07-13)
346+
347+### ✅ K. No send-side body length check — silent message loss
348+
349+**Severity: medium — fixed.**
350+
351+`send_text` did not check `body.len()` against `protocol::MAX_BODY_LEN`. The
352+recipient's `parse_payload` enforces the cap and silently drops oversized text,
353+so a user who pastes a very long message would see it stored locally, sent to
354+the relay, and marked "sent" — but it would never arrive, never get acked, and
355+the sender would see it stuck as "sent" forever with no error.
356+
357+**Fix:** `send_text` now refuses with `"message too long"` before queueing.
358+
359+### ✅ L. No profile field length checks in SaveProfile — silent broadcast failure
360+
361+**Severity: medium — fixed.**
362+
363+`SaveProfile` broadcast `display_name`, `bio`, and `photo` without checking
364+against `MAX_DISPLAY_NAME_LEN` (128 chars), `MAX_BIO_LEN` (1024 chars), or
365+`MAX_PHOTO_LEN` (64 KiB). Every recipient's `parse_payload` would silently drop
366+the oversized profile, creating a divergence between what the sender sees and
367+what contacts see.
368+
369+**Fix:** All three fields are validated before the profile is saved or broadcast.
370+
371+### ✅ M. `Decrypted` plaintext not zeroized
372+
373+**Severity: low — fixed.**
374+
375+The `inner` buffer and `signed` intermediate were carefully `Zeroizing<Vec<u8>>`,
376+but the output `Decrypted { plaintext: Vec<u8> }` escaped the zeroization
377+boundary. The decrypted message content sat in freed memory until the allocator
378+reused that page. `plaintext` is now `Zeroizing<Vec<u8>>`.
379+
380+### ✅ N. No send watchdog — stuck `flushing` guard
381+
382+**Severity: low — fixed.**
383+
384+The poll loop had a watchdog (`POLL_WATCHDOG_MS`) that recovered from a dropped
385+HTTP effect, but the send loop had no equivalent. If `SendResult` never came
386+back (a cancelled task, a backgrounded app, a bug), `flushing` stayed `true`
387+forever and the outbox was permanently stuck. A `FlushWatchdog` event (armed
388+alongside the send, same pattern as the poll watchdog) now releases the guard
389+and retries the flush after `FLUSH_WATCHDOG_MS` (90 s).
390+
391+### ✅ O. No nickname length check in AddContact
392+
393+**Severity: very low — fixed.**
394+
395+The `nickname` in `AddContact` was stored without any length bound. A user could
396+set a megabyte-long nickname, bloating the contacts kv blob (rewritten in full on
397+every change). `nickname.len()` is now checked against `MAX_DISPLAY_NAME_LEN`.
398+
399+---
400+
401+## Fixed in seventh-pass audit (2026-07-14)
402+
403+### ✅ P. `encrypt`'s `inner` buffer not zeroized on AEAD failure
404+
405+**Severity: low — fixed.**
406+
407+The `inner` buffer in `crypto::encrypt` (sender pubkey || signature ||
408+compressed_len || compressed || padding) was a plain `Vec<u8>`. It was
409+explicitly `zeroize()`d on the success path, but if `cipher.encrypt()`
410+returned `Err`, the `?` operator returned early and `inner` was dropped
411+without zeroization — the sender's identity, signature, and compressed
412+plaintext remained in freed memory. Every other sensitive intermediate in
413+`encrypt` (`compressed`, `signed`, `padding`, `eph_priv`, `raw_secret`,
414+`key`) was already `Zeroizing`; `inner` was the sole exception. Now
415+`Zeroizing<Vec<u8>>`, matching the pattern established for `decrypt`'s
416+`inner` and `signed` in the fourth-pass audit.
PROTOCOL.md+138−36
@@ -1,6 +1,6 @@
11# Skrepka Protocol Specification
22
3−**Version:** 0.1 (Draft)
3+**Version:** 0.2 (Draft)
44
55---
66
@@ -110,7 +110,7 @@ The wire-visible "envelope" carries only the recipient and the opaque blob. The
110110 key = hkdf_sha256(
111111 ikm = raw_secret,
112112 salt = ephemeral_public || recipient_x25519_public,
113− info = "skrepka-v1",
113+ info = "skrepka-v2",
114114 len = 32
115115 )
116116 ```
@@ -118,39 +118,53 @@ The wire-visible "envelope" carries only the recipient and the opaque blob. The
118118 ```
119119 compressed = zstd(plaintext_bytes) // standard zstd frame (embeds content size)
120120 ```
121−5. Sign the recipient pubkey concatenated with the compressed plaintext. Binding the signature to the recipient prevents the same blob from being replayed against another recipient:
121+5. Sign a domain-separation tag, the recipient pubkey, and the compressed plaintext with padding. The `"skrepka-msg-v2:"` prefix is a domain-separation tag distinguishing message signatures from auth-challenge signatures (which begin with `"skrepka-auth-v1:"`, §6), so a signature produced in one context can never validate in the other. Binding the signature to the recipient prevents the same blob from being replayed against another recipient:
122122 ```
123+ compressed_len = uint32_be(len(compressed))
124+ padding = random_bytes(target_blob_size - unpadded_blob_size)
123125 signature = ed25519_sign(sender_ed25519_private,
124− recipient_ed25519_public || compressed)
126+ "skrepka-msg-v2:" || recipient_ed25519_public || compressed_len || compressed || padding)
125127 ```
1261286. Build the inner buffer that will be encrypted:
127129 ```
128− inner = sender_ed25519_public || signature || compressed
130+ inner = sender_ed25519_public || signature || compressed_len || compressed || padding
129131 ```
130−7. Generate a random 24-byte nonce and AEAD-encrypt the inner buffer:
132+7. Generate a random 24-byte nonce and AEAD-encrypt the inner buffer with
133+ associated data binding the envelope header and recipient identity:
131134 ```
132135 nonce = random_bytes(24)
133− ciphertext = xchacha20_poly1305_encrypt(key, nonce, inner) // no associated data
136+ aad = version_byte || ephemeral_public || nonce || recipient_ed25519_public
137+ ciphertext = xchacha20_poly1305_encrypt(key, nonce, inner, aad)
134138 ```
139+ The AAD authenticates every cleartext field a relay can see (version,
140+ ephemeral public key, nonce) and the recipient's Ed25519 public key.
141+ A relay that swaps the envelope `to` field to a different recipient causes
142+ AEAD decryption to fail at the wrong recipient — the blob is dropped before
143+ any cursor advance, and the original recipient's message stays in the
144+ mailbox. Without AAD, a relay could silently misdeliver messages by
145+ swapping `to`, making the censorship undetectable to both sender and
146+ recipient.
1351478. Emit the on-wire blob:
136148 ```
137− blob = ephemeral_public || nonce || ciphertext
149+ blob = version_byte || ephemeral_public || nonce || ciphertext
138150 ```
151+ where `version_byte` is `0x02` (see *Cryptographic Versioning* below).
139152
140153**Decryption flow:**
141154
142−1. Split the blob: 32-byte `ephemeral_public`, 24-byte `nonce`, remainder is `ciphertext`.
155+1. Read the leading version byte (reject the blob if it is not recognized). Split the rest: 32-byte `ephemeral_public`, 24-byte `nonce`, remainder is `ciphertext`.
1431562. Derive the recipient's X25519 private key from the recipient's Ed25519 private key, compute the raw shared secret with `ephemeral_public`, and HKDF-derive the same `key`.
144−3. AEAD-decrypt the ciphertext to recover the inner buffer.
145−4. Split: 32-byte `sender_ed25519_public`, 64-byte `signature`, remainder is `compressed`.
146−5. Verify the signature over `recipient_ed25519_public || compressed` using `sender_ed25519_public`. Reject the message on failure.
147−6. zstd-decompress to recover the plaintext payload.
157+3. Reconstruct the AAD: `version_byte || ephemeral_public || nonce || recipient_ed25519_public`. AEAD-decrypt the ciphertext with this AAD to recover the inner buffer.
158+4. Split: 32-byte `sender_ed25519_public`, 64-byte `signature`, 4-byte `compressed_len` (big-endian u32), then `compressed_len` bytes of `compressed` (the remainder is padding).
159+5. Verify the signature over `"skrepka-msg-v2:" || recipient_ed25519_public || inner[96..]` (i.e. the domain-separation tag followed by `compressed_len || compressed || padding`) using `sender_ed25519_public`. Reject the message on failure.
160+6. zstd-decompress the `compressed` bytes (only the `compressed_len`-length slice, not the trailing padding) to recover the plaintext payload.
148161
149162### Encrypted Blob Format
150163
151164On the wire (cleartext, server-visible):
152165
153166```
167+version (1 byte, currently 0x02)
154168ephemeral_x25519_pubkey (32 bytes)
155169nonce (24 bytes)
156170ciphertext (variable, includes 16-byte AEAD tag)
@@ -161,20 +175,34 @@ After AEAD decryption, the inner buffer is:
161175```
162176sender_ed25519_pubkey (32 bytes)
163177signature (64 bytes)
164−compressed_plaintext (variable, zstd)
178+compressed_len (4 bytes, big-endian u32)
179+compressed_plaintext (variable, zstd; exactly compressed_len bytes)
180+padding (variable, random)
165181```
166182
167−The sender's pubkey and signature are inside the AEAD ciphertext: the server never sees them, and only the intended recipient can recover the sender's identity. The minimum blob size is `32 + 24 + 32 + 64 + 16 = 168` bytes. A relay rejects any blob shorter than that as malformed (`400`), since it cannot possibly carry an envelope.
183+The sender's pubkey and signature are inside the AEAD ciphertext: the server never sees them, and only the intended recipient can recover the sender's identity. The `compressed_len` field tells the recipient exactly where the zstd frame ends, so trailing padding bytes are never fed to the decompressor. The minimum blob size is `1 + 32 + 24 + 32 + 64 + 4 + 16 = 173` bytes (346 hex chars). A relay rejects any blob shorter than this with `400 invalid_message`, since it cannot possibly carry a valid envelope.
168184
169−> **Compression before encryption leaks plaintext structure.** The payload is zstd-compressed *then* encrypted (steps 4–7), so the ciphertext length is a function of how *compressible* the plaintext was, not just how long it was. XChaCha20-Poly1305 is a stream cipher with no padding: the blob is exactly `72 + len(compressed)` bytes, and that number is visible to every relay and network observer.
185+### Length Padding
186+
187+Blob sizes are padded to fixed boundaries so the on-wire length does not reveal the exact compressed (and thus plaintext) size to relays and network observers. The padding is added *inside* the AEAD ciphertext (after the compressed data, before encryption), so the server only sees the padded size.
188+
189+The bucket boundaries are:
190+
191+```
192+256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536
193+```
194+
195+A blob is rounded up to the smallest bucket ≥ its unpadded size. Above 65536 bytes, the blob is rounded up to the next multiple of 65536. The padding bytes are randomly generated per message, so two encryptions of the same plaintext produce the same blob size (same bucket) but different blob contents. The on-wire blob is therefore `173 + len(compressed) + len(padding)` bytes, and that padded size is all a relay or network observer sees.
196+
197+> **Compression before encryption leaks plaintext structure.** The payload is zstd-compressed *then* encrypted (steps 4–7), so the ciphertext length is a function of how *compressible* the plaintext was, not just how long it was. XChaCha20-Poly1305 is a stream cipher with no padding: without length padding the blob would be exactly `173 + len(compressed)` bytes, and that number would be visible to every relay and network observer. Version 0x02 adds length padding (see *Length Padding* above), which buckets blob sizes to fixed boundaries so the exact compressed size is hidden.
170198>
171199> Two consequences. First, message length is only ever obscured *upward*: a long but repetitive message can produce a smaller blob than a short random-looking one, and blob size still distinguishes a one-word reply from a pasted document. Second — the more serious one — where an attacker can influence part of the plaintext that is compressed together with a secret, the compressed size reveals whether the two share structure. That is the CRIME/BREACH pattern, and it is a real (if narrow) concern for a format that compresses attacker-influenceable text alongside sensitive text in one frame.
172200>
173−> Skrepka accepts this: payloads are small, each message is compressed independently (no cross-message compression context), and there is no adaptive-guessing oracle in the protocol — an attacker cannot make the client re-encrypt a chosen variant of a secret on demand. Implementations must **not** add one (e.g. by compressing several messages, or attacker-supplied and user-supplied text, into a shared frame). A future revision should add length padding (e.g. bucket blobs to fixed sizes), which is the only real mitigation.
201+> Skrepka accepts the remaining risk: payloads are small, each message is compressed independently (no cross-message compression context), and there is no adaptive-guessing oracle in the protocol — an attacker cannot make the client re-encrypt a chosen variant of a secret on demand. Implementations must **not** add one (e.g. by compressing several messages, or attacker-supplied and user-supplied text, into a shared frame). Length padding (version 0x02) obscures the exact compressed size by bucketing blob lengths, but does not eliminate the CRIME/BREACH side channel within a single bucket — it only makes the granularity coarser.
174202
175203### Cryptographic Versioning
176204
177−There is currently **no version field** on the wire or in the plaintext payload, and the HKDF `info` string is the fixed constant `"skrepka-v1"`. The unknown-`type` rule (§4) gives forward compatibility for *payload* types, but the wire format, AEAD, KDF, and curve choices have no negotiated version, so there is no in-band path to migrate them without a flag day. A future revision should introduce an explicit protocol version (e.g. a leading version byte on the blob, or a `v` field) to allow cryptographic agility.
205+The wire format carries a leading **version byte** (currently `0x02`) on every encrypted blob. A recipient that sees a version it does not recognise MUST reject the blob without attempting further processing (no AEAD decrypt, no key derivation, no decompression) — the reference client returns a decryption error and drops the blob. This ensures a future revision can introduce a new AEAD, KDF, or curve by bumping this byte without risk of misinterpreting an unknown format. Version 0x02 adds AEAD associated data (AAD): the cleartext header `version_byte || ephemeral_public || nonce` and the recipient's Ed25519 public key are authenticated alongside the ciphertext, so a relay that tampers with any envelope field — including swapping the `to` recipient — causes AEAD decryption to fail rather than silently misdelivering the blob. The HKDF `info` string is the fixed constant `"skrepka-v2"` for version 0x02. The unknown-`type` rule (§4) gives forward compatibility for *payload* types; the version byte gives the same for the wire format, AEAD, KDF, and curve choices. A future revision that changes the crypto primitives should bump both the version byte and the HKDF `info` string together — the reference implementation derives the info string from the version to ensure they cannot drift (see `crypto.rs`).
178206
179207---
180208
@@ -193,10 +221,10 @@ The envelope is what servers see. It carries only the recipient and the opaque e
193221
194222| Field | Type | Description |
195223|-----------------|--------|--------------------------------------------------|
196−| `to` | string | Recipient's Ed25519 public key (64 lowercase hex)|
197−| `encryptedBlob` | string | Hex-encoded blob from §3 |
224+| `to` | string | Recipient's Ed25519 public key — exactly 64 lowercase hex chars. The server validates the **format** only (length and charset); it does not verify the decoded bytes form a valid Ed25519 curve point. |
225+| `encryptedBlob` | string | Hex-encoded blob from §3. Must be at least 346 hex chars (173 bytes); the server rejects shorter blobs with `400 invalid_message`. |
198226
199−Servers route based on `to`. They cannot inspect `encryptedBlob` and they do not know the sender.
227+Servers route based on `to`. They cannot inspect `encryptedBlob` and they do not know the sender. The `to` field is format-validated only — the server does not check that it represents a valid Ed25519 curve point, so blobs addressed to non-existent keys are stored and forwarded normally (the intended recipient simply cannot decrypt them). A message whose `to` matches the authenticated sender's own pubkey is rejected with `400 self_send` (§6, *POST /messages*).
200228
201229### Plaintext Payload
202230
@@ -212,7 +240,7 @@ After decryption (and zstd decompression), the plaintext is a UTF-8 JSON object
212240
213241- `type` and `ts` are present on every payload. `ts` is the sender's wall-clock at send time, in **milliseconds** since the Unix epoch.
214242- `id` is a client-generated unique ID (e.g. UUID v4) carried by `text` messages only. Clients deduplicate incoming `text` messages by `id`. `delivery.ack` and `profile` payloads do not carry an `id`.
215−- Clients MUST silently ignore message types they do not recognize. This allows newer clients to introduce new types without breaking older ones.
243+- Clients MUST silently drop message types they do not recognize — no error is surfaced to the sender, and the blob is treated as if it were not there. This allows newer clients to introduce new types without breaking older ones.
216244
217245### Message Types
218246
@@ -226,6 +254,21 @@ The current implementation defines three plaintext message types:
226254
227255Future message types (media attachments, read receipts, group messages) are not part of this revision.
228256
257+### Payload Size Limits
258+
259+A decrypted payload is attacker-controlled: a peer can put any value in any field. The reference client enforces the following caps and silently drops a payload that exceeds any of them (treated identically to an unknown type). An independent client SHOULD enforce the same caps, or it risks storing, rendering, and re-transmitting unbounded attacker-supplied data.
260+
261+| Field | Cap | Rationale |
262+|-------------------|-------------|--------------------------------------------------------|
263+| `text.body` | 64 KiB | A text body is never legitimately this long. |
264+| `text.id` | 128 chars | IDs are UUIDs; 128 chars is generous. |
265+| `profile.display_name` | 128 chars (Unicode) | A display name is not a bio. |
266+| `profile.bio` | 1024 chars (Unicode) | Enough for a paragraph. |
267+| `profile.photo` | 64 KiB (base64) | A 256px JPEG is ~10-30 KiB; 64 KiB is headroom. |
268+| `delivery.ack.ack_ids` | 1024 entries | Bounds the O(n·m) scan a peer can dictate. |
269+
270+The caps on `display_name` and `bio` are measured in Unicode characters (not bytes), so a multi-byte emoji costs the same as an ASCII letter. A payload sitting exactly at the cap is accepted; the bound is inclusive.
271+
229272### Profiles
230273
231274Users share a display name, bio, and photo with contacts by sending a `profile` message. This is a regular encrypted message — servers never see profile data.
@@ -260,7 +303,7 @@ This is the only delivery-confirmation channel in the protocol: the server itsel
260303
261304### Blocking
262305
263−Blocking is client-side only. A blocked sender's messages are still received and decrypted but are not displayed to the user. The protocol does not provide a mechanism to tell a server to reject messages from a specific pubkey.
306+Blocking is client-side only. A blocked sender's messages are decrypted to recover the sender identity (which lives inside the AEAD ciphertext, §3), then dropped without storage, display, or ack — the reference client does not store, display, or ack them. Decryption is necessary because the sender identity is inside the AEAD ciphertext; the decrypted content is never persisted or shown. The protocol does not provide a mechanism to tell a server to reject messages from a specific pubkey. Blocking also cuts the peer off in the other direction: the reference client refuses to send new messages to a blocked contact and drops any queued outgoing messages (including delivery acks) for them when the block is applied.
264307
265308---
266309
@@ -295,7 +338,12 @@ This file is a static suggestion, not a federation directory. Federation between
295338
296339### Content Type
297340
298−All request and response bodies use `application/json`.
341+All request and response bodies use `application/json`. The following encoding rules apply to every JSON body (request and response):
342+
343+- **Encoding:** UTF-8. Implementations MUST NOT use UTF-16 or UTF-32.
344+- **Key ordering:** Object keys are unordered. A sender may emit them in any order; a receiver MUST NOT depend on key ordering for correctness.
345+- **Whitespace:** Inter-token whitespace (spaces, tabs, newlines) is allowed and does not affect semantics. Pretty-printed JSON is valid.
346+- **Duplicate keys:** If an object contains the same key more than once, behavior is undefined. Implementations SHOULD avoid producing duplicates and MAY reject or retain only the first value for a repeated key.
299347
300348### Federation Transport
301349
@@ -328,8 +376,9 @@ When a client connects, it proves ownership of its keypair:
328376 ```json
329377 { "challenge": "<random_hex>", "expiresAt": 1679003660000 }
330378 ```
379+ The challenge is a lowercase hex string of at least 32 chars (128 bits of entropy). The reference server uses 48 hex chars (192 bits). The challenge MUST be unique per challenge request and consumed on first use (verified).
331380
332−3. Client signs the **UTF-8 bytes of `"skrepka-auth-v1:" + server_host + ":" + challenge`** with its Ed25519 private key and submits. `server_host` is the bare lowercased hostname of the server the client dialed (no scheme, no port, no trailing dot). The `skrepka-auth-v1:` prefix is a domain-separation tag distinguishing auth signatures from message signatures (which sign `recipientPub ++ compressed`, §4):
381+3. Client signs the **UTF-8 bytes of `"skrepka-auth-v1:" + server_host + ":" + challenge`** with its Ed25519 private key and submits. `server_host` is the bare lowercased hostname of the server the client dialed (no scheme, no port, no trailing dot). For IPv6 literals, the host must include square brackets (e.g. `[::1]`), matching the URL host syntax — the server's `serverHost` configuration must also include brackets for IPv6. The `skrepka-auth-v1:` prefix is a domain-separation tag distinguishing auth signatures from message signatures (which begin with `"skrepka-msg-v2:"` and sign `recipientPub ++ compressed`, §3):
333382 ```
334383 POST /auth/verify
335384 {
@@ -340,7 +389,7 @@ When a client connects, it proves ownership of its keypair:
340389 }
341390 ```
342391 The server verifies against its own configured hostname (`serverHost`, port stripped). Binding the signature to the target host prevents a malicious or relay server from forwarding a challenge it obtained from a *different* server and replaying the client's signature there to impersonate the client (§10, *Unauthenticated session relay*).
343− Setting `revokeOthers: true` invalidates every other live session for this pubkey (useful for "log out other devices").
392+ Setting `revokeOthers: true` invalidates every other live session for this pubkey (useful for "log out other devices"). Revocation is **immediate** (within the atomic block that processes the verify) and a revoked session receives `401 unauthorized` on its next request. Note that `revokeOthers` revokes **sessions only**, not outstanding challenges — a challenge issued before the `revokeOthers` call remains valid for its 60-second window. (The reference implementation has been fixed to also drop outstanding challenges for the pubkey on `revokeOthers: true`; independent implementations SHOULD do the same.)
344393
3453944. Server verifies the signature. On success, returns a session token valid for **1 hour**:
346395 ```json
@@ -379,10 +428,12 @@ Errors return a non-2xx HTTP status with a body of:
379428| 401 | `unauthorized` | `/poll` or `/messages` with a missing, invalid, or expired token, or a request from a different IP |
380429| 403 | `federation_disabled` | A `/federation/*` endpoint was called while federation is disabled |
381430| 404 | `no_presence` | Federated forward arrived for a recipient with no live local session |
382−| 413 | `batch_too_large` | A `/messages` batch exceeds the 100-message cap |
431+| 413 | `batch_too_large` | A `/messages` batch exceeds the 100-message cap. A bare `413` with no JSON body (the runtime's HTTP body-size cap, `--http-max-body-bytes`) is also possible when the total request body exceeds the operator-configured limit; clients MUST treat a bodyless `413` the same as `batch_too_large` for retry purposes. Operators **must** set `--http-max-body-bytes` above `maxBlobLen` plus the JSON envelope (the reference deployment uses `42M`), otherwise the runtime's default 16 MiB cap rejects a maximum-size blob before the per-blob `400` check is reached. |
383432| 429 | (HTTP only) | Per-route rate limit exceeded |
384433| 503 | `capacity` | Server-side resource cap reached |
385434
435+> **Timing side-channel on token comparison (known gap).** The reference server compares the presented bearer token against each stored session token with plain string equality, which short-circuits on the first differing byte and so leaks, through response timing, how long a correct prefix an attacker guessed. The 192-bit token and the per-IP rate limit on `/poll` and `/messages` bound the attack — a blind guess is infeasible, and the sample count needed to resolve a per-byte timing difference across a network is large — but they do not eliminate it. A constant-time comparison is the correct fix; the reference implementation is blocked on the absence of such a primitive in its runtime. Implementations on platforms that offer one (`crypto_verify`, `subtle`, `hmac.compare_digest`, …) SHOULD use it.
436+
386437### `POST /poll` — Long poll for new events
387438
388439The client makes a blocking POST. The server holds the connection open until new events are available or the long-poll timeout (25 s) elapses.
@@ -394,7 +445,7 @@ The client makes a blocking POST. The server holds the connection open until new
394445{ "cursor": 0 }
395446```
396447
397−`cursor` is the maximum `receivedAt` value the client has already seen (`0` on first poll).
448+`cursor` is the maximum `receivedAt` value the client has already seen. It MUST be a non-negative integer. `0` means "first poll" — no messages have been acked, so the server returns all pending events. Negative cursors are clamped to `0` by the server.
398449
399450**Response:**
400451```json
@@ -407,6 +458,7 @@ The client makes a blocking POST. The server holds the connection open until new
407458```
408459
409460- `cursor` is a server-side **strictly-monotonic sequence**, seeded from the wall-clock millisecond at assignment but bumped to `previous + 1` whenever messages arrive within the same millisecond. Two messages therefore never share a `receivedAt`, so advancing the cursor past one message can never silently drop another. Treat it as an opaque checkpoint, not a clock.
461+- The server clamps the supplied cursor to `max(0, min(max(t, curSeq), cursor))`, where `t` is the current wall-clock millisecond and `curSeq` is the last assigned sequence — note the ceiling is `max(t, curSeq)`, not just `curSeq`, so under idle the clamp allows acking up to the current wall-clock, while under sustained bursts (where the sequence has run ahead of the clock) it still refuses to ack beyond what has actually been issued.
410462- Advancing past a message acts as an **implicit ack**: when the next poll arrives with a `cursor` greater than or equal to a stored message's `receivedAt`, the server drops the stored message **and any pending federation forwards for it**.
411463- If events are available immediately, the server responds right away. Otherwise it parks the connection on a row-level wait against the mailbox and returns when a new matching message lands or after 25 s, whichever comes first.
412464- An empty page (`events: []`) is returned on timeout, with the cursor echoed back.
@@ -628,16 +680,34 @@ Skrepka protects message **content and sender identity** from servers and networ
628680
629681| Risk | Details |
630682|-----------------------------------|-----------------------------------------------------|
631−| **No forward secrecy** | A captured blob plus a later compromise of the recipient's long-term key **is enough to decrypt that message** — the per-message ephemeral key is the *sender's*, and the recipient's half of the exchange is their long-term identity key, which never rotates. So an adversary who records ciphertext today (a network observer, or any relay it passed through) and obtains the recipient's key at any point in the future can read everything it recorded. There is no ratchet, so there is also no post-compromise recovery: once the key leaks, future messages are readable too until the user rotates identity. Do not read the per-message ephemeral keys as forward secrecy; they are not. |
632−| **Recipient metadata exposure** | Servers see the recipient pubkey and arrival time of every message, plus the rough size of each blob. They do **not** see the sender. |
683+| **No forward secrecy** | A captured blob plus a later compromise of the recipient's long-term key **is enough to decrypt that message** — the per-message ephemeral key is the *sender's*, and the recipient's half of the exchange is their long-term identity key, which never rotates. So an adversary who records ciphertext today (a network observer, or any relay it passed through) and obtains the recipient's key at any point in the future can read everything it recorded. There is no ratchet, so there is also no post-compromise recovery: once the key leaks, future messages are readable too until the user rotates identity. Do not read the per-message ephemeral keys as forward secrecy; they are not. **Additionally**, because the HKDF salt (`ephemeral_public ‖ recipient_x25519_public`) omits the sender's identity, compromising the recipient's private key also enables a *key-compromise impersonation (KCI)* vector: the attacker can decrypt a captured blob, replace the sender identity and signature inside the inner buffer with their own, re-encrypt with the same derived key, and re-deliver. The recipient sees a valid message apparently from a different sender. Including the sender pubkey in the HKDF salt or info would close this by construction, but requires a wire-format change. The signature already prevents forgery *without* key compromise, so KCI is an additional consequence of an already-catastrophic key leak, not a standalone attack. |
684+| **No AAD on AEAD — envelope fields unauthenticated** (v0.1, fixed in v0.2) | In v0.1, XChaCha20-Poly1305 was called with no associated data. The envelope's `to` field was not authenticated by the AEAD — a relay could swap `to` to a different recipient's pubkey, silently misdelivering and censoring messages with zero detectability. **v0.2 fixes this**: the AAD includes `version_byte ‖ ephemeral_public ‖ nonce ‖ recipient_ed25519_public`, binding the envelope to the ciphertext. A `to`-swap now causes AEAD failure at the wrong recipient, and the original recipient's message stays in the mailbox. |
685+| **Recipient metadata exposure** | Servers see the recipient pubkey and arrival time of every message, plus the rough size of each blob. They do **not** see the sender. **The relay can also infer delivery** by correlating a message's arrival time with the recipient's subsequent poll time — the gap between the two reveals whether the recipient was online and actively reading. |
686+| **Blob size reveals message type** | The length-padding buckets (§3, *Length Padding*) are coarse enough that a relay can distinguish payload types: a `delivery.ack` with a single ID (~233 bytes) falls in the 256-byte bucket, a short `text` message falls in the 512-byte bucket, and a `profile` with a photo falls in the 65536-byte bucket. A relay observing the bucket pattern learns who acks whom and who updates their profile — without decrypting anything. Finer-grained padding (e.g., a single minimum bucket for all small messages) would reduce this leak. |
687+| **Poll cursor reveals reading progress** | The client sends its cursor (last-seen `receivedAt`) on every poll, telling the relay exactly how far behind the recipient is. A relay can determine whether the recipient is actively reading (cursor advances each poll) or just polling (cursor stays the same), estimate reading speed, and detect device switches (cursor jumps backward). This is inherent to the long-poll model. |
688+| **CRIME/BREACH surface on profiles** | The CRIME/BREACH side channel (§3, *Length Padding*) extends beyond text messages to `profile` broadcasts: `display_name`, `bio`, and `photo` are compressed together in one zstd frame. If an attacker can influence part of the profile text (e.g., the user sets their display name based on something the attacker controls), the compressed size could leak information about the user's other profile fields. The risk is low in practice — the base64-encoded photo is high-entropy and nearly incompressible, and bucket padding coarsens the granularity — but the spec's claim that "an attacker cannot make the client re-encrypt a chosen variant of a secret on demand" is too strong for profile broadcasts. |
633689| **Presence gossip leaks location** | Federated peers learn which server a user is currently connected to. A presence row is anchored for up to 90 min (`onlineGossipTtl`), which outlives the 1 h session, so location metadata — and forwards aimed at the user — can linger for up to ~90 min after the user disconnects. |
634690| **No durable delivery** | If the sender's server goes down or all forward retries fail, messages may be lost. |
635−| **Unauthenticated session relay** (mitigated) | The auth signature is bound to the target server's hostname under a domain-separation tag (§6), so a malicious/relay server can no longer forward another server's challenge and replay the resulting signature to impersonate the client elsewhere — the signature commits to the relay's own hostname. Residual caveat: the binding is to the hostname the client dialed, so it assumes the client reaches each server under its true `serverHost` (DNS/TLS integrity); it does not defend against an attacker who fully controls name resolution and the server's certificate. |
636−| **Same-recipient replay** | Nothing stops a captured blob from being re-delivered to its original recipient. The damage is bounded per payload type: `text` is deduplicated by `id`, `delivery.ack` is idempotent, and `profile` — which carries no `id` — is guarded by the per-contact `ts` staleness check of §4, which the reference client enforces, so a replayed stale `profile` is dropped rather than rolling a contact's cached profile back. A client that omits that check is open to profile rollback. |
637−| **Open federation — gossip redirect** | `/federation/gossip` is unauthenticated, and the harm is *active*, not merely passive observation: an attacker announces the victim online at a host it controls and origin relays forward the victim's queued ciphertext there. See *Open federation* below. |
638−| **Open federation — forward injection** | `/federation/forward` is unauthenticated, so any host can inject arbitrary blobs into a currently-online recipient's mailbox. See *Open federation* below. |
639−| **No cryptographic agility** | The wire format has no version field and a fixed HKDF `info` (§3); the AEAD/KDF/curve cannot be migrated in-band. |
640−| **TOFU only** | A first-time public key is trusted on encounter; users must compare fingerprints out-of-band to detect MITM at first contact. |
691+| **Mailbox eviction under flood (DoS)** | The per-recipient mailbox cap (`maxMessagesPerRecipient`, default 10 000) evicts the oldest messages when the cap is reached. An authenticated attacker (pubkeys are free to mint) can flood a victim's mailbox with junk, pushing out genuine undelivered messages. The victim's client only sees junk; the genuine messages are permanently destroyed. At 60 requests/min × 100 messages = 6 000/min, the attacker fills the cap in ~2 minutes (per IP; multiple IPs are faster). This is an accepted design tradeoff of v0.1 — a real fix requires per-sender quotas or pricing. |
692+| **Unbounded mailbox storage** | The per-recipient mailbox cap (`maxMessagesPerRecipient`) bounds each recipient but not the count of distinct recipient keys. An attacker can fill the server's disk by sending messages to many distinct invalid pubkeys, bounded only by the 30-day TTL and rate limits. The reference server now enforces a global `maxMessagesTotal` cap (default 1 000 000) that evicts the globally-oldest rows on overflow, symmetric with the other state refs. |
693+| **CPU amplification via dedup scan** | `appendMessage` performs an O(n) full-scan dedup check on every message (§6). Under a burst of 100-message batches, each message triggers a scan of the entire mailbox. With large mailboxes this is quadratic and amplifies CPU cost per request. Bounded by rate limits (60/min per IP) and the fact that the attacker must be authenticated, but the amplification is real. |
694+| **Clock forward-jump pins the sequence counter** | The `receivedAt` sequence counter is a forward-only ratchet: `max(wall_clock, previous + 1)`. A single NTP forward-jump (server migration, misconfiguration) pins the counter at the jumped value, delaying all TTL pruning until real time catches up. Backward jumps are safe (the counter dominates). |
695+| **Challenge pool floodable (soft DoS)** | The challenge pool is globally capped at `maxChallenges` (default 10 000) with per-IP rate limiting. An attacker with many IPs — or behind a proxy with XFF spoofing when `trustForwardedFor = true` — can fill the pool with challenges for random pubkeys, causing legitimate challenges to be LRU-evicted. Authentication still works but with extra latency (clients retry). This is a soft DoS. |
696+| **Rate limit counts requests, not messages** | The per-IP send rate limit (60/min) counts requests, and each request can carry up to 100 messages. The effective message rate is therefore 60 × 100 = 6 000 messages/min per IP (bounded by the body-size cap), much higher than the per-request limit suggests. An attacker with multiple IPs can send millions of messages per minute. |
697+| **Session pool Sybil-floodable** | The global session pool (`maxSessions`, default 10 000) uses LRU eviction. An attacker with enough IPs can generate thousands of keypairs, authenticate each one, and fill the pool — evicting legitimate users' sessions. Users re-authenticate automatically (they get `401` and retry), so this is a soft DoS adding latency and load. Per-IP session caps were considered and rejected because they collapse behind carrier-grade NAT. |
698+| **Presence table fillable with fake keys** | The presence table (`maxPresence`, default 100 000) can be filled with fake keys via gossip (100 events per request, 60/min per IP). Local rows are exempt from the cap, so local users' presence is never evicted, but legitimate *remote* presence (from honest peers) can be evicted, causing forwards to those peers to fail. Requires federation to be enabled. |
699+| **Gossip amplification** | A single `/federation/gossip` request with 100 `online` events triggers up to 100 mailbox scans and forward-staging operations. The reference server caps the number of newly-online keys that trigger forward sweeps per batch (`maxNewlyOnlineForwards`, default 10), limiting the amplification to 10× per request. An attacker can still send 100 online events per request, but only 10 trigger forward sweeps; the remaining keys are written to `*presence` without a forward sweep. Bounded by the per-IP rate limit (60/min). |
700+| **`fromServer` not verified** | The `fromServer` field in gossip events is self-asserted and not verified against the connecting peer's actual network address — the server has **no mechanism** to verify that the connecting peer is who it claims to be. An attacker can claim `fromServer: "legit-relay.example.com"` from any IP, poisoning the presence table with the legitimate relay's hostname. Forwards go to the legitimate relay (which doesn't have the key online → 404), causing spurious forward requests. This is a variant of the gossip-redirect attack; the intended fix is reverse-DNS verification of the connecting peer, which requires runtime DNS support not currently available. |
701+| **No identity revocation** | There is no in-protocol mechanism to revoke or invalidate a compromised identity key. A stolen key allows full takeover: decrypt all captured messages, send messages as the user, poll their mailbox, and receive their messages via presence redirect. The only defense is out-of-band communication. See §11 (Future Extensions — Key Rotation) for the intended direction. |
702+| **Unauthenticated session relay** (mitigated) | The auth signature is bound to the target server's hostname under a domain-separation tag (§6), so a malicious/relay server can no longer forward another server's challenge and replay the resulting signature to impersonate the client elsewhere. Residual caveat: the binding is to the hostname the client dialed, so it assumes the client reaches each server under its true `serverHost` (DNS/TLS integrity). |
703+| **Same-recipient replay** | Nothing stops a captured blob from being re-delivered to its original recipient. The damage is bounded per payload type: `text` is deduplicated by `id` (the reference client maintains a persistent `seen_ids` set that survives `trim_history`), `delivery.ack` is idempotent, and `profile` is guarded by the per-contact `ts` staleness check of §4. |
704+| **Open federation — gossip redirect** | `/federation/gossip` is unauthenticated; an attacker announces the victim online at a host it controls and origin relays forward the victim's queued ciphertext there. **Active users are also affected**: even when the recipient is locally online and actively polling, a forged remote presence row causes each new incoming message to be duplicated to the attacker's server — the victim receives everything normally but the attacker silently collects ciphertext metadata for the live inbound stream. See *Open federation* below. |
705+| **Open federation — forward injection** | `/federation/forward` is unauthenticated; any host can inject arbitrary blobs into a currently-online recipient's mailbox. See *Open federation* below. |
706+| **Bearer token theft = full impersonation** | Sessions are bearer-token-based: anyone who obtains the token can use it. The token is bound to `(pubkey, ip, expiry)`, but the `pubkey` binding is for authorization (self-send rejection), not for authenticating the request. If an attacker steals a bearer token (e.g., from a compromised proxy's access log), they can poll the victim's mailbox and send messages as the victim — modulo IP binding. Token expiry (1 hour) is the only automatic recovery. Consider shorter token lifetimes or per-request signing. |
707+| **Token entropy depends on runtime CSPRNG** | Session and challenge tokens are generated by the server's runtime random source. Implementations SHOULD verify that their RNG is cryptographically secure (e.g., backed by `/dev/urandom` or an OS-provided CSPRNG). |
708+| **Non-curve-point `to` keys accepted** | The server validates that `to` is 64 lowercase hex chars but does not check that the decoded bytes form a valid Ed25519 curve point. Blobs addressed to non-existent keys are stored and forwarded normally, consuming storage until TTL expiry. |
709+| **No crypto rotation performed** | The wire format carries a version byte (§3, *Cryptographic Versioning*) and a fixed HKDF `info` (`"skrepka-v2"`), so a future revision *can* introduce new AEAD/KDF/curve choices by bumping both. Version 0x02 added AEAD associated data (AAD) to bind envelope fields to the ciphertext. No further rotation has been performed. |
710+| **TOFU only — no verification UI** | A first-time public key is trusted on encounter; users must compare fingerprints out-of-band (e.g., @p syllables in person) to detect MITM at first contact. The reference client does not yet provide a UI for this out-of-band verification. Independent clients SHOULD implement such a UI. |
641711
642712### Open Federation (accepted limitation of v0.1)
643713
@@ -654,6 +724,8 @@ to every relay it can reach. Each relay holding mail for the victim now forwards
654724
655725**2. Forward injection — spam into an online recipient's mailbox.** `/federation/forward` is unauthenticated, so any host can inject arbitrary blobs into the mailbox of any recipient who is currently locally online. Injected junk is undecryptable, so a client drops it silently on ingest — but it occupies the recipient's poll stream and the relay's mailbox until the cursor advances past it. The only bounds are the per-source-IP rate limit (`forwardLimit`), the SSRF deny-list (which constrains where a relay will *send*, not who may call it), and the `no_presence` gate (which limits injection to online recipients).
656726
727+**3. Forward cancellation — deleting queued mail-in-flight.** The offline-event forward cancellation (§7) **widens** the unauthenticated-gossip blast radius from writing presence to **deleting queued forwards** — an attacker claiming `fromServer: X` can cancel pending forwards to any real relay X by announcing an `offline` event for the relevant key, so mail queued for delivery to X is dropped from the origin's outbox (the message itself stays in `*messages` and is re-forwarded if the key reappears on another peer, so this delays rather than destroys delivery).
728+
657729**Mitigation path.** Both attacks are accepted limitations of v0.1's unauthenticated federation. The intended fix is peer authentication — signed presence gossip and authenticated forward requests — or an explicit peer allow-list gate before `forwardQueuedToServer`. Until then, operators who federate only with trusted peers (or not at all) are unaffected.
658730
659731### Recommendations for Implementers
@@ -663,3 +735,33 @@ to every relay it can reach. Each relay holding mail for the victim now forwards
663735- Consider pinning server TLS certificates for additional transport security.
664736- Federate only with peers operated by trusted operators if presence metadata is sensitive.
665737- Servers SHOULD delete message blobs as soon as the implicit ack (cursor advance) lands.
738+
739+---
740+
741+## 11. Future Extensions
742+
743+Nothing in this section is implemented or normative in v0.1. It records the shape the extension is expected to take, so that clients avoid design choices that would foreclose it.
744+
745+### Key Rotation
746+
747+Identity in Skrepka *is* the Ed25519 keypair (§2), so today a user who loses or wants to retire a key has no in-protocol way to say so: they have to re-share a new key out-of-band, and every contact must re-add them by hand. Worse, because contacts are TOFU (§2, *Trust Model*), a contact who simply receives a message from an unfamiliar key cannot distinguish "my peer rotated" from "someone is impersonating my peer".
748+
749+A future revision may add a `key_rotation` message type (§4) that lets a user signal the change in-band:
750+
751+```json
752+{
753+ "type": "key_rotation",
754+ "new_pubkey": "<hex(new_ed25519_pubkey)>",
755+ "ts": 1679000000000
756+}
757+```
758+
759+The message is a normal plaintext payload: encrypted to each contact and, per §4, signed by the **old** key — which is exactly the point. Only the holder of the retiring key can announce its successor, so the announcement carries the same authority as any other message from that identity, and a recipient who already trusts the old key can extend that trust to the new one without a fresh out-of-band fingerprint check. Recipients would update the contact entry in place: replace the stored pubkey with `new_pubkey`, keep the existing display name, avatar, and message history, and retain the old key only as a *former identity* so that already-received messages still verify.
760+
761+Open questions a full specification must settle:
762+
763+- **Proof of possession of the new key.** A signature by the old key alone proves the *announcement* is authentic, not that the announcer holds the new secret. A cross-signature (the payload additionally signed by the new key, over both pubkeys) closes that gap and should be considered mandatory.
764+- **Ordering and replay.** Rotations must be totally ordered per identity, or a replayed old `key_rotation` could roll a contact back to a superseded key. The per-contact `ts` staleness rule of §4 is the obvious mechanism, and it inherits that rule's weakness (§10, *Same-recipient replay*) — a monotonic rotation counter is likely the safer construction.
765+- **Contacts who miss the announcement.** A contact offline past the 30-day TTL (§9) never receives the rotation and is left holding a dead key. Re-announcing on reconnect, or letting a client ask a peer to re-send its current identity, would need to be specified.
766+- **Revocation vs. rotation.** These are different operations. Rotation says "use this key from now on" and assumes the old key is still under the owner's control; revocation says "the old key is compromised — distrust it", and an attacker holding the compromised key can forge exactly the rotation message that would hijack the identity. A rotation announcement therefore MUST NOT be treated as a compromise recovery mechanism. Recovering from a stolen key needs a separate design (an offline recovery key, or out-of-band re-verification) and is out of scope here.
767+- **No retroactive protection.** Rotating does not protect past traffic. Messages already sent to the old key remain decryptable by whoever holds it, exactly as §10, *No forward secrecy* describes.
apple/SkrepkaApp/Core.swift+23−16
@@ -6,6 +6,15 @@ import SkrepkaShared
66/// each effect (HTTP, key-value, timer, render) and resolves it back into the core.
77@MainActor
88final class Core: ObservableObject {
9+ /// One core per process, reachable outside the view tree.
10+ ///
11+ /// `SkrepkaApp` holds this in a `@StateObject`, but the background-refresh handler runs
12+ /// with no view installed — and a `@StateObject` read from there hands back a *fresh*
13+ /// instance every time. That would mean a second `CoreFFI` with its own identity, its own
14+ /// kv state and its own poll loop, writing over the real one's files and rendering into
15+ /// nothing. The state machine is a singleton in fact; make it one in the type.
16+ static let shared = Core()
17+
918 @Published var view: ViewModel
1019
1120 /// A Keychain failure never reaches the core — without an identity there is no
@@ -16,17 +25,18 @@ final class Core: ObservableObject {
1625 private let core = CoreFFI()
1726 private let store = KvStore()
1827
19− init() {
20− // swiftlint:disable:next force_try
21− self.view = try! .bincodeDeserialize(input: [UInt8](core.view()))
28+ private init() {
29+ // The FFI's guard returns empty bytes when the core panics; force-try
30+ // on empty bytes crashes the app. Fall back to a default ViewModel instead.
31+ self.view = (try? ViewModel.bincodeDeserialize(input: [UInt8](core.view()))) ?? ViewModel()
2232 bootIdentity()
2333 }
2434
2535 // MARK: - Event/effect loop
2636
2737 func update(_ event: Event) {
28− // swiftlint:disable:next force_try
29− let effects = [UInt8](core.update(data: Data(try! event.bincodeSerialize())))
38+ guard let eventData = try? event.bincodeSerialize() else { return }
39+ let effects = [UInt8](core.update(data: Data(eventData)))
3040 dispatch(effects)
3141 }
3242
@@ -36,8 +46,7 @@ final class Core: ObservableObject {
3646 }
3747
3848 private func dispatch(_ effects: [UInt8]) {
39− // swiftlint:disable:next force_try
40− let requests = try! Requests.bincodeDeserialize(input: effects).value
49+ guard let requests = try? Requests.bincodeDeserialize(input: effects).value else { return }
4150 for request in requests {
4251 process(request)
4352 }
@@ -47,29 +56,27 @@ final class Core: ObservableObject {
4756 let id = request.id
4857 switch request.effect {
4958 case .render:
50− // swiftlint:disable:next force_try
51− self.view = try! .bincodeDeserialize(input: [UInt8](core.view()))
59+ self.view = (try? ViewModel.bincodeDeserialize(input: [UInt8](core.view()))) ?? self.view
5260
5361 case .http(let req):
5462 Task { [weak self] in
5563 let result = await Http.perform(req)
56− // swiftlint:disable:next force_try
57− self?.resolve(id, try! result.bincodeSerialize())
64+ guard let output = try? result.bincodeSerialize() else { return }
65+ self?.resolve(id, output)
5866 }
5967
6068 case .keyValue(let op):
6169 // The file I/O runs on the store's own serial queue; hop the result back to
6270 // the main actor, because the core is single-threaded and `.render` publishes.
6371 store.handle(op) { [weak self] result in
64− // swiftlint:disable:next force_try
65− let output = try! result.bincodeSerialize()
72+ guard let output = try? result.bincodeSerialize() else { return }
6673 Task { @MainActor in self?.resolve(id, output) }
6774 }
6875
6976 case .time(let req):
7077 Time.handle(req) { [weak self] response in
71− // swiftlint:disable:next force_try
72− self?.resolve(id, try! response.bincodeSerialize())
78+ guard let output = try? response.bincodeSerialize() else { return }
79+ self?.resolve(id, output)
7380 }
7481 }
7582 }
@@ -88,4 +95,4 @@ final class Core: ObservableObject {
8895 identityError = error.message
8996 }
9097 }
91−}
98+}
apple/SkrepkaApp/Effects.swift+98−3
@@ -5,11 +5,100 @@ import Skrepka
55
66// MARK: - HTTP
77
8+/// Hard cap on any HTTP response body we will buffer. A hostile relay
9+/// can answer any endpoint with a multi-gigabyte body; without this cap
10+/// `URLSession.data(for:)` would OOM the app before the core's own
11+/// `MAX_POLL_RESPONSE_BYTES` check (which runs on the wrong side of the
12+/// FFI boundary to prevent the allocation) ever fires.
13+private let maxResponseBytes = 64 * 1024 * 1024 // 64 MiB
14+
15+/// The one session delegate, handling two defenses against an untrusted relay.
16+///
17+/// **Redirect cancellation.** URLSession replays the original request's headers onto a
18+/// redirect target, including `Authorization: Bearer <session_token>`. A hostile (or
19+/// compromised) relay could answer `/poll` or `/messages` with a 302 to a host it chooses
20+/// and harvest the bearer token from the request we would dutifully re-send there. Sessions
21+/// are bound to a single relay by design (§6), so a cross-host redirect is never legitimate
22+/// — refusing it costs nothing and closes the token-exfiltration path. Same-host redirects
23+/// (e.g. HTTP → HTTPS upgrade on the same host) are allowed; the Authorization header stays
24+/// within the relay's own host. Returning `nil` from the completion handler does not error
25+/// the task: it stops the redirect and hands the 3xx response itself back to the caller,
26+/// which the core sees as a non-2xx status and treats as a failed request.
27+///
28+/// **Response size limiting.** As body chunks arrive we accumulate the byte count per task
29+/// and cancel the task the moment it crosses `maxResponseBytes`, so a multi-gigabyte body
30+/// never fully materializes in memory. Cancelling surfaces to the caller as a `URLError`
31+/// with code `.cancelled`, which `Http.perform` maps to a transport error.
32+private final class HttpSessionDelegate: NSObject, URLSessionTaskDelegate, URLSessionDataDelegate {
33+ let maxResponseBytes: Int
34+
35+ /// Per-task accumulated byte counts. The delegate is shared across every concurrent
36+ /// request, so a single shared counter would conflate their bodies — key by task instead.
37+ /// Guarded by `lock` because delegate callbacks arrive on the session's own (non-main)
38+ /// queue and may interleave across tasks.
39+ private var taskSizes: [URLSessionTask: Int] = [:]
40+ private let lock = NSLock()
41+
42+ init(maxResponseBytes: Int) {
43+ self.maxResponseBytes = maxResponseBytes
44+ }
45+
46+ func urlSession(
47+ _ session: URLSession,
48+ task: URLSessionTask,
49+ willPerformHTTPRedirection response: HTTPURLResponse,
50+ newRequest request: URLRequest,
51+ completionHandler: @escaping (URLRequest?) -> Void
52+ ) {
53+ // Allow same-host redirects (e.g. HTTP → HTTPS upgrade on the same host).
54+ // Cancel cross-host redirects — a hostile relay could redirect to an
55+ // attacker-controlled host and harvest the Authorization header.
56+ if let originalURL = task.currentRequest?.url,
57+ let redirectHost = request.url?.host?.lowercased(),
58+ let originalHost = originalURL.host?.lowercased(),
59+ redirectHost == originalHost {
60+ completionHandler(request)
61+ } else {
62+ completionHandler(nil)
63+ }
64+ }
65+
66+ func urlSession(
67+ _ session: URLSession,
68+ dataTask: URLSessionDataTask,
69+ didReceive data: Data
70+ ) {
71+ lock.lock()
72+ let total = (taskSizes[dataTask] ?? 0) + data.count
73+ taskSizes[dataTask] = total
74+ let exceeded = total > maxResponseBytes
75+ lock.unlock()
76+ if exceeded {
77+ dataTask.cancel()
78+ }
79+ }
80+
81+ func urlSession(
82+ _ session: URLSession,
83+ task: URLSessionTask,
84+ didCompleteWithError error: Error?
85+ ) {
86+ lock.lock()
87+ taskSizes.removeValue(forKey: task)
88+ lock.unlock()
89+ }
90+}
91+
892enum Http {
93+ /// Strongly held by `session` for the app's lifetime — the session is never invalidated,
94+ /// so the delegate is never released. That is the intended shape here, not a leak.
95+ private static let httpDelegate = HttpSessionDelegate(maxResponseBytes: maxResponseBytes)
96+
997 /// A private, ephemeral session. `URLSession.shared` would hand every relay a
1098 /// persistent cookie jar and an on-disk response cache — a relay is untrusted
1199 /// infrastructure and must not be able to pin a stable identifier on the client
12− /// or leave polled ciphertext lying around on disk.
100+ /// or leave polled ciphertext lying around on disk. It would also follow redirects,
101+ /// which is what `HttpSessionDelegate` is here to prevent.
13102 private static let session: URLSession = {
14103 let config = URLSessionConfiguration.ephemeral
15104 config.httpCookieAcceptPolicy = .never
@@ -19,11 +108,13 @@ enum Http {
19108 config.requestCachePolicy = .reloadIgnoringLocalAndRemoteCacheData
20109 config.timeoutIntervalForRequest = 70 // server long-polls for ~25s
21110 config.tlsMinimumSupportedProtocolVersion = .TLSv12
22− return URLSession(configuration: config)
111+ return URLSession(configuration: config, delegate: httpDelegate, delegateQueue: nil)
23112 }()
24113
25114 static func perform(_ req: HttpRequest) async -> HttpResult {
26− guard let url = URL(string: req.url) else {
115+ guard let url = URL(string: req.url),
116+ let scheme = url.scheme,
117+ scheme == "http" || scheme == "https" else {
27118 return .err(.url(req.url))
28119 }
29120 var request = URLRequest(url: url)
@@ -43,6 +134,10 @@ enum Http {
43134 headers: headers(of: http),
44135 body: [UInt8](data)
45136 ))
137+ } catch let error as URLError where error.code == .cancelled {
138+ // The size-limit delegate cancels the task when the body exceeds the cap.
139+ // Treat it as a transport error so the core backs off and retries.
140+ return .err(.io("response body exceeded \(maxResponseBytes) bytes"))
46141 } catch let error as URLError where error.code == .timedOut {
47142 return .err(.timeout)
48143 } catch {
apple/SkrepkaApp/Forms.swift+9
@@ -158,6 +158,15 @@ struct EditProfileView: View {
158158 }
159159 Section("Name") { TextField("Display name", text: $name) }
160160 Section("Bio") { TextField("About you", text: $bio, axis: .vertical) }
161+ // SaveProfile sets model.error on validation failures ("display name
162+ // too long", "bio too long", "photo too large") but leaves the page
163+ // open. Without displaying it the user taps Save, nothing happens, and
164+ // they have no idea why.
165+ if !core.view.error.isEmpty {
166+ Section {
167+ Text(core.view.error).foregroundColor(.red)
168+ }
169+ }
161170 }
162171 .navigationTitle("Edit profile")
163172 .toolbar {
apple/SkrepkaApp/PhotoPicker.swift+23−1
@@ -62,7 +62,29 @@ struct PhotoPicker: UIViewControllerRepresentable {
6262 guard let source = CGImageSourceCreateWithURL(url as CFURL, nil),
6363 let thumb = CGImageSourceCreateThumbnailAtIndex(source, 0, options as CFDictionary)
6464 else { return nil }
65− return UIImage(cgImage: thumb).jpegData(compressionQuality: 0.7)?.base64EncodedString()
65+ let image = UIImage(cgImage: thumb)
66+ // Reduce quality until the base64 fits within the protocol cap (MAX_PHOTO_LEN,
67+ // 64 KiB). A high-detail 256px frame can exceed the cap even at q0.7; without
68+ // this loop `SaveProfile` rejects the whole profile with no recourse for the user.
69+ let maxBase64Len = 64 * 1024
70+ var quality: CGFloat = 0.7
71+ while quality > 0.1 {
72+ if let jpegData = image.jpegData(compressionQuality: quality) {
73+ let base64 = jpegData.base64EncodedString()
74+ if base64.count <= maxBase64Len {
75+ return base64
76+ }
77+ }
78+ quality -= 0.1
79+ }
80+ // Last resort: the smallest quality that still produces something.
81+ // If even this exceeds the cap, return nil so onCancel fires rather
82+ // than sending an oversized payload the core will reject.
83+ let lastResort = image.jpegData(compressionQuality: 0.1)?.base64EncodedString()
84+ if let result = lastResort, result.count <= maxBase64Len {
85+ return result
86+ }
87+ return nil
6688 }
6789 }
6890}
apple/SkrepkaApp/QRView.swift+36−2
@@ -21,6 +21,9 @@ func qrImage(_ string: String) -> UIImage? {
2121/// A QR code carries whatever its author put there. Strip a leading scheme so a share
2222/// link (`skrepka:<key>`, `https://…/<key>`) yields the bare key the core will accept,
2323/// and so the pubkey field never silently fills with an unrelated URL.
24+// NOTE: This URL scheme stripping is arguably business logic that belongs in
25+// the core (see AGENTS.md). It is kept here for now because moving it requires
26+// an FFI change. The core's `try_parse_pubkey` validates the result regardless.
2427func scannedKeyPayload(_ raw: String) -> String {
2528 var value = raw.trimmingCharacters(in: .whitespacesAndNewlines)
2629 let schemes = ["skrepka://", "skrepka:", "https://", "http://"]
@@ -75,6 +78,24 @@ final class ScannerVC: UIViewController {
7578 override func viewDidLoad() {
7679 super.viewDidLoad()
7780 view.backgroundColor = .black
81+
82+ let status = AVCaptureDevice.authorizationStatus(for: .video)
83+ switch status {
84+ case .authorized:
85+ startSession()
86+ case .notDetermined:
87+ AVCaptureDevice.requestAccess(for: .video) { [weak self] granted in
88+ DispatchQueue.main.async {
89+ if granted { self?.startSession() }
90+ else { self?.showPermissionDenied() }
91+ }
92+ }
93+ default:
94+ showPermissionDenied()
95+ }
96+ }
97+
98+ private func startSession() {
7899 guard let device = AVCaptureDevice.default(for: .video),
79100 let input = try? AVCaptureDeviceInput(device: device),
80101 session.canAddInput(input) else { return }
@@ -93,6 +114,19 @@ final class ScannerVC: UIViewController {
93114 previewLayer = preview
94115 }
95116
117+ private func showPermissionDenied() {
118+ let label = UILabel()
119+ label.text = "Camera permission required"
120+ label.textAlignment = .center
121+ label.textColor = .secondaryLabel
122+ view.addSubview(label)
123+ label.translatesAutoresizingMaskIntoConstraints = false
124+ NSLayoutConstraint.activate([
125+ label.centerXAnchor.constraint(equalTo: view.centerXAnchor),
126+ label.centerYAnchor.constraint(equalTo: view.centerYAnchor),
127+ ])
128+ }
129+
96130 override func viewDidLayoutSubviews() {
97131 super.viewDidLayoutSubviews()
98132 previewLayer?.frame = view.bounds
@@ -100,7 +134,7 @@ final class ScannerVC: UIViewController {
100134
101135 override func viewWillAppear(_ animated: Bool) {
102136 super.viewWillAppear(animated)
103− if !session.isRunning {
137+ if !session.isRunning && !session.inputs.isEmpty {
104138 DispatchQueue.global(qos: .userInitiated).async { self.session.startRunning() }
105139 }
106140 }
@@ -112,4 +146,4 @@ final class ScannerVC: UIViewController {
112146 DispatchQueue.global(qos: .userInitiated).async { self.session.stopRunning() }
113147 }
114148 }
115−}
149+}
apple/SkrepkaApp/SkrepkaApp.swift+152−6
@@ -1,20 +1,166 @@
1+import BackgroundTasks
12import SwiftUI
3+import UIKit
24
35@main
46struct SkrepkaApp: App {
5− @StateObject private var core = Core()
7+ /// Must stay in step with `BGTaskSchedulerPermittedIdentifiers` in `project.yml`.
8+ /// An identifier the Info.plist does not list is refused by `submit` — quietly, and
9+ /// forever: the task simply never runs, and nothing at runtime says why.
10+ static let refreshTaskId = "lol.skrepka.SkrepkaApp.fetch"
11+
12+ @StateObject private var core = Core.shared
613 @Environment(\.scenePhase) private var scenePhase
714
15+ init() {
16+ // Launch handlers must all be registered before the app finishes launching, so this
17+ // cannot wait for a view to appear. The handler is called on a background queue;
18+ // `BackgroundRefresh` hops to the main actor, where the core lives.
19+ BGTaskScheduler.shared.register(
20+ forTaskWithIdentifier: Self.refreshTaskId,
21+ using: nil
22+ ) { task in
23+ guard let task = task as? BGAppRefreshTask else {
24+ task.setTaskCompleted(success: false)
25+ return
26+ }
27+ BackgroundRefresh.handle(task)
28+ }
29+ }
30+
831 var body: some Scene {
932 WindowGroup {
1033 RootView(core: core)
1134 .onChange(of: scenePhase) { _, phase in
12− // Backgrounding kills the long-poll socket and the app stops running,
13− // so on return the core would otherwise sit out its whole backoff
14− // (up to 30s) before noticing. Reconnect immediately instead.
15− guard phase == .active, core.view.hasIdentity else { return }
16− core.update(.connect)
35+ switch phase {
36+ case .active:
37+ // Backgrounding kills the long-poll socket and the app stops running,
38+ // so on return the core would otherwise sit out its whole backoff
39+ // (up to 30s) before noticing. Reconnect immediately instead.
40+ guard core.view.hasIdentity else { return }
41+ core.update(.connect)
42+ case .background:
43+ // Ask for a refresh pass on the way out — that is the only window in
44+ // which a pending request is any use, and the system replaces the
45+ // previous request for this identifier rather than queueing another.
46+ BackgroundRefresh.schedule()
47+ default:
48+ break
49+ }
1750 }
1851 }
1952 }
2053}
54+
55+/// Opportunistic catch-up while the app is backgrounded.
56+///
57+/// This does **not** keep the poll loop alive — iOS grants no such thing to a non-VoIP app.
58+/// `BGAppRefreshTask` wakes us for a few tens of seconds at times the system chooses from the
59+/// user's launch habits (`earliestBeginDate` is a floor, not a schedule: a pass may be hours
60+/// late, or never come at all if the app was force-quit), and suspends us again as soon as we
61+/// report completion. So this drains whatever the relay is already holding, on the system's
62+/// terms. Prompt delivery would need a push, and the protocol has no APNs surface at all.
63+@MainActor
64+enum BackgroundRefresh {
65+ /// The system coalesces and defers as it sees fit; asking for less does not make it come
66+ /// sooner, it only tells the scheduler we have nothing useful to do before then.
67+ private static let earliestBegin: TimeInterval = 30 * 60
68+
69+ /// The grant is around 30s, and an app that habitually burns all of it — or worse, gets
70+ /// expired — is scheduled less often. Leave headroom.
71+ private static let budget: TimeInterval = 25
72+
73+ /// How long to hold the poll open once we are online. The relay answers a poll at once
74+ /// when it is holding mail and otherwise long-polls ~25s, so a few seconds of silence
75+ /// already *is* the answer "nothing waiting" — there is nothing to be gained by waiting
76+ /// out the long poll, and the budget is better left unspent.
77+ private static let idleGrace: TimeInterval = 5
78+
79+ static func schedule() {
80+ let request = BGAppRefreshTaskRequest(identifier: SkrepkaApp.refreshTaskId)
81+ request.earliestBeginDate = Date(timeIntervalSinceNow: earliestBegin)
82+ // Throws on `.notPermitted` (the identifier is missing from the Info.plist — a
83+ // packaging bug, see `SkrepkaApp.refreshTaskId`) and on `.tooManyPendingTaskRequests`.
84+ // Neither is actionable from here, and neither is worth failing a scene transition.
85+ try? BGTaskScheduler.shared.submit(request)
86+ }
87+
88+ nonisolated static func handle(_ task: BGAppRefreshTask) {
89+ let work = Task { @MainActor in await run(task) }
90+ // Expiry only *cancels*; `run` owns the single `setTaskCompleted` call.
91+ // The handler is assigned immediately after Task creation — the window
92+ // where the task is alive but unhandled is one assignment, and the system
93+ // does not expire a task in its first few milliseconds.
94+ task.expirationHandler = { work.cancel() }
95+ }
96+
97+ private static func run(_ task: BGAppRefreshTask) async {
98+ // Before anything that can fail or be cut short: we still want the next pass.
99+ schedule()
100+
101+ // Every kv file is written `completeUnlessOpen`, so while the device is
102+ // locked an *existing* one cannot be opened and every read fails. The
103+ // core now distinguishes a failed read from an absent key (`parse_kv`
104+ // returns `Err` vs `Ok(None)`), so it surfaces a storage error instead
105+ // of silently loading an empty model. But the guard is still the right
106+ // call: a locked device means the core would come up with errors on
107+ // every key, no contacts, and no history — and even if it doesn't
108+ // overwrite, it would poll into an empty conversation list and ack
109+ // messages the user can't see. Locked means we must not run at all.
110+ guard UIApplication.shared.isProtectedDataAvailable else {
111+ task.setTaskCompleted(success: false)
112+ return
113+ }
114+
115+ let deadline = Date(timeIntervalSinceNow: budget)
116+ let core = Core.shared
117+
118+ // Reading `Core.shared` is what boots the core when the system launched us straight
119+ // into the background. Startup is asynchronous — the identity, then five kv loads —
120+ // and the core fires its own `Connect` once the settings land. It must be left to do
121+ // that: nudging it beforehand would authenticate against the *default* relay, because
122+ // the configured URL has not been read off disk yet.
123+ guard await settle(by: deadline, until: { core.view.hasIdentity }) else {
124+ task.setTaskCompleted(success: false)
125+ return
126+ }
127+
128+ // Still offline once startup has had its chance: either the core is idle, or it was
129+ // suspended part-way through a backoff whose timer will not come due for another 30s.
130+ // A `Connect` collapses that wait. (It is a no-op when the core already believes it
131+ // is online — there, a stale poll is the watchdog's problem, not ours.)
132+ let startupDeadline = min(deadline, Date(timeIntervalSinceNow: 3))
133+ let connecting = await settle(by: startupDeadline, until: {
134+ core.view.connStatus != "offline"
135+ })
136+ if !connecting {
137+ core.update(.connect)
138+ }
139+
140+ // Online is the token in hand and the poll issued. Anything the relay was holding
141+ // comes back on that first page.
142+ guard await settle(by: deadline, until: { core.view.connStatus == "online" }) else {
143+ task.setTaskCompleted(success: false)
144+ return
145+ }
146+ try? await Task.sleep(for: .seconds(idleGrace))
147+
148+ task.setTaskCompleted(success: !Task.isCancelled)
149+ }
150+
151+ /// Waits for a condition on the view, or for the deadline (or expiry) to overtake it.
152+ ///
153+ /// The core has nothing to await — it publishes a `ViewModel` and that is the whole of
154+ /// its output — so the shell watches that. A 500ms tick across the handful of transitions
155+ /// this cares about is cheaper than threading a Combine subscription through an actor hop.
156+ /// The previous 200ms interval was unnecessarily aggressive for a background task with a
157+ /// 25s budget that only cares about a few state transitions.
158+ private static func settle(by deadline: Date, until condition: () -> Bool) async -> Bool {
159+ while !condition() {
160+ guard !Task.isCancelled, Date() < deadline else { return false }
161+ // Cancellation makes this throw at once; the guard above is what breaks the loop.
162+ try? await Task.sleep(for: .milliseconds(500))
163+ }
164+ return true
165+ }
166+}
apple/SkrepkaApp/Views.swift+68−13
@@ -161,6 +161,34 @@ struct BlockToggle: View {
161161 }
162162}
163163
164+/// Permanently removes a contact, their conversation history, and any queued
165+/// outbox items for them. Unlike blocking (which silences but keeps the entry),
166+/// deletion is irreversible — so a confirmation prompt gates the action.
167+struct DeleteContactButton: View {
168+ @ObservedObject var core: Core
169+ let peer: String
170+
171+ @State private var confirming = false
172+
173+ var body: some View {
174+ Button(role: .destructive) {
175+ confirming = true
176+ } label: {
177+ Label("Delete contact", systemImage: "trash")
178+ }
179+ .confirmationDialog(
180+ "Delete this contact? Their message history will be removed and cannot be recovered.",
181+ isPresented: $confirming,
182+ titleVisibility: .visible
183+ ) {
184+ Button("Delete", role: .destructive) {
185+ core.update(.deleteContact(peer: peer))
186+ }
187+ Button("Cancel", role: .cancel) {}
188+ }
189+ }
190+}
191+
164192struct ConversationsView: View {
165193 @ObservedObject var core: Core
166194
@@ -218,6 +246,7 @@ struct ConversationsView: View {
218246 }
219247 .contextMenu {
220248 BlockToggle(core: core, peer: contact.pubkey, blocked: contact.blocked)
249+ DeleteContactButton(core: core, peer: contact.pubkey)
221250 }
222251 }
223252}
@@ -259,6 +288,7 @@ struct ChatView: View {
259288 peer: core.view.activePeer,
260289 blocked: core.view.activePeerBlocked
261290 )
291+ DeleteContactButton(core: core, peer: core.view.activePeer)
262292 } label: {
263293 Image(systemName: "ellipsis.circle")
264294 }
@@ -289,20 +319,45 @@ struct ChatView: View {
289319 }
290320
291321 private var composer: some View {
292− HStack(spacing: 8) {
293− TextField("Message", text: $draft, axis: .vertical)
294− .textFieldStyle(.roundedBorder)
295− .lineLimit(1...4)
296− Button {
297− let text = draft.trimmingCharacters(in: .whitespacesAndNewlines)
298− guard !text.isEmpty else { return }
299− core.update(.composeChanged(text))
300− core.update(.sendText)
301− draft = ""
302− } label: {
303− Image(systemName: "arrow.up.circle.fill").font(.title)
322+ VStack(spacing: 0) {
323+ // Errors from send_text ("message too long", "contact list is full",
324+ // "gave up sending …", "invalid key") are set on model.error and rendered
325+ // into view.error, but without this the chat page swallowed them — the
326+ // user tapped send, it failed, and they saw nothing.
327+ if !core.view.error.isEmpty {
328+ Text(core.view.error)
329+ .font(.caption)
330+ .foregroundColor(.red)
331+ .frame(maxWidth: .infinity, alignment: .leading)
332+ .padding(.horizontal)
333+ .padding(.top, 4)
334+ }
335+ HStack(spacing: 8) {
336+ TextField("Message", text: $draft, axis: .vertical)
337+ .textFieldStyle(.roundedBorder)
338+ .lineLimit(1...4)
339+ .disabled(core.view.activePeerBlocked)
340+ Button {
341+ let text = draft.trimmingCharacters(in: .whitespacesAndNewlines)
342+ guard !text.isEmpty else { return }
343+ core.update(.composeChanged(text))
344+ core.update(.sendText)
345+ // Only clear the local draft when the core actually accepted the
346+ // message. send_text refuses (and sets error) on a blocked peer,
347+ // an oversized body, or a full contact list — and it preserves
348+ // model.compose on those paths so the user's text is not lost.
349+ // Clearing draft unconditionally wiped it from the UI even though
350+ // the core kept it, so the failure was both invisible and
351+ // destructive: the text was gone with no explanation.
352+ if core.view.error.isEmpty {
353+ draft = ""
354+ }
355+ } label: {
356+ Image(systemName: "arrow.up.circle.fill").font(.title)
357+ }
358+ .disabled(draft.trimmingCharacters(in: .whitespacesAndNewlines).isEmpty
359+ || core.view.activePeerBlocked)
304360 }
305− .disabled(draft.trimmingCharacters(in: .whitespacesAndNewlines).isEmpty)
306361 }
307362 .padding(.horizontal).padding(.vertical, 8)
308363 .background(.bar)
apple/project.yml+8
@@ -43,6 +43,14 @@ targets:
4343 - UIInterfaceOrientationPortrait
4444 NSCameraUsageDescription: Scan a contact's QR code to add them.
4545 NSPhotoLibraryUsageDescription: Choose a photo for your profile.
46+ # Opportunistic catch-up polls while backgrounded (BGAppRefreshTask). `fetch` is the
47+ # mode BGAppRefreshTask runs under; `processing` is for long deferrable work and is
48+ # not what this is. The scheduler refuses — silently — any identifier not listed in
49+ # BGTaskSchedulerPermittedIdentifiers, so it must match `SkrepkaApp.refreshTaskId`.
50+ UIBackgroundModes:
51+ - fetch
52+ BGTaskSchedulerPermittedIdentifiers:
53+ - lol.skrepka.SkrepkaApp.fetch
4654 # Declared so App Store Connect stops asking on every upload.
4755 ITSAppUsesNonExemptEncryption: false
4856 # Relays must be reachable over TLS. The only cleartext exception is a
core/Cargo.toml+1
@@ -45,6 +45,7 @@ zstd.workspace = true
4545rand_core.workspace = true
4646uuid.workspace = true
4747hex.workspace = true
48+base64.workspace = true
4849zeroize.workspace = true
4950url.workspace = true
5051
core/src/app.rs+2737−245
@@ -5,9 +5,13 @@
55//! key-value storage, a timer, and (natively, fed back as events) the Keychain,
66//! QR scanning, photo picking, and clipboard.
77
8−use std::collections::{BTreeMap, VecDeque};
8+use std::collections::{BTreeMap, HashMap, HashSet, VecDeque};
9+use std::sync::Arc;
910use std::time::{Duration, SystemTime, UNIX_EPOCH};
1011
12+use base64::prelude::*;
13+use base64::Engine;
14+
1115use crux_core::{
1216 macros::effect,
1317 render::{render, RenderOperation},
@@ -57,6 +61,24 @@ const MAX_CONTACTS: usize = 500;
5761/// the budget is dropped exactly like an undecryptable blob would be.
5862const MAX_POLL_TOTAL_BYTES: usize = 64 * 1024 * 1024;
5963
64+/// Cap on the number of events we will attempt to decrypt out of a single poll
65+/// page, independent of the byte budget. Minimum-size blobs (173 bytes decoded)
66+/// would otherwise permit ~388K events within the 64 MiB byte budget, each
67+/// costing a full scalar mult + SHA-512 + AEAD pass — enough to freeze the app
68+/// for tens of seconds per poll. An honest relay caps at 50 events
69+/// (`maxPollEvents`); this is a hostile-relay bound. Set above `MAX_ACK_IDS`
70+/// (1024) so a legitimate large page from one sender still fully processes.
71+const MAX_POLL_EVENTS: usize = 2000;
72+
73+/// Upper bound on a poll response body we will buffer and parse, in bytes.
74+///
75+/// Before the per-blob byte/count budgets in `ingest_poll` ever run, the client
76+/// reads the entire response body into a `Vec<u8>` and deserializes it. A
77+/// multi-gigabyte response from a hostile relay would OOM the app before
78+/// `ingest_poll`'s defenses are consulted. This cap (generously above what 50
79+/// max-size blobs + JSON envelope could cost) bounds the allocation.
80+const MAX_POLL_RESPONSE_BYTES: usize = 64 * 1024 * 1024;
81+
6082/// How long a poll may stay in flight before we assume the shell lost it.
6183///
6284/// `polling` gates the whole long-poll loop, and it is only cleared by a
@@ -72,16 +94,71 @@ const MAX_POLL_TOTAL_BYTES: usize = 64 * 1024 * 1024;
7294/// relay, so leave the margin.
7395const POLL_WATCHDOG_MS: u64 = 90_000;
7496
97+/// How long a send may stay in flight before we assume the shell lost it.
98+///
99+/// `flushing` gates the whole send loop, and it is only cleared by a
100+/// `SendResult`. If the shell ever drops the HTTP effect (a cancelled task, a
101+/// backgrounded app, a bug), `flushing` stays `true` and the outbox is
102+/// permanently stuck — new messages queue up but never send. The watchdog
103+/// releases the guard so the next `StartFlush` can retry.
104+///
105+/// Kept above the shell's 70 s HTTP timeout for the same reason as
106+/// `POLL_WATCHDOG_MS`: a misfire on a merely slow send is survivable (the late
107+/// `SendResult` finds `in_flight` already cleared and pops nothing), but each
108+/// one costs a redundant request.
109+const FLUSH_WATCHDOG_MS: u64 = 90_000;
110+
111+/// How long an auth round-trip may stay in flight before we assume the
112+/// shell lost it. Same rationale as `POLL_WATCHDOG_MS`: `authenticating`
113+/// gates the whole auth flow, and without a watchdog a dropped effect
114+/// leaves it stuck forever. Kept above the 70 s shell HTTP timeout.
115+const AUTH_WATCHDOG_MS: u64 = 90_000;
116+
117+/// Messages per `/messages` request.
118+///
119+/// The relay rejects a longer batch outright (`413 batch_too_large`,
120+/// PROTOCOL.md §7), so this is a hard ceiling, not a tuning knob.
121+const MAX_SEND_BATCH: usize = 100;
122+
123+/// ...and a byte ceiling on the same batch, counted in hex characters — i.e. in
124+/// the units the request body is actually built from.
125+///
126+/// The count limit alone is not enough: a hundred profile broadcasts each
127+/// carrying a 64 KiB photo would build a request far past the 16 MiB body cap a
128+/// relay has by default (`--http-max-body-bytes`, PROTOCOL.md §7), and the whole
129+/// batch would come back `413` — which we read as a transient failure and retry,
130+/// forever. Bounding the body here keeps the batch inside what any conforming
131+/// relay accepts. A single item over the budget still goes out alone: it is the
132+/// relay's job to reject it, and its rejection is per-message and permanent.
133+const MAX_SEND_BATCH_BYTES: usize = 4 * 1024 * 1024;
134+
135+/// Ceiling on a `Retry-After` we will honour from a relay.
136+///
137+/// The header is a number the relay chooses and we obey, so without a cap a
138+/// single `Retry-After: 999999999` — from a hostile relay, or a merely broken
139+/// one — parks the outbox for thirty years with nothing on screen to say why.
140+/// Five minutes is longer than any real rate-limit window and still recovers on
141+/// its own.
142+const MAX_RETRY_AFTER_MS: u64 = 5 * 60 * 1000;
143+
75144// kv keys
76145const K_SETTINGS: &str = "settings";
77146const K_PROFILE: &str = "profile";
78147const K_CONTACTS: &str = "contacts";
79148const K_CURSOR: &str = "cursor";
80149const K_OUTBOX: &str = "outbox";
150+const K_SEEN_IDS: &str = "seen_ids";
81151fn k_messages(peer: &str) -> String {
82152 format!("messages:{peer}")
83153}
84154
155+/// N7: Cap on the per-peer `seen_ids` dedup set. Without a cap the set grows
156+/// without bound — a peer who sends thousands of messages accumulates
157+/// thousands of IDs, and the `seen_ids` kv blob is rewritten in full on every
158+/// incoming message. Kept well above `MAX_MESSAGES_PER_PEER` (1000) so a
159+/// trim-and-replay within the conversation window still hits the set.
160+const MAX_SEEN_IDS_PER_PEER: usize = 2000;
161+
85162// ---------------------------------------------------------------------------
86163// Effect
87164// ---------------------------------------------------------------------------
@@ -119,6 +196,10 @@ pub enum Event {
119196 SendText,
120197 AddContact { input: String, nickname: String },
121198 SetBlocked { peer: String, blocked: bool },
199+ /// Forget a peer entirely: the contact, the conversation, and anything still
200+ /// queued for them. Blocking only silences a peer; the entry stays in the
201+ /// list forever, and there was no way to be rid of it.
202+ DeleteContact { peer: String },
122203 SaveProfile {
123204 display_name: String,
124205 bio: String,
@@ -145,6 +226,9 @@ pub enum Event {
145226 LoadedOutbox(#[facet(opaque)] KvData),
146227 #[serde(skip)]
147228 #[facet(skip)]
229+ LoadedSeenIds(#[facet(opaque)] KvData),
230+ #[serde(skip)]
231+ #[facet(skip)]
148232 LoadedMessages(String, #[facet(opaque)] KvData),
149233 #[serde(skip)]
150234 #[facet(skip)]
@@ -178,6 +262,17 @@ pub enum Event {
178262 #[serde(skip)]
179263 #[facet(skip)]
180264 StartFlush,
265+ /// Fires `FLUSH_WATCHDOG_MS` after generation `n`'s flush is issued; a no-op
266+ /// unless that exact send is somehow still in flight — same pattern as
267+ /// `PollWatchdog`.
268+ #[serde(skip)]
269+ #[facet(skip)]
270+ FlushWatchdog(u64),
271+ /// Fires `AUTH_WATCHDOG_MS` after generation `n`'s auth round-trip is
272+ /// issued; a no-op unless that exact auth is somehow still in flight.
273+ #[serde(skip)]
274+ #[facet(skip)]
275+ AuthWatchdog(u64),
181276 #[serde(skip)]
182277 #[facet(skip)]
183278 ChallengeResult(u64, #[facet(opaque)] HttpResult),
@@ -189,7 +284,7 @@ pub enum Event {
189284 PollResult(u64, #[facet(opaque)] HttpResult),
190285 #[serde(skip)]
191286 #[facet(skip)]
192− SendResult(#[facet(opaque)] HttpResult),
287+ SendResult(u64, #[facet(opaque)] HttpResult),
193288}
194289
195290// ---------------------------------------------------------------------------
@@ -215,9 +310,24 @@ pub enum Page {
215310 EditProfile,
216311}
217312
218−/// The five kv keys loaded at startup (`settings`, `profile`, `contacts`,
219−/// `cursor`, `outbox`). `Connect` waits for all of them.
220−const STARTUP_LOADS: u8 = 5;
313+/// The six kv keys loaded at startup (`settings`, `profile`, `contacts`,
314+/// `cursor`, `outbox`, `seen_ids`). `Connect` waits for all of them.
315+const STARTUP_LOADS: u8 = 6;
316+
317+/// The batch a live `/messages` request is carrying: the first `count` items of
318+/// the outbox, all bound for `recipient`.
319+///
320+/// `SendResult` needs all three. The count is what it pops on success and what it
321+/// charges a retry against on a transient failure; the recipient is what tells
322+/// `SetBlocked` and `DeleteContact` whether the items they are about to remove
323+/// are the very ones this send is going to pop; and `bytes` — the size of the
324+/// body we actually built — is what a `413` halves to find a batch this relay
325+/// will accept (see `Model::send_batch_budget`).
326+struct InFlight {
327+ recipient: String,
328+ count: usize,
329+ bytes: usize,
330+}
221331
222332pub struct Model {
223333 /// Zeroized on drop: this is the Ed25519 seed, the one secret whose leak
@@ -228,11 +338,23 @@ pub struct Model {
228338 profile: OwnProfile,
229339 contacts: BTreeMap<String, Contact>,
230340 messages: BTreeMap<String, Vec<StoredMessage>>,
341+ /// Q18: Per-peer dedup ID set, independent of the trimmed conversation.
342+ /// Without this, a replayed blob whose `id` was aged out by `trim_history`
343+ /// (past the 1000-message cap) passes the dedup check and re-enters the
344+ /// conversation. This set is loaded from and persisted to kv alongside
345+ /// messages, so it survives restarts.
346+ seen_ids: BTreeMap<String, HashSet<String>>,
231347 outbox: VecDeque<OutboxItem>,
232348 cursor: i64,
233349 token: Option<String>,
234350 conn: ConnStatus,
235351 poll_retries: u32,
352+ /// The send loop's own backoff counter, spent when a `429` arrives with no
353+ /// `Retry-After` to obey. Kept apart from `poll_retries` because the poll loop
354+ /// resets that one on every page it takes: a client polling happily while the
355+ /// relay rate-limits its sends would restart the send backoff at 3 s forever,
356+ /// which is not a backoff.
357+ send_retries: u32,
236358 /// A poll request is in flight. Guards against stacking concurrent long-poll
237359 /// loops (every extra loop re-polls itself forever and never terminates).
238360 polling: bool,
@@ -260,11 +382,65 @@ pub struct Model {
260382 /// flight from before the app was backgrounded must not install a token or
261383 /// overwrite `conn` on top of the attempt that replaced it.
262384 auth_gen: u64,
385+ /// A `/messages` request is in flight. One at a time: `SendResult` pops the
386+ /// items it sent off the head of the outbox, so two overlapping sends would
387+ /// pop each other's messages.
263388 flushing: bool,
389+ /// Which flush the in-flight `SendResult` / `FlushWatchdog` is allowed to
390+ /// belong to. Same pattern as `poll_gen`: bumped every time a flush is
391+ /// issued and every time one is abandoned, so a `SendResult` or watchdog
392+ /// from a superseded send cannot clear the guard or pop items belonging to
393+ /// the replacement.
394+ flush_gen: u64,
395+ /// What the in-flight send will pop off the head of the outbox when it
396+ /// succeeds — see `InFlight`. `None` while nothing is in flight, and also
397+ /// while a send is in flight whose items have since been removed from under
398+ /// it (`SetBlocked`, `DeleteContact`): there is then nothing left to pop, and
399+ /// popping by count anyway would eat whichever messages slid into their place.
400+ in_flight: Option<InFlight>,
401+ /// What this relay will actually accept as a request body, in hex characters,
402+ /// once it has told us. `None` until then — meaning "assume
403+ /// `MAX_SEND_BATCH_BYTES`", which is a guess at a cap the protocol never
404+ /// publishes.
405+ ///
406+ /// A relay configured below our guess answers `413`, and a `413` read as a
407+ /// transient failure is a batch that is rebuilt identically, rejected
408+ /// identically, and retried until every item in it has burned its retry budget
409+ /// and been dropped — the outbox drains into the void without a single message
410+ /// leaving. So a `413` *measures* the cap instead: halve what we just tried and
411+ /// rebuild smaller. It is deliberately not reset on success — the batch that
412+ /// worked is evidence about the relay, and the relay's cap does not grow — only
413+ /// on a server change, where the evidence no longer applies.
414+ send_batch_budget: Option<usize>,
264415 /// Startup kv loads still outstanding. `Connect` only fires at 0, so a poll
265416 /// can't land and be persisted against a half-loaded model — which would
266417 /// then be clobbered by the loads still in flight.
267418 loads_pending: u8,
419+ /// A startup kv *read* failed — as opposed to finding the key absent.
420+ ///
421+ /// The distinction is the whole point of `parse_kv`'s `Result<Option<T>, ()>`:
422+ /// an absent key is a fresh install and defaulting is right, but a failed read
423+ /// leaves a hole in the model over data that is still on disk, and writing that
424+ /// hole back destroys it. The outbox is the sharpest case — `ingest_poll`
425+ /// persists it on *every* poll page, so a single failed read followed by one
426+ /// empty poll writes `[]` over a queue of real, unsent messages.
427+ ///
428+ /// So this latches the model as untrustworthy, and every write path checks it:
429+ /// no persist, no ingest, no flush. Nothing is lost, because nothing is
430+ /// written — the data stays on disk for the next launch, which re-runs the
431+ /// loads (`IdentityLoaded` fires on every boot) and clears the flag if they
432+ /// succeed. It is deliberately one flag and not a per-key set: a read that
433+ /// fails because the device is locked fails for every key, and a model that is
434+ /// wrong about its outbox is not one to be trusted about its contacts either.
435+ kv_load_failed: bool,
436+ /// `now_ms()` before which `flush_next` must not send.
437+ ///
438+ /// A `429` schedules a `StartFlush` for the far side of the relay's
439+ /// `Retry-After`, but that timer is not the only thing that fires one — a poll
440+ /// page and a fresh `SendText` both do. Without a pause the wait is decorative:
441+ /// the next poll page walks straight through it and hammers the relay that just
442+ /// asked us to stop.
443+ flush_paused_until: i64,
268444 page: Page,
269445 active_peer: Option<String>,
270446 compose: String,
@@ -280,17 +456,24 @@ impl Default for Model {
280456 profile: OwnProfile::default(),
281457 contacts: BTreeMap::new(),
282458 messages: BTreeMap::new(),
459+ seen_ids: BTreeMap::new(),
283460 outbox: VecDeque::new(),
284461 cursor: 0,
285462 token: None,
286463 conn: ConnStatus::Offline,
287464 poll_retries: 0,
465+ send_retries: 0,
288466 polling: false,
289467 poll_gen: 0,
290468 authenticating: false,
291469 auth_gen: 0,
292470 flushing: false,
471+ flush_gen: 0,
472+ in_flight: None,
473+ send_batch_budget: None,
293474 loads_pending: 0,
475+ kv_load_failed: false,
476+ flush_paused_until: 0,
294477 page: Page::default(),
295478 active_peer: None,
296479 compose: String::new(),
@@ -337,11 +520,49 @@ impl Model {
337520 self.auth_gen
338521 }
339522
523+ /// Open a new flush generation and return it. Same pattern as
524+ /// `next_poll_gen`: a `SendResult` or `FlushWatchdog` whose generation no
525+ /// longer matches is dropped, so a late result from a superseded send
526+ /// cannot clear the guard or pop items belonging to the replacement.
527+ fn next_flush_gen(&mut self) -> u64 {
528+ self.flush_gen = self.flush_gen.wrapping_add(1);
529+ self.flush_gen
530+ }
531+
532+ /// Abandon the in-flight flush, if any: release the guard and retire the
533+ /// generation so a late `SendResult` cannot clear the *replacement* flush's
534+ /// guard or pop its items.
535+ fn abandon_flush(&mut self) {
536+ self.flushing = false;
537+ self.in_flight = None;
538+ self.flush_gen = self.flush_gen.wrapping_add(1);
539+ }
540+
340541 /// Abandon the in-flight auth round-trip (either leg).
341542 fn abandon_auth(&mut self) {
342543 self.authenticating = false;
343544 self.auth_gen = self.auth_gen.wrapping_add(1);
344545 }
546+
547+ /// Every item bound for `peer` is about to be removed from the outbox. If the
548+ /// send in flight is the one carrying them, forget what it was going to pop:
549+ /// those items will not be there when it lands, and popping by count anyway
550+ /// would take whatever slid into their place — another peer's mail.
551+ ///
552+ /// The `flushing` guard stays up. Nothing can cancel the request; it is still
553+ /// out there, and a second send started underneath it would have its own items
554+ /// popped by the first one's result.
555+ fn detach_in_flight(&mut self, peer: &str) {
556+ if self.in_flight.as_ref().is_some_and(|f| f.recipient == peer) {
557+ self.in_flight = None;
558+ }
559+ }
560+
561+ /// How many items at the head of the outbox are already on the wire, and so
562+ /// must not be rewritten in place (their ciphertext is built and gone).
563+ fn in_flight_count(&self) -> usize {
564+ self.in_flight.as_ref().map_or(0, |f| f.count)
565+ }
345566}
346567
347568// ---------------------------------------------------------------------------
@@ -358,11 +579,12 @@ impl Model {
358579/// `ingest_poll`) would have to become a two-step round-trip through the shell.
359580/// That refactor is worth doing; it is not worth folding into a bug-fix pass, so
360581/// the impurity is documented rather than hidden.
582+// TODO: replace with crux_time effect for deterministic timestamps
361583fn now_ms() -> i64 {
362584 SystemTime::now()
363585 .duration_since(UNIX_EPOCH)
364586 .map(|d| d.as_millis() as i64)
365− .unwrap_or(0)
587+ .unwrap_or(1)
366588}
367589
368590/// Bare lowercased hostname of a server URL (no scheme/port/trailing dot).
@@ -450,6 +672,16 @@ struct PollEvent {
450672 #[serde(rename = "encryptedBlob")]
451673 encrypted_blob: String,
452674}
675+
676+/// Q17: Deferred delivery-ack accumulator. Collects ack_ids and the max `ts`
677+/// across all `delivery.ack` payloads from one sender in a single poll page,
678+/// so the staleness check and watermark update run once per sender after the
679+/// event loop — immune to relay page ordering.
680+#[derive(Default)]
681+struct PendingAck {
682+ ts: i64,
683+ ids: HashSet<String>,
684+}
453685#[derive(Serialize)]
454686struct SendBatch {
455687 messages: Vec<Envelope>,
@@ -483,63 +715,152 @@ impl App for Skrepka {
483715 // Fan out the startup loads. `Connect` waits until the last of
484716 // them lands (see `startup_load_done`).
485717 model.loads_pending = STARTUP_LOADS;
718+ // A fresh round of loads: whatever a previous one failed to read,
719+ // this one gets to answer for. Clearing it here is what lets a
720+ // relaunch recover from a locked-device read failure.
721+ model.kv_load_failed = false;
486722 Command::all([
487723 KeyValue::get(K_SETTINGS).then_send(Event::LoadedSettings),
488724 KeyValue::get(K_PROFILE).then_send(Event::LoadedProfile),
489725 KeyValue::get(K_CONTACTS).then_send(Event::LoadedContacts),
490726 KeyValue::get(K_CURSOR).then_send(Event::LoadedCursor),
491727 KeyValue::get(K_OUTBOX).then_send(Event::LoadedOutbox),
728+ KeyValue::get(K_SEEN_IDS).then_send(Event::LoadedSeenIds),
492729 ])
493730 .and(render())
494731 }
495732
496733 Event::LoadedSettings(res) => {
497− if let Some(s) = parse_kv::<Settings>(res) {
498− // Re-validate on the way in. The URL was normalized when the
499− // user typed it, but the blob on disk is not trustworthy: an
500− // older build wrote URLs this parser rejects, and a corrupted
501− // or hand-edited file would reach `Http::post`, which unwraps
502− // the parse. That is a panic on every launch — a boot loop
503− // with no way out from inside the app.
504− model.settings.server_url = normalize_server_url(&s.server_url)
505− .unwrap_or_else(|| DEFAULT_SERVER_URL.to_string());
734+ match parse_kv::<Settings>(res) {
735+ Ok(Some(s)) => {
736+ // Re-validate on the way in. The URL was normalized when the
737+ // user typed it, but the blob on disk is not trustworthy: an
738+ // older build wrote URLs this parser rejects, and a corrupted
739+ // or hand-edited file would reach `Http::post`, which unwraps
740+ // the parse. That is a panic on every launch — a boot loop
741+ // with no way out from inside the app.
742+ model.settings.server_url = normalize_server_url(&s.server_url)
743+ .unwrap_or_else(|| DEFAULT_SERVER_URL.to_string());
744+ }
745+ Ok(None) => {}
746+ Err(()) => {
747+ model.kv_load_failed = true;
748+ model.error = Some("could not read settings from storage".into());
749+ }
506750 }
507751 self.startup_done(model).and(render())
508752 }
509753 Event::LoadedProfile(res) => {
510− if let Some(p) = parse_kv::<OwnProfile>(res) {
511− model.profile = p;
754+ match parse_kv::<OwnProfile>(res) {
755+ Ok(Some(p)) => model.profile = p,
756+ Ok(None) => {}
757+ Err(()) => {
758+ model.kv_load_failed = true;
759+ model.error = Some("could not read profile from storage".into());
760+ }
512761 }
513762 self.startup_done(model).and(render())
514763 }
515764 Event::LoadedContacts(res) => {
516765 let mut cmds = vec![self.startup_done(model)];
517− if let Some(list) = parse_kv::<Vec<Contact>>(res) {
518− model.contacts = list.into_iter().map(|c| (c.pubkey.clone(), c)).collect();
519− // Lazily load each conversation's messages.
520− cmds.extend(model.contacts.keys().map(|peer| {
521− let peer = peer.clone();
522− KeyValue::get(k_messages(&peer))
523− .then_send(move |r| Event::LoadedMessages(peer.clone(), r))
524− }));
766+ match parse_kv::<Vec<Contact>>(res) {
767+ Ok(Some(list)) => {
768+ model.contacts = list.into_iter().map(|c| (c.pubkey.clone(), c)).collect();
769+ // Lazily load each conversation's messages.
770+ cmds.extend(model.contacts.keys().map(|peer| {
771+ let peer = peer.clone();
772+ KeyValue::get(k_messages(&peer))
773+ .then_send(move |r| Event::LoadedMessages(peer.clone(), r))
774+ }));
775+ }
776+ Ok(None) => {}
777+ Err(()) => {
778+ model.kv_load_failed = true;
779+ model.error = Some("could not read contacts from storage".into());
780+ }
525781 }
526782 Command::all(cmds).and(render())
527783 }
528784 Event::LoadedCursor(res) => {
529− if let Some(c) = parse_kv::<i64>(res) {
530− model.cursor = c;
785+ match parse_kv::<i64>(res) {
786+ Ok(Some(c)) => model.cursor = c,
787+ Ok(None) => {}
788+ Err(()) => {
789+ model.kv_load_failed = true;
790+ model.error = Some("could not read cursor from storage".into());
791+ }
531792 }
532793 self.startup_done(model).and(render())
533794 }
534795 Event::LoadedOutbox(res) => {
535− if let Some(list) = parse_kv::<Vec<OutboxItem>>(res) {
536− model.outbox = list.into();
796+ match parse_kv::<Vec<OutboxItem>>(res) {
797+ Ok(Some(list)) => model.outbox = list.into(),
798+ Ok(None) => {}
799+ Err(()) => {
800+ model.kv_load_failed = true;
801+ model.error = Some("could not read outbox from storage".into());
802+ }
803+ }
804+ self.startup_done(model).and(render())
805+ }
806+ Event::LoadedSeenIds(res) => {
807+ match parse_kv::<BTreeMap<String, HashSet<String>>>(res) {
808+ Ok(Some(map)) => model.seen_ids = map,
809+ Ok(None) => {}
810+ Err(()) => {
811+ // Non-fatal: dedup falls back to the conversation-derived
812+ // set, which is weaker but functional.
813+ model.seen_ids = BTreeMap::new();
814+ }
537815 }
538816 self.startup_done(model).and(render())
539817 }
540818 Event::LoadedMessages(peer, res) => {
541− if let Some(list) = parse_kv::<Vec<StoredMessage>>(res) {
542− model.messages.insert(peer, list);
819+ match parse_kv::<Vec<StoredMessage>>(res) {
820+ Ok(Some(list)) => {
821+ // D5: Add on-disk message IDs to seen_ids so future
822+ // replays don't pass dedup. Without this, a seen_ids
823+ // kv load failure leaves the set empty, and on-disk
824+ // messages aren't protected against replay.
825+ if let Some(id_set) = model.seen_ids.get_mut(&peer) {
826+ id_set.extend(list.iter().map(|m| m.id.clone()));
827+ }
828+ // Merge: a poll that beat this lazy load may have already
829+ // inserted messages for this peer. Overwriting with the
830+ // on-disk list (which the GET read before the poll wrote)
831+ // would silently destroy the freshly-ingested messages.
832+ // Union by id, keeping both the on-disk history and any
833+ // in-memory additions.
834+ match model.messages.get_mut(&peer) {
835+ Some(existing) => {
836+ let existing_ids: HashSet<&String> =
837+ existing.iter().map(|m| &m.id).collect();
838+ let new_msgs: Vec<StoredMessage> = list
839+ .into_iter()
840+ .filter(|m| !existing_ids.contains(&m.id))
841+ .collect();
842+ existing.extend(new_msgs);
843+ // Re-sort by ts to maintain the invariant.
844+ existing.sort_by_key(|m| m.ts);
845+ trim_history(existing);
846+ }
847+ None => {
848+ model.messages.insert(peer, list);
849+ }
850+ }
851+ }
852+ Ok(None) => {}
853+ Err(()) => {
854+ // Leaving the conversation absent is not enough on its own.
855+ // An absent conversation is an *empty* one to everything
856+ // downstream, so the next message from this peer would be
857+ // appended to nothing and `persist_messages` would write
858+ // that one message over the whole history still on disk.
859+ // Latch the model as untrustworthy instead — same reasoning
860+ // as the outbox, same fix.
861+ model.kv_load_failed = true;
862+ model.error = Some("could not read messages from storage".into());
863+ }
543864 }
544865 render()
545866 }
@@ -617,6 +938,12 @@ impl App for Skrepka {
617938 model.settings.server_url = url;
618939 model.token = None;
619940 model.conn = ConnStatus::Offline;
941+ // Whatever we learned about the old relay's body cap was about *it*.
942+ // A new relay is entitled to a bigger one, and carrying a shrunken
943+ // budget over would cap our batches against a limit that no longer
944+ // exists — with no `413` left to correct it, since the new relay has
945+ // no reason to send one.
946+ model.send_batch_budget = None;
620947 // The cursor is *per relay*: it is that server's own sequence
621948 // number, and the next poll acks everything up to it. Carrying
622949 // relay A's cursor (roughly `now_ms()`) over to relay B tells B
@@ -630,12 +957,30 @@ impl App for Skrepka {
630957 // would then ack a sequence number B never issued, and B would
631958 // drop every message waiting for us.
632959 model.abandon_poll();
633− Command::all([
634− KeyValue::set(K_SETTINGS, json_bytes(&model.settings)).then_send(Event::Saved),
635− KeyValue::set(K_CURSOR, json_bytes(&0i64)).then_send(Event::Saved),
636− ])
637− .and(Command::event(Event::Connect))
638− .and(render())
960+ // ...and retire the send that is still in flight *to relay A*,
961+ // for the same reason: its `SendResult` carries A's acceptance,
962+ // and popping items here would eat whatever the new relay's
963+ // send is about to carry. The generation check in `SendResult`
964+ // is what makes the late result a no-op.
965+ model.abandon_flush();
966+ // The old relay's rate limit was the old relay's opinion. A new one is
967+ // entitled to take our sends immediately, and carrying the pause over
968+ // would park the outbox against a limit that no longer applies.
969+ model.flush_paused_until = 0;
970+ model.send_retries = 0;
971+ // D2: Reset poll retries too — the new relay's poll failures
972+ // should start fresh, not inherit the old relay's backoff.
973+ model.poll_retries = 0;
974+ let writes = if self.refuse_write(model) {
975+ Command::done()
976+ } else {
977+ Command::all([
978+ KeyValue::set(K_SETTINGS, json_bytes(&model.settings))
979+ .then_send(Event::Saved),
980+ KeyValue::set(K_CURSOR, json_bytes(&0i64)).then_send(Event::Saved),
981+ ])
982+ };
983+ writes.and(Command::event(Event::Connect)).and(render())
639984 }
640985 Event::Connect => {
641986 // Connect restarts the auth flow, so whatever challenge/verify was
@@ -646,13 +991,42 @@ impl App for Skrepka {
646991 // and about to resolve. Clearing the guard alone would let it land
647992 // and install its token on top of the attempt replacing it.
648993 model.abandon_auth();
994+ // The shell fires `Connect` on every return to the foreground. A model
995+ // that failed a startup read must not take that invitation: connecting
996+ // leads to polling, and polling into a hole acks mail to the relay that
997+ // we cannot store. Staying offline is what keeps the disk intact until
998+ // a relaunch re-runs the loads.
999+ if model.kv_load_failed {
1000+ return render();
1001+ }
6491002 if model.secret_key.is_some() && model.conn != ConnStatus::Online {
6501003 Command::event(Event::Authenticate)
1004+ } else if model.secret_key.is_some()
1005+ && model.conn == ConnStatus::Online
1006+ && !model.polling
1007+ {
1008+ // The poll loop can die without `conn` going offline: after
1009+ // `PollResult` clears `polling`, the re-poll is chained off
1010+ // `SavedCursor`. If the shell drops that effect (backgrounded
1011+ // app, bug), `polling` stays `false` with no pending re-poll
1012+ // and the watchdog sees `!polling` and does nothing. The
1013+ // status shows "online" but no polling ever happens. Restart
1014+ // the loop here — `Connect` is fired on every foreground return.
1015+ Command::event(Event::Poll)
6511016 } else {
6521017 render()
6531018 }
6541019 }
6551020 Event::AddContact { input, nickname } => {
1021+ // Clear a stale error from a previous failed add.
1022+ model.error = None;
1023+ // A nickname is stored in the contacts kv blob, which is
1024+ // rewritten in full on every change. An unbounded nickname
1025+ // bloats the blob and every subsequent write.
1026+ if nickname.len() > protocol::MAX_DISPLAY_NAME_LEN {
1027+ model.error = Some("nickname too long".into());
1028+ return render();
1029+ }
6561030 match phonemic::try_parse_pubkey(&input) {
6571031 Some(hex) if hex != model.my_pubkey => {
6581032 model
@@ -682,6 +1056,9 @@ impl App for Skrepka {
6821056 if let Some(c) = model.contacts.get_mut(&peer) {
6831057 c.blocked = blocked;
6841058 }
1059+ // Clear a stale error (e.g. "cannot send to a blocked contact")
1060+ // when the user unblocks — the block that caused it is now lifted.
1061+ model.error = None;
6851062 if blocked {
6861063 // Gating *ingest* on the block only stops the acks we have not
6871064 // queued yet. Anything already sitting in the outbox for this
@@ -691,16 +1068,68 @@ impl App for Skrepka {
6911068 // signal the block is supposed to cut off. Drop it all: once
6921069 // blocked, nothing more goes to this peer.
6931070 model.outbox.retain(|item| item.recipient != peer);
1071+ model.detach_in_flight(&peer);
6941072 return Command::all([self.persist_contacts(model), self.persist_outbox(model)])
6951073 .and(render());
6961074 }
6971075 self.persist_contacts(model).and(render())
6981076 }
1077+ Event::DeleteContact { peer } => {
1078+ model.contacts.remove(&peer);
1079+ model.messages.remove(&peer);
1080+ model.seen_ids.remove(&peer);
1081+ model.outbox.retain(|item| item.recipient != peer);
1082+ // The send in flight may be carrying the very items we just
1083+ // dropped; if so its result must pop nothing.
1084+ model.detach_in_flight(&peer);
1085+ if model.active_peer.as_deref() == Some(peer.as_str()) {
1086+ model.active_peer = None;
1087+ model.page = Page::Conversations;
1088+ }
1089+ model.error = None;
1090+ Command::all([
1091+ self.persist_contacts(model),
1092+ // The conversation is gone from the model, but `persist_messages`
1093+ // would leave a `messages:<peer>` blob behind holding every
1094+ // message the user just asked us to forget. Delete the key.
1095+ KeyValue::delete(k_messages(&peer)).then_send(Event::Saved),
1096+ self.persist_outbox(model),
1097+ // Q18: persist the seen_ids map without the removed peer.
1098+ self.persist_seen_ids(model),
1099+ ])
1100+ .and(render())
1101+ }
6991102 Event::SaveProfile {
7001103 display_name,
7011104 bio,
7021105 photo,
7031106 } => {
1107+ // Clear a stale error from a previous failed save.
1108+ model.error = None;
1109+ // The recipient's `parse_payload` enforces these caps and
1110+ // silently drops oversized profiles. Without these checks the
1111+ // sender's local profile would be saved, broadcast to every
1112+ // contact, and silently dropped by every recipient — a silent
1113+ // divergence between what the sender sees and what contacts see.
1114+ if display_name.chars().count() > protocol::MAX_DISPLAY_NAME_LEN {
1115+ model.error = Some("display name too long".into());
1116+ return render();
1117+ }
1118+ if bio.chars().count() > protocol::MAX_BIO_LEN {
1119+ model.error = Some("bio too long".into());
1120+ return render();
1121+ }
1122+ if photo.as_ref().is_some_and(|p| p.len() > protocol::MAX_PHOTO_LEN) {
1123+ model.error = Some("photo too large".into());
1124+ return render();
1125+ }
1126+ // S6: Validate the photo is valid base64 before broadcasting —
1127+ // the recipient's parse_payload rejects invalid base64, so an
1128+ // invalid photo would be silently dropped by every recipient.
1129+ if photo.as_ref().is_some_and(|p| BASE64_STANDARD.decode(p).is_err()) {
1130+ model.error = Some("photo is not valid base64".into());
1131+ return render();
1132+ }
7041133 model.profile = OwnProfile {
7051134 display_name,
7061135 bio,
@@ -709,8 +1138,8 @@ impl App for Skrepka {
7091138 model.page = Page::Conversations;
7101139 let ts = now_ms();
7111140 let payload = Payload::Profile {
712− display_name: model.profile.display_name.clone(),
713− bio: model.profile.bio.clone(),
1141+ display_name: Some(model.profile.display_name.clone()),
1142+ bio: Some(model.profile.bio.clone()),
7141143 photo: model.profile.photo.clone(),
7151144 };
7161145 // Broadcast the new profile to every contact we haven't blocked.
@@ -718,25 +1147,44 @@ impl App for Skrepka {
7181147 // profile broadcast would keep feeding them our display name,
7191148 // avatar, and a liveness signal.
7201149 //
721− // Each item carries its own copy of the serialized payload, so a
722− // profile with a photo is duplicated (base64 and all) once per
723− // contact, in memory and in the `outbox` kv blob. Acceptable at
724− // today's contact counts; the fix is to intern the payload and
725− // have `OutboxItem` reference it by id.
1150+ // One `Arc<String>` for the whole fan-out: the payload carries a
1151+ // base64 photo, and a copy per contact would be megabytes in memory
1152+ // for a list of any size. (The `outbox` kv blob still serializes the
1153+ // string once per item — serde has no idea the `Arc`s are shared —
1154+ // but the supersede-in-place below caps that at one pending profile
1155+ // per contact, which is the bound that actually matters.)
7261156 let recipients: Vec<String> = model
7271157 .contacts
7281158 .values()
7291159 .filter(|c| !c.blocked)
7301160 .map(|c| c.pubkey.clone())
7311161 .collect();
1162+ let payload_json = Arc::new(protocol::serialize_payload(&payload, ts));
1163+ // Items already on the wire cannot be rewritten: their ciphertext is
1164+ // built and gone, and `SendResult` will pop them on success — so a
1165+ // payload swapped into one now would be dropped having never been
1166+ // sent. Supersede only what is still behind them.
1167+ let live = model.in_flight_count();
7321168 for peer in recipients {
733− model.outbox.push_back(OutboxItem {
734− recipient: peer,
735− envelope_json: protocol::serialize_payload(&payload, ts),
736− });
1169+ // A profile is state, not an event: only the newest one means
1170+ // anything. Overwrite the pending one for this peer instead of
1171+ // queueing a second — five quick edits to a profile with a photo
1172+ // would otherwise be five payloads per contact, each of which we
1173+ // then encrypt and send.
1174+ match model
1175+ .outbox
1176+ .iter_mut()
1177+ .skip(live)
1178+ .find(|i| i.is_profile() && i.recipient == peer)
1179+ {
1180+ Some(pending) => pending.envelope_json = Arc::clone(&payload_json),
1181+ None => model
1182+ .outbox
1183+ .push_back(OutboxItem::profile(peer, Arc::clone(&payload_json))),
1184+ }
7371185 }
7381186 Command::all([
739− KeyValue::set(K_PROFILE, json_bytes(&model.profile)).then_send(Event::Saved),
1187+ self.persist_profile(model),
7401188 self.persist_outbox(model),
7411189 ])
7421190 .and(Command::event(Event::StartFlush))
@@ -770,6 +1218,11 @@ impl App for Skrepka {
7701218 let gen = model.next_auth_gen();
7711219 req.build()
7721220 .then_send(move |r| Event::ChallengeResult(gen, r))
1221+ .and(
1222+ Time::notify_after(Duration::from_millis(AUTH_WATCHDOG_MS))
1223+ .0
1224+ .then_send(move |_| Event::AuthWatchdog(gen)),
1225+ )
7731226 .and(render())
7741227 }
7751228 Err(_) => {
@@ -934,42 +1387,214 @@ impl App for Skrepka {
9341387 return self.backoff_poll(model);
9351388 }
9361389 model.poll_retries = 0;
1390+ // Ingesting a page into a model with a hole in it is the worst thing
1391+ // this client can do. The cursor write below is what lets the relay
1392+ // delete the mail we just took, so a page ingested into a model that
1393+ // cannot persist it is a page destroyed on both sides at once. Stop
1394+ // the poll loop instead — it restarts on the next launch, which
1395+ // re-runs the loads.
1396+ if model.kv_load_failed {
1397+ model.error = Some(
1398+ "storage read failed — restart the app; messages are not being saved"
1399+ .into(),
1400+ );
1401+ return render();
1402+ }
9371403 let bytes = resp.take_body().unwrap_or_default();
938− let parsed: PollResp = serde_json::from_slice(&bytes).unwrap_or_default();
1404+ // Bound the response before parsing: a hostile relay can return
1405+ // a multi-gigabyte body that OOMs the app before `ingest_poll`'s
1406+ // per-blob budgets are even consulted.
1407+ if bytes.len() > MAX_POLL_RESPONSE_BYTES {
1408+ model.error = Some("relay sent an oversized poll response".into());
1409+ return self.backoff_poll(model);
1410+ }
1411+ // Q25: A malformed or unparseable poll response must not be
1412+ // treated as an empty page — `unwrap_or_default()` would adopt
1413+ // cursor 0, forcing a re-fetch from the beginning and wasting
1414+ // bandwidth on already-seen (deduped) messages. Back off instead.
1415+ let parsed: PollResp = match serde_json::from_slice(&bytes) {
1416+ Ok(p) => p,
1417+ Err(_) => {
1418+ model.error = Some("relay sent a malformed poll response".into());
1419+ return self.backoff_poll(model);
1420+ }
1421+ };
1422+ let cursor_before = model.cursor;
9391423 let cmd = self.ingest_poll(model, parsed);
9401424 // The re-poll hangs off the *cursor write*, not off this event.
9411425 // Polling again is what acks the batch we just took — the server
9421426 // deletes everything up to `cursor` — so it must not happen until
9431427 // the batch is durable on our side. `SavedCursor` re-polls.
944− cmd.and(
1428+ //
1429+ // Arm a watchdog alongside the cursor write: if the shell ever
1430+ // drops the KV effect (suspension, bug), `SavedCursor` never fires,
1431+ // `polling` stays `false`, and the loop is dead until the next
1432+ // foreground `Connect`. The watchdog fires `Poll` if the loop is
1433+ // still idle — same pattern as the poll/send HTTP watchdogs.
1434+ //
1435+ // Skip the cursor write when the cursor did not advance (an empty
1436+ // or fully-deduped page): there is nothing new to persist, so
1437+ // re-poll directly. The watchdog is still armed as a fallback.
1438+ let cursor_advanced = model.cursor != cursor_before;
1439+ cmd.and(if cursor_advanced {
9451440 KeyValue::set(K_CURSOR, json_bytes(&model.cursor))
946− .then_send(Event::SavedCursor),
1441+ .then_send(Event::SavedCursor)
1442+ } else {
1443+ Command::event(Event::Poll)
1444+ })
1445+ .and(
1446+ Time::notify_after(Duration::from_millis(POLL_WATCHDOG_MS))
1447+ .0
1448+ .then_send(|_| Event::Poll),
9471449 )
9481450 .and(render())
9491451 }
9501452
9511453 // ---------------- outbox ----------------
9521454 Event::StartFlush => self.flush_next(model),
953− Event::SendResult(Ok(resp)) => {
1455+ Event::FlushWatchdog(gen) => {
1456+ // Only the flush this watchdog was armed for, and only while it
1457+ // is still the current one and still in flight. A watchdog whose
1458+ // send already completed (or was superseded) is a stale timer and
1459+ // must not touch a healthy successor — same pattern as
1460+ // `PollWatchdog`.
1461+ if gen != model.flush_gen || !model.flushing {
1462+ return Command::done();
1463+ }
1464+ // Retire it as we give up on it. The request itself is not
1465+ // cancelled, so if it eventually resolves the generation check
1466+ // in `SendResult` is what stops it from popping the replacement's
1467+ // items.
1468+ model.abandon_flush();
1469+ self.flush_next(model)
1470+ }
1471+ Event::AuthWatchdog(gen) => {
1472+ // Only the auth this watchdog was armed for, and only while it is
1473+ // still the current one and still in flight.
1474+ if gen != model.auth_gen || !model.authenticating {
1475+ return Command::done();
1476+ }
1477+ model.abandon_auth();
1478+ Command::event(Event::Authenticate)
1479+ }
1480+ Event::SendResult(gen, Ok(resp)) => {
1481+ // A result for a send we already abandoned (a watchdog gave up
1482+ // on it, or a server change invalidated it). Dropping it is safe
1483+ // and required: its items were re-queued, so popping by count
1484+ // here would eat whichever messages slid into their place.
1485+ if gen != model.flush_gen {
1486+ return Command::done();
1487+ }
9541488 // The in-flight send is over; `flush_next` refuses to run while
9551489 // this is set, so it must be cleared before *any* branch below.
9561490 model.flushing = false;
1491+ let batch = model.in_flight.take();
9571492 let status = u16::from(resp.status());
9581493 if status == 401 {
9591494 model.token = None;
1495+ // The batch stays exactly as it is — re-auth, then re-send it.
9601496 return Command::event(Event::Authenticate);
9611497 }
1498+ if status == 429 {
1499+ // Rate-limited. Not a delivery failure and not the items'
1500+ // fault, so they are not charged a retry — a client that spent
1501+ // its delivery budget on the relay's load would drop perfectly
1502+ // good messages for being sent too enthusiastically. They stay
1503+ // queued untouched; we just wait.
1504+ //
1505+ // `Retry-After` is the relay saying how long. Only the
1506+ // delta-seconds form is read — the HTTP-date form falls back to
1507+ // our own backoff — and it is clamped either way, because
1508+ // obeying an unbounded number from a relay is how the outbox
1509+ // gets parked forever.
1510+ let delay = resp
1511+ .header("retry-after")
1512+ .map(|v| v.last().as_str())
1513+ .and_then(|v| v.trim().parse::<u64>().ok())
1514+ .map_or_else(
1515+ || {
1516+ // Nothing to honour, so guess — on the *send* loop's
1517+ // counter, not the poll loop's. `poll_retries` is reset
1518+ // by every page the poll loop takes, so a client polling
1519+ // happily while the relay throttles its sends would
1520+ // restart the send backoff at 3 s on every page, forever.
1521+ // That is not a backoff; it is a fixed 3 s retry dressed
1522+ // as one.
1523+ let ms = backoff_ms(model.send_retries);
1524+ model.send_retries = model.send_retries.saturating_add(1);
1525+ Duration::from_millis(ms)
1526+ },
1527+ |secs| {
1528+ Duration::from_millis(
1529+ secs.saturating_mul(1000).min(MAX_RETRY_AFTER_MS),
1530+ )
1531+ },
1532+ );
1533+ // Park the send loop for the duration, on the *model*. The timer
1534+ // below is not the only thing that fires `StartFlush` — a poll page
1535+ // and a fresh `SendText` both do — and without a pause they walk
1536+ // straight through the wait and hammer the relay that just asked us
1537+ // to stop. `flush_next` refuses to send until this passes, whoever
1538+ // wakes it.
1539+ model.flush_paused_until =
1540+ now_ms().saturating_add(i64::try_from(delay.as_millis()).unwrap_or(i64::MAX));
1541+ return Time::notify_after(delay)
1542+ .0
1543+ .then_send(|_| Event::StartFlush)
1544+ .and(render());
1545+ }
1546+ if status == 413 {
1547+ // The body outgrew what this relay accepts. `MAX_SEND_BATCH_BYTES`
1548+ // is only a guess at that cap, and this relay's is smaller — so
1549+ // treating the `413` as transient rebuilds the very same batch,
1550+ // which is rejected the very same way, forever.
1551+ //
1552+ // Measure the cap instead: halve what this batch actually
1553+ // weighed and rebuild under that. The items are untouched (we
1554+ // only pop on 200/400), so there is nothing to re-queue.
1555+ //
1556+ // Only a *splittable* batch takes this path. A lone item over
1557+ // the cap cannot be made any smaller, and halving the budget
1558+ // around it would spin — `flush_next` always takes the first
1559+ // item whatever it weighs. It falls through to `retry_batch`,
1560+ // whose budget is what eventually drops it, with an error the
1561+ // user can see.
1562+ if let Some(b) = batch.as_ref().filter(|b| b.count > 1) {
1563+ model.send_batch_budget = Some(b.bytes / 2);
1564+ return self.flush_next(model);
1565+ }
1566+ }
9621567 if (200..300).contains(&status) || status == 400 {
963− // success, or a permanent rejection (self_send/invalid) — drop it.
964− model.outbox.pop_front();
1568+ // The batch was accepted, or rejected outright (`self_send` /
1569+ // `invalid_message` — both permanent, and the relay takes a
1570+ // batch all-or-nothing). Either way it is finished with.
1571+ //
1572+ // The relay is taking our sends again, so the rate-limit backoff
1573+ // has done its job: forget it, or the *next* 429 — possibly hours
1574+ // later, under load that has nothing to do with this one — starts
1575+ // at whatever height the last one climbed to.
1576+ model.send_retries = 0;
1577+ // D3-app: Don't pop if kv is broken — the persist would be
1578+ // refused, and the items would be lost from memory but still
1579+ // on disk, causing duplicate sends on relaunch.
1580+ if !model.kv_load_failed {
1581+ for _ in 0..batch.map_or(0, |b| b.count) {
1582+ model.outbox.pop_front();
1583+ }
1584+ }
9651585 return self.persist_outbox(model).and(self.flush_next(model));
9661586 }
967− // transient error — stop; will resume on next connect/poll.
968− render()
1587+ // A transient failure: a 5xx, a rate limit, a relay restarting.
1588+ self.retry_batch(model, batch)
9691589 }
970− Event::SendResult(Err(_)) => {
1590+ Event::SendResult(gen, Err(_)) => {
1591+ // A transport error is the same transient failure as a 5xx.
1592+ if gen != model.flush_gen {
1593+ return Command::done();
1594+ }
9711595 model.flushing = false;
972− render()
1596+ let batch = model.in_flight.take();
1597+ self.retry_batch(model, batch)
9731598 }
9741599 }
9751600 }
@@ -990,18 +1615,13 @@ impl App for Skrepka {
9901615
9911616 let active_peer = model.active_peer.clone().unwrap_or_default();
9921617
993− // `view()` runs on every render, and `ComposeChanged` renders on every
994− // keystroke. A contact's `photo` is a base64 avatar — tens of KiB each —
995− // so cloning all of them per keypress meant megabytes of allocation and
996− // bincode-encoding to type one message.
997− //
998− // Only the chat page has a composer (`ComposeChanged` is sent from
999− // `ChatView` and nowhere else), so only the chat page is on that hot path
1000− // — and while it is up, the only avatar on screen is the peer we are
1001− // talking to. Every *other* page renders from a cold event, and the
1002− // conversations list draws an avatar per row, so it gets the real photos.
1003− // Withholding them there would not save a single keystroke's work; it
1004− // would just replace every contact's picture with their initials.
1618+ // `view()` is called after every event the core processes. The
1619+ // per-keystroke optimization below assumes `ComposeChanged` fires on
1620+ // every keystroke, but the Swift shell only sends it before `SendText`
1621+ // — so in practice this path runs once per message, not per keypress.
1622+ // The optimization is still correct (it withholds avatars on the chat
1623+ // page regardless of how often `view` runs), just the original comment
1624+ // overstated the frequency.
10051625 let chat_open = model.page == Page::Chat;
10061626
10071627 let mut contacts: Vec<ContactVM> = model
@@ -1066,7 +1686,6 @@ impl App for Skrepka {
10661686 active_peer_ob: hex_to_ob(&active_peer),
10671687 active_peer_blocked: active_contact.is_some_and(|c| c.blocked),
10681688 messages,
1069− compose: model.compose.clone(),
10701689 error: model.error.clone().unwrap_or_default(),
10711690 }
10721691 }
@@ -1080,28 +1699,83 @@ impl Skrepka {
10801699 /// still in flight would then overwrite what the poll just ingested, and the
10811700 /// stale `cursor` (0) would make us re-fetch mail we had already acked.
10821701 fn startup_done(&self, model: &mut Model) -> Command<Effect, Event> {
1083− if model.startup_load_done() {
1084− Command::event(Event::Connect)
1085− } else {
1086− Command::done()
1702+ if !model.startup_load_done() {
1703+ return Command::done();
1704+ }
1705+ if model.kv_load_failed {
1706+ // One of the loads could not be read (as opposed to being absent), so
1707+ // the model has a hole in it over data that is still on disk. Do not
1708+ // connect: a poll would ingest mail into that hole and ack it, and the
1709+ // relay would then delete the only copy of messages we never persisted.
1710+ //
1711+ // Everything downstream is already write-guarded, so this is belt and
1712+ // braces — but it is also the only place that can *say* so, and the
1713+ // recovery is a relaunch, which re-runs the loads.
1714+ model.error = Some(
1715+ "storage read failed — restart the app; changes will not be saved until you do"
1716+ .into(),
1717+ );
1718+ return render();
1719+ }
1720+ Command::event(Event::Connect)
1721+ }
1722+
1723+ /// The three model-state writes, and the one rule they share: a model that
1724+ /// failed to read a key must never write one.
1725+ ///
1726+ /// `persist_outbox` is the reason this matters. `ingest_poll` calls it on every
1727+ /// poll page — including an empty one — so a failed outbox read followed by a
1728+ /// single idle poll is enough to write `[]` over a queue of real unsent
1729+ /// messages. The user's mail is destroyed by a client doing nothing at all.
1730+ fn refuse_write(&self, model: &mut Model) -> bool {
1731+ if model.kv_load_failed {
1732+ model.error = Some("storage read failed — changes will not be saved".into());
1733+ return true;
10871734 }
1735+ false
10881736 }
10891737
1090− fn persist_contacts(&self, model: &Model) -> Command<Effect, Event> {
1738+ fn persist_contacts(&self, model: &mut Model) -> Command<Effect, Event> {
1739+ if self.refuse_write(model) {
1740+ return Command::done();
1741+ }
10911742 let list: Vec<Contact> = model.contacts.values().cloned().collect();
10921743 KeyValue::set(K_CONTACTS, json_bytes(&list)).then_send(Event::Saved)
10931744 }
10941745
1095− fn persist_outbox(&self, model: &Model) -> Command<Effect, Event> {
1746+ fn persist_profile(&self, model: &mut Model) -> Command<Effect, Event> {
1747+ if self.refuse_write(model) {
1748+ return Command::done();
1749+ }
1750+ KeyValue::set(K_PROFILE, json_bytes(&model.profile)).then_send(Event::Saved)
1751+ }
1752+
1753+ fn persist_outbox(&self, model: &mut Model) -> Command<Effect, Event> {
1754+ if self.refuse_write(model) {
1755+ return Command::done();
1756+ }
10961757 let list: Vec<OutboxItem> = model.outbox.iter().cloned().collect();
10971758 KeyValue::set(K_OUTBOX, json_bytes(&list)).then_send(Event::Saved)
10981759 }
10991760
1100− fn persist_messages(&self, model: &Model, peer: &str) -> Command<Effect, Event> {
1761+ fn persist_messages(&self, model: &mut Model, peer: &str) -> Command<Effect, Event> {
1762+ if self.refuse_write(model) {
1763+ return Command::done();
1764+ }
11011765 let list = model.messages.get(peer).cloned().unwrap_or_default();
11021766 KeyValue::set(k_messages(peer), json_bytes(&list)).then_send(Event::Saved)
11031767 }
11041768
1769+ /// Q18: Persist the per-peer dedup ID set. Written alongside messages so
1770+ /// the set survives restarts and covers IDs that `trim_history` has aged
1771+ /// out of the conversation.
1772+ fn persist_seen_ids(&self, model: &mut Model) -> Command<Effect, Event> {
1773+ if self.refuse_write(model) {
1774+ return Command::done();
1775+ }
1776+ KeyValue::set(K_SEEN_IDS, json_bytes(&model.seen_ids)).then_send(Event::Saved)
1777+ }
1778+
11051779 fn schedule_reconnect(&self, model: &mut Model) -> Command<Effect, Event> {
11061780 let delay = backoff_ms(model.poll_retries);
11071781 model.poll_retries = model.poll_retries.saturating_add(1);
@@ -1132,47 +1806,95 @@ impl Skrepka {
11321806 let Some(peer) = model.active_peer.clone() else {
11331807 return render();
11341808 };
1809+ // Clear a stale error from a previous failed send, so the error display
1810+ // does not persist after the user fixes the issue and sends again.
1811+ model.error = None;
1812+ // Blocking cuts the peer off in both directions (PROTOCOL.md §4). The
1813+ // ingest side drops their messages; the send side must refuse too, or
1814+ // a blocked peer still receives our texts, acks, and the liveness
1815+ // signal that blocking is supposed to cut off.
1816+ if model.contacts.get(&peer).is_some_and(|c| c.blocked) {
1817+ model.error = Some("cannot send to a blocked contact".into());
1818+ return render();
1819+ }
11351820 let body = model.compose.trim().to_string();
11361821 if body.is_empty() {
11371822 return render();
11381823 }
1824+ // The recipient's `parse_payload` enforces `MAX_BODY_LEN` and silently
1825+ // drops oversized text. Without this check the message would be stored
1826+ // locally, sent to the relay, and marked "sent" — but never arrive, never
1827+ // get acked, and the sender would see it stuck as "sent" forever with no
1828+ // error.
1829+ if body.len() > protocol::MAX_BODY_LEN {
1830+ model.error = Some("message too long".into());
1831+ return render();
1832+ }
1833+
1834+ // Check the contact cap *before* mutating anything. The old order
1835+ // cleared `compose` and inserted the message into `model.messages`
1836+ // first, then hit the cap and returned early — so the user's text was
1837+ // gone (compose cleared), the message sat in an invisible orphan
1838+ // conversation (no contact entry to click on), and nothing was
1839+ // persisted (no `persist_messages` before the early return). On next
1840+ // launch the message was silently lost.
1841+ let was_new = !model.contacts.contains_key(&peer);
1842+ if was_new && model.contacts.len() >= MAX_CONTACTS {
1843+ model.error = Some("contact list is full".into());
1844+ return render();
1845+ }
1846+
11391847 model.compose.clear();
11401848 let ts = now_ms();
11411849 let id = uuid::Uuid::new_v4().to_string();
11421850
11431851 let convo = model.messages.entry(peer.clone()).or_default();
1144− let first_to_peer = !convo.iter().any(|m| m.outgoing);
1145− convo.push(StoredMessage {
1146− id: id.clone(),
1147− body: body.clone(),
1148− ts,
1149− outgoing: true,
1150− delivered: false,
1151− });
1852+ // Insert in order rather than appending: an incoming message may hold a
1853+ // `ts` up to `MAX_FUTURE_SKEW_MS` ahead of ours, so appending would leave
1854+ // the conversation unsorted — and `trim_history` ages out the *front*.
1855+ insert_sorted(
1856+ convo,
1857+ StoredMessage {
1858+ id: id.clone(),
1859+ body: body.clone(),
1860+ ts,
1861+ outgoing: true,
1862+ delivered: false,
1863+ },
1864+ );
11521865 trim_history(convo);
11531866
1154− // Auto-create a bare contact if messaging a brand-new key.
1155− model
1156− .contacts
1157− .entry(peer.clone())
1158− .or_insert_with(|| Contact::new(peer.clone(), String::new(), ts));
1867+ // Auto-create a bare contact if messaging a brand-new key, respecting
1868+ // the same `MAX_CONTACTS` cap `ingest_poll` enforces. This is
1869+ // user-driven (not an attack vector), but the cap exists to bound the
1870+ // `contacts` kv blob, which is rewritten in full on every change.
1871+ if was_new {
1872+ model
1873+ .contacts
1874+ .insert(peer.clone(), Contact::new(peer.clone(), String::new(), ts));
1875+ }
11591876
11601877 let text = Payload::Text { id, body };
1161− model.outbox.push_back(OutboxItem {
1162− recipient: peer.clone(),
1163− envelope_json: protocol::serialize_payload(&text, ts),
1164− });
1165− // On first contact, also share our profile.
1166− if first_to_peer {
1878+ model.outbox.push_back(OutboxItem::new(
1879+ peer.clone(),
1880+ Arc::new(protocol::serialize_payload(&text, ts)),
1881+ ));
1882+
1883+ // On first contact, share our profile *after* the text. The text
1884+ // auto-creates the contact on the recipient's side; the profile that
1885+ // follows in the same batch then applies to the now-existing contact.
1886+ // (Previously profile was queued before the text, but the recipient's
1887+ // ingest drops profiles from non-contacts, so the profile was lost.)
1888+ if was_new {
11671889 let profile = Payload::Profile {
1168− display_name: model.profile.display_name.clone(),
1169− bio: model.profile.bio.clone(),
1890+ display_name: Some(model.profile.display_name.clone()),
1891+ bio: Some(model.profile.bio.clone()),
11701892 photo: model.profile.photo.clone(),
11711893 };
1172− model.outbox.push_back(OutboxItem {
1173− recipient: peer.clone(),
1174− envelope_json: protocol::serialize_payload(&profile, ts),
1175− });
1894+ model.outbox.push_back(OutboxItem::profile(
1895+ peer.clone(),
1896+ Arc::new(protocol::serialize_payload(&profile, ts)),
1897+ ));
11761898 }
11771899
11781900 Command::all([
@@ -1184,8 +1906,23 @@ impl Skrepka {
11841906 .and(render())
11851907 }
11861908
1187− /// Encrypt and send the head of the outbox, discarding any unsendable items
1188− /// ahead of it.
1909+ /// Encrypt and send a batch from the head of the outbox, discarding any
1910+ /// unsendable items in the way.
1911+ ///
1912+ /// The batch is the longest run of items at the head that share a recipient,
1913+ /// bounded by `MAX_SEND_BATCH` and `MAX_SEND_BATCH_BYTES`. Sending them one
1914+ /// at a time meant an HTTP round-trip per message — and per *ack*, which
1915+ /// `ingest_poll` queues one of per sender per page, so catching up after a
1916+ /// long offline stretch was one request per message received. The relay takes
1917+ /// up to a hundred per request (PROTOCOL.md §7); take it up on that.
1918+ ///
1919+ /// Stopping at the first recipient change keeps the outbox's FIFO ordering
1920+ /// intact — a batch is delivered as a unit, so hoisting a later item for the
1921+ /// same peer over an earlier one for a different peer could only reorder
1922+ /// *across* conversations, but it would also let one busy peer starve the
1923+ /// rest of the queue. Consecutive-only is the cheap, obviously-fair rule, and
1924+ /// it already collapses the two cases that matter: a burst of texts to the
1925+ /// open chat, and a page's worth of acks back to one sender.
11891926 ///
11901927 /// The discards happen in one pass, followed by a single `persist_outbox`.
11911928 /// The previous shape recursed once per bad item and emitted a full outbox
@@ -1196,86 +1933,223 @@ impl Skrepka {
11961933 if model.flushing {
11971934 return Command::done();
11981935 }
1936+ // A failed startup read means the outbox in memory is not the outbox on
1937+ // disk. Sending from it is not the danger — `persist_outbox` refusing to
1938+ // write is — but a send that cannot record having happened is one that will
1939+ // happen again on the next launch, from the queue still on disk. Sit still.
1940+ if model.kv_load_failed {
1941+ return Command::done();
1942+ }
1943+ // A 429 parked the loop until the far side of the relay's `Retry-After`.
1944+ // The timer that set the pause also scheduled the `StartFlush` that resumes
1945+ // us, so whoever woke us early — a poll page, a fresh `SendText` — the
1946+ // answer is the same: the relay asked us to stop until then.
1947+ if now_ms() < model.flush_paused_until {
1948+ return Command::done();
1949+ }
11991950 let (Some(id), Some(token)) = (model.identity(), model.token.clone()) else {
12001951 return Command::done();
12011952 };
12021953
1203− let mut dropped = false;
1204− let sendable = loop {
1205− let Some(item) = model.outbox.front() else {
1206− break None;
1954+ let now = now_ms();
1955+ let mut dirty = false;
1956+ let mut recipient: Option<String> = None;
1957+ let mut messages: Vec<Envelope> = Vec::new();
1958+ let mut bytes = 0usize;
1959+ // What we believe this relay's body cap to be — `MAX_SEND_BATCH_BYTES`
1960+ // until a `413` tells us otherwise.
1961+ let batch_budget = model.send_batch_budget.unwrap_or(MAX_SEND_BATCH_BYTES);
1962+
1963+ while messages.len() < MAX_SEND_BATCH {
1964+ let Some(item) = model.outbox.get(messages.len()) else {
1965+ break;
12071966 };
1208− match encrypt_for(&id, item) {
1209− Some(blob) => break Some((item.recipient.clone(), blob)),
1210− None => {
1211− // An unusable recipient key can never be encrypted to, so the
1212− // item has to go or it blocks the head of the outbox forever —
1213− // but say so, rather than letting the message vanish.
1214− model.error = Some(format!(
1215− "cannot send to {}: invalid key",
1216− trunc_ob(&item.recipient)
1217− ));
1218− model.outbox.pop_front();
1219− dropped = true;
1220− }
1967+ if recipient.as_ref().is_some_and(|r| r != &item.recipient) {
1968+ break;
12211969 }
1222− };
1223−
1224− let persist = if dropped {
1225− self.persist_outbox(model)
1226− } else {
1227− Command::done()
1228− };
1970+ let Some(blob) = encrypt_for(&id, item) else {
1971+ // An unusable recipient key can never be encrypted to, so the item
1972+ // has to go or it blocks the head of the outbox forever — but say
1973+ // so, rather than letting the message vanish. (Only reachable at
1974+ // the head: an item deeper in the batch shares the recipient of one
1975+ // we have already encrypted to, so its key is good by construction.)
1976+ model.error = Some(format!(
1977+ "cannot send to {}: invalid key",
1978+ trunc_ob(&item.recipient)
1979+ ));
1980+ model.outbox.remove(messages.len());
1981+ dirty = true;
1982+ continue;
1983+ };
1984+ let hex_blob = hex::encode(blob);
1985+ // Always take the first item, whatever it weighs — a lone oversized
1986+ // payload must still reach the relay, which rejects it permanently
1987+ // (`400`) and so gets it out of the queue for good. Past the first,
1988+ // stop before the body outgrows what a relay will accept.
1989+ if !messages.is_empty() && bytes + hex_blob.len() > batch_budget {
1990+ break;
1991+ }
1992+ bytes += hex_blob.len();
1993+ recipient = Some(item.recipient.clone());
1994+ messages.push(Envelope {
1995+ to: item.recipient.clone(),
1996+ encrypted_blob: hex_blob,
1997+ });
1998+ }
12291999
1230− let Some((recipient, blob)) = sendable else {
2000+ let Some(recipient) = recipient else {
12312001 // Nothing left to send. Render only if we dropped something, so the
12322002 // user sees why their message went away.
1233− return if dropped {
1234− persist.and(render())
2003+ return if dirty {
2004+ self.persist_outbox(model).and(render())
12352005 } else {
12362006 Command::done()
12372007 };
12382008 };
12392009
1240− model.flushing = true;
1241− let batch = SendBatch {
1242− messages: vec![Envelope {
1243− to: recipient,
1244− encrypted_blob: hex::encode(blob),
1245− }],
2010+ // Stamp the items now going out for the first time. This is what the TTL
2011+ // in `OutboxItem::is_expired` measures from, so it has to be durable —
2012+ // otherwise a relaunch resets the clock and a permanently-stuck item is
2013+ // immortal again.
2014+ for item in model.outbox.iter_mut().take(messages.len()) {
2015+ if item.first_attempt == 0 {
2016+ item.first_attempt = now;
2017+ dirty = true;
2018+ }
2019+ }
2020+ let persist = if dirty {
2021+ self.persist_outbox(model)
2022+ } else {
2023+ Command::done()
12462024 };
2025+
2026+ model.flushing = true;
2027+ let gen = model.next_flush_gen();
2028+ model.in_flight = Some(InFlight {
2029+ recipient,
2030+ count: messages.len(),
2031+ bytes,
2032+ });
12472033 let url = format!("{}/messages", model.settings.server_url);
12482034 match Http::post(url)
12492035 .header("authorization", format!("Bearer {token}"))
1250− .body_json(&batch)
2036+ .body_json(&SendBatch { messages })
12512037 {
1252− Ok(req) => persist.and(req.build().then_send(Event::SendResult)),
2038+ Ok(req) => persist.and(req.build().then_send(move |r| Event::SendResult(gen, r)))
2039+ .and(
2040+ Time::notify_after(Duration::from_millis(FLUSH_WATCHDOG_MS))
2041+ .0
2042+ .then_send(move |_| Event::FlushWatchdog(gen)),
2043+ ),
12532044 Err(_) => {
12542045 // Not a dead loop: the next StartFlush (from a poll page or a
12552046 // fresh send) retries the head of the outbox.
12562047 model.flushing = false;
2048+ model.in_flight = None;
12572049 model.error = Some("could not build send request".into());
12582050 persist.and(render())
12592051 }
12602052 }
12612053 }
12622054
2055+ /// A send failed transiently (a 5xx, a rate limit, a dropped connection). The
2056+ /// batch stays queued and goes out again on the next `StartFlush` — but not
2057+ /// forever.
2058+ ///
2059+ /// The outbox is a strict FIFO, so an item that can never be delivered blocks
2060+ /// every message queued behind it, permanently: a single unreachable recipient
2061+ /// relay used to be enough to silence the client for good. Charge every item in
2062+ /// the failed batch a retry and drop the ones that have exhausted their budget
2063+ /// (`OutboxItem::is_expired`) — with an error, rather than letting them vanish.
2064+ fn retry_batch(&self, model: &mut Model, batch: Option<InFlight>) -> Command<Effect, Event> {
2065+ // `None` means the items were removed out from under the send (the peer was
2066+ // blocked, or deleted). There is nothing left to charge or to drop.
2067+ let Some(batch) = batch else {
2068+ return render();
2069+ };
2070+
2071+ let now = now_ms();
2072+ let mut expired = 0usize;
2073+ let mut kept: VecDeque<OutboxItem> = VecDeque::with_capacity(model.outbox.len());
2074+ for (i, mut item) in std::mem::take(&mut model.outbox).into_iter().enumerate() {
2075+ if i < batch.count {
2076+ item.retries = item.retries.saturating_add(1);
2077+ if item.is_expired(now) {
2078+ expired += 1;
2079+ continue;
2080+ }
2081+ }
2082+ kept.push_back(item);
2083+ }
2084+ model.outbox = kept;
2085+
2086+ if expired == 0 {
2087+ // Nothing dropped, but the retry counters still have to be durable: a
2088+ // relaunch that handed every stuck item a fresh budget would wedge the
2089+ // outbox across restarts exactly as it did before there was a budget.
2090+ return self.persist_outbox(model).and(render());
2091+ }
2092+ model.error = Some(format!(
2093+ "gave up sending {expired} message(s) to {}",
2094+ trunc_ob(&batch.recipient)
2095+ ));
2096+ // The head of the outbox has moved, so whatever was stuck behind the items
2097+ // we just dropped can finally go out.
2098+ self.persist_outbox(model)
2099+ .and(self.flush_next(model))
2100+ .and(render())
2101+ }
2102+
12632103 /// Decrypt and fold a poll page into the model; queue delivery acks.
12642104 fn ingest_poll(&self, model: &mut Model, page: PollResp) -> Command<Effect, Event> {
1265− if page.cursor > model.cursor {
1266− model.cursor = page.cursor;
2105+ // The caller already refuses to poll into a broken model, and must — the
2106+ // cursor write is its own, and advancing it is what acks the page. This
2107+ // stands guard for whoever calls this next: ingesting is only safe if what
2108+ // is ingested can be written down.
2109+ if model.kv_load_failed {
2110+ return Command::done();
2111+ }
2112+ let prev_cursor = model.cursor;
2113+ // Clamp the relay-supplied cursor: honest cursors are wall-clock-seeded
2114+ // sequence numbers, so anything far in the future is a hostile or buggy
2115+ // relay. Adopting `i64::MAX` would ack (delete) all queued mail on the
2116+ // next poll and persist that poison across relaunches.
2117+ let clamped_cursor = page.cursor.min(now_ms().saturating_add(60_000));
2118+ // Q16: Only advance the cursor when the page actually carried events.
2119+ // An empty page with a cursor higher than ours is suspicious — a
2120+ // compromised relay could poison the cursor to ack (delete) messages
2121+ // the client hasn't seen. When there are no events, there is nothing
2122+ // to acknowledge, so the cursor should not move. (An honest relay's
2123+ // empty-page cursor equals what the client sent, so this is a no-op
2124+ // in the normal case.)
2125+ if !page.events.is_empty() && clamped_cursor > model.cursor {
2126+ model.cursor = clamped_cursor;
12672127 }
12682128 let Some(id) = model.identity() else {
12692129 return Command::done();
12702130 };
12712131
12722132 let now = now_ms();
1273− let mut touched_convos: Vec<String> = Vec::new();
2133+ let mut touched_convos: HashSet<String> = HashSet::new();
12742134 let mut contacts_dirty = false;
2135+ let mut outbox_dirty = false;
12752136 // sender hex -> message ids needing acks
12762137 let mut ack_targets: BTreeMap<String, Vec<String>> = BTreeMap::new();
2138+ // Q17: Per-sender deferred ack accumulation. Collected during the event
2139+ // loop, applied after it — so relay page ordering cannot cause an older
2140+ // ack to be dropped as stale by a newer one processed first.
2141+ let mut pending_acks: HashMap<String, PendingAck> = HashMap::new();
12772142
12782143 let mut budget = MAX_POLL_TOTAL_BYTES;
2144+ let mut events_processed = 0usize;
2145+ // N9: Track whether any event was successfully decrypted and stored.
2146+ // When the budget/count is exhausted mid-page, we ack the page (keep
2147+ // the advanced cursor) only if at least one event was processed —
2148+ // the unprocessed tail is from a hostile/misconfigured relay and
2149+ // losing them is better than livelocking. If zero events were
2150+ // processed (a completely hostile page), restore the cursor so we
2151+ // don't ack mail we never saw.
2152+ let mut events_stored = 0usize;
12792153 for ev in page.events {
12802154 // Reject an oversized blob on its hex length, before it costs us a
12812155 // decode. No conforming sender produces one (the relay caps blobs at
@@ -1283,12 +2157,37 @@ impl Skrepka {
12832157 if ev.encrypted_blob.len() > MAX_BLOB_LEN * 2 {
12842158 continue;
12852159 }
2160+ // Event count cap: the byte budget alone permits ~388K minimum-size
2161+ // events, each costing a full decrypt attempt. A hostile relay can
2162+ // freeze the app for tens of seconds per poll with a page of small
2163+ // junk blobs. Stop processing past this count.
2164+ if events_processed >= MAX_POLL_EVENTS {
2165+ // N9: If we stored at least one event, keep the advanced cursor
2166+ // to ack the page and avoid a livelock. The unprocessed events
2167+ // are hostile junk or beyond our capacity — we can't process
2168+ // them anyway, and re-fetching them forever would wedge the
2169+ // client.
2170+ if events_stored == 0 {
2171+ model.cursor = prev_cursor;
2172+ }
2173+ model.error = Some("relay sent too many poll events".into());
2174+ break;
2175+ }
2176+ events_processed += 1;
12862177 match budget.checked_sub(ev.encrypted_blob.len() / 2) {
12872178 Some(left) => budget = left,
12882179 None => {
1289− // A page this large is a misbehaving relay, not real mail.
1290− // Stop here; the rest of the page is discarded exactly as an
1291− // undecryptable blob would be.
2180+ // N9: Budget exhausted. If we stored at least one event,
2181+ // keep the advanced cursor to ack the page — re-fetching
2182+ // an oversized page forever is a livelock. The unprocessed
2183+ // events are beyond our capacity and would be re-served
2184+ // on every poll, wedging the client. Acking them breaks
2185+ // the loop. If zero events were stored (completely hostile
2186+ // page), restore the cursor to avoid acking mail we
2187+ // never saw.
2188+ if events_stored == 0 {
2189+ model.cursor = prev_cursor;
2190+ }
12922191 model.error = Some("relay sent an oversized poll page".into());
12932192 break;
12942193 }
@@ -1302,8 +2201,23 @@ impl Skrepka {
13022201 let Some(parsed) = protocol::parse_payload(&dec.plaintext) else {
13032202 continue;
13042203 };
2204+ // D1: Any event that was successfully decrypted AND parsed counts
2205+ // as "stored" for cursor advancement — the client has processed it
2206+ // even if it was a duplicate/stale/stranger that was dropped.
2207+ events_stored += 1;
13052208 let sender = dec.sender_hex;
13062209
2210+ // Mail from ourselves. A relay cannot forge this — the sender identity
2211+ // is signed inside the AEAD — but it can *echo back* a blob we sent
2212+ // through it, and one addressed to ourselves decrypts perfectly well.
2213+ // Nothing downstream would notice: it would auto-create a contact for
2214+ // our own key (which `AddContact` explicitly refuses to do), file our
2215+ // own words as an incoming message, and queue a delivery ack addressed
2216+ // to us — which flushes, comes back, and is acked again.
2217+ if sender == model.my_pubkey {
2218+ continue;
2219+ }
2220+
13072221 // Blocking cuts the peer off entirely (PROTOCOL.md §4) — not just
13082222 // their texts. A blocked peer must not be able to rewrite their
13092223 // display name and avatar in our contact list, mark our messages
@@ -1317,8 +2231,14 @@ impl Skrepka {
13172231 // `ts` is chosen by the sender and drives conversation ordering,
13182232 // in-chat ordering, and the displayed time. Bound it to the near
13192233 // future so a peer cannot pin itself to the top of the list forever
1320− // with `ts = i64::MAX`.
1321− let ts = parsed.ts.min(now.saturating_add(MAX_FUTURE_SKEW_MS));
2234+ // with `ts = i64::MAX`, and bound it to the non-negative past so a
2235+ // malicious peer cannot make their own message invisible by dating
2236+ // it at `i64::MIN` — `insert_sorted` would put it at position 0 and
2237+ // `trim_history` would age it out first.
2238+ let ts = parsed
2239+ .ts
2240+ .max(0)
2241+ .min(now.saturating_add(MAX_FUTURE_SKEW_MS));
13222242 let known = model.contacts.contains_key(&sender);
13232243 match parsed.payload {
13242244 Payload::Text { id: msg_id, body } => {
@@ -1336,38 +2256,103 @@ impl Skrepka {
13362256 Contact::new(sender.clone(), String::new(), ts),
13372257 );
13382258 contacts_dirty = true;
2259+ // D6-app: Send our profile to the new contact so they
2260+ // see our display name and avatar, not just our @p.
2261+ let profile = Payload::Profile {
2262+ display_name: Some(model.profile.display_name.clone()),
2263+ bio: Some(model.profile.bio.clone()),
2264+ photo: model.profile.photo.clone(),
2265+ };
2266+ model.outbox.push_back(OutboxItem::profile(
2267+ sender.clone(),
2268+ Arc::new(protocol::serialize_payload(&profile, ts)),
2269+ ));
2270+ outbox_dirty = true;
13392271 }
13402272 let convo = model.messages.entry(sender.clone()).or_default();
1341− // dedup by id
1342− if !convo.iter().any(|m| m.id == msg_id) {
1343− convo.push(StoredMessage {
1344− id: msg_id.clone(),
1345− body,
1346− ts,
1347− outgoing: false,
1348− delivered: false,
1349− });
1350− convo.sort_by_key(|m| m.ts);
1351− trim_history(convo);
1352− if !touched_convos.contains(&sender) {
1353− touched_convos.push(sender.clone());
2273+ // Q18: Use the persistent per-peer dedup set from
2274+ // `model.seen_ids` (loaded from kv at startup) instead of
2275+ // deriving it from the trimmed conversation. Without this,
2276+ // a replayed blob whose `id` was aged out by `trim_history`
2277+ // (past the 1000-message cap) passes the dedup check and
2278+ // re-enters the conversation.
2279+ let id_set = model
2280+ .seen_ids
2281+ .entry(sender.clone())
2282+ .or_default();
2283+ // Also seed from the conversation in case the kv load was
2284+ // missing or partial — covers the upgrade path.
2285+ if id_set.is_empty() {
2286+ id_set.extend(convo.iter().map(|m| m.id.clone()));
2287+ }
2288+ // dedup by id — O(1) via HashSet
2289+ if !id_set.contains(&msg_id) {
2290+ // The conversation is *kept* sorted rather than re-sorted:
2291+ // a `sort_by_key` per arrival is O(n log n) on a list of up
2292+ // to `MAX_MESSAGES_PER_PEER`, every time, and a poll page
2293+ // can carry hundreds of messages.
2294+ insert_sorted(
2295+ convo,
2296+ StoredMessage {
2297+ id: msg_id.clone(),
2298+ body,
2299+ ts,
2300+ outgoing: false,
2301+ delivered: false,
2302+ },
2303+ );
2304+ id_set.insert(msg_id.clone());
2305+ // N7: Cap the dedup set so it doesn't grow without
2306+ // bound. The set is rewritten to kv on every message
2307+ // receipt, so an unbounded set makes every receipt
2308+ // slower. Keep the most recent IDs by draining excess
2309+ // from the oldest. `HashSet` has no ordering, so when
2310+ // the cap is exceeded we rebuild from the conversation
2311+ // (which is trimmed to MAX_MESSAGES_PER_PEER and
2312+ // sorted by ts) — the oldest IDs in the set that are
2313+ // no longer in the conversation are the ones to drop.
2314+ if id_set.len() > MAX_SEEN_IDS_PER_PEER {
2315+ let convo_ids: HashSet<&String> =
2316+ convo.iter().map(|m| &m.id).collect();
2317+ let excess = id_set.len() - MAX_SEEN_IDS_PER_PEER;
2318+ let to_remove: Vec<String> = id_set
2319+ .iter()
2320+ .filter(|id| !convo_ids.contains(*id))
2321+ .take(excess)
2322+ .cloned()
2323+ .collect();
2324+ for id in to_remove {
2325+ id_set.remove(&id);
2326+ }
13542327 }
2328+ trim_history(convo);
2329+ touched_convos.insert(sender.clone());
2330+ // Only ack a message we actually stored — a duplicate id
2331+ // was already acked when its first copy was ingested.
2332+ ack_targets.entry(sender.clone()).or_default().push(msg_id);
13552333 }
1356− ack_targets.entry(sender).or_default().push(msg_id);
13572334 }
13582335 Payload::DeliveryAck { ack_ids } => {
1359− if let Some(convo) = model.messages.get_mut(&sender) {
1360− let mut changed = false;
1361− for m in convo.iter_mut() {
1362− if m.outgoing && ack_ids.contains(&m.id) && !m.delivered {
1363− m.delivered = true;
1364− changed = true;
1365− }
1366− }
1367− if changed && !touched_convos.contains(&sender) {
1368− touched_convos.push(sender);
1369− }
2336+ // Q17: Defer the staleness check until after the event loop.
2337+ // Within a single page, a relay can reorder events so that a
2338+ // newer ack (higher ts) is processed before an older one. If
2339+ // we applied the watermark immediately, the older ack would be
2340+ // dropped as stale — even if it acks different message IDs.
2341+ // Instead, accumulate all ack_ids per sender and the max ts,
2342+ // then apply them in a second pass below the loop.
2343+ let prev_ts = pending_acks
2344+ .get(&sender)
2345+ .map(|p| p.ts)
2346+ .unwrap_or(0);
2347+ if ts > prev_ts {
2348+ let entry = pending_acks.entry(sender.clone()).or_default();
2349+ entry.ts = ts;
13702350 }
2351+ pending_acks
2352+ .entry(sender.clone())
2353+ .or_default()
2354+ .ids
2355+ .extend(ack_ids);
13712356 }
13722357 Payload::Profile {
13732358 display_name,
@@ -1381,20 +2366,73 @@ impl Skrepka {
13812366 let Some(c) = model.contacts.get_mut(&sender) else {
13822367 continue;
13832368 };
1384− // Ignore stale profile replays (PROTOCOL.md §4). The clamped
1385− // `ts` is what gets recorded, so a peer cannot park
1386− // `last_profile_ts` at `i64::MAX` and freeze its own profile.
2369+ // Ignore stale profile replays (PROTOCOL.md §4). The watermark
2370+ // is clamped to *now* for the same reason `last_ack_ts` is: a
2371+ // peer that parked it in the future would freeze its own
2372+ // profile, since every honest update it sent afterwards would
2373+ // read as a stale replay of itself.
2374+ //
2375+ // `>=` (not `>`): a contact's `last_profile_ts` starts at 0,
2376+ // and a first profile whose `ts` is also 0 — the default when
2377+ // the field is missing — must still be accepted. `>` would
2378+ // silently drop it, leaving the contact with no profile at all.
2379+ // A replayed profile at the same `ts` overwrites with identical
2380+ // content, which is a no-op in practice.
13872381 if ts >= c.last_profile_ts {
1388− c.display_name = display_name;
1389− c.bio = bio;
1390− c.photo = photo;
1391− c.last_profile_ts = ts;
2382+ // D13: Only update fields that are present (Some).
2383+ // An absent field (None) means "don't change".
2384+ if let Some(name) = display_name {
2385+ c.display_name = name;
2386+ }
2387+ if let Some(b) = bio {
2388+ c.bio = b;
2389+ }
2390+ if let Some(p) = photo {
2391+ c.photo = Some(p);
2392+ }
2393+ c.last_profile_ts = ts.min(now);
13922394 contacts_dirty = true;
13932395 }
13942396 }
13952397 }
13962398 }
13972399
2400+ // Q17: Apply deferred delivery acks. Collected during the event loop
2401+ // above, now applied with a single staleness check per sender using the
2402+ // highest `ts` seen — so relay page ordering cannot cause an older ack
2403+ // to be dropped as stale by a newer one processed first.
2404+ for (sender, pending) in &pending_acks {
2405+ let stale = model
2406+ .contacts
2407+ .get(sender)
2408+ .is_some_and(|c| pending.ts < c.last_ack_ts);
2409+ if stale {
2410+ continue;
2411+ }
2412+ // The watermark is clamped to *now*, not merely into the skew window:
2413+ // `ts` is the peer's to choose, and `last_ack_ts` is what every later
2414+ // ack is measured against. A single ack at `ts = i64::MAX` would
2415+ // otherwise park the watermark a minute into the future, and every
2416+ // honest ack that followed — the ones that actually mark our messages
2417+ // delivered — would read as stale and be dropped.
2418+ if let Some(c) = model.contacts.get_mut(sender) {
2419+ c.last_ack_ts = pending.ts.min(now);
2420+ contacts_dirty = true;
2421+ }
2422+ if let Some(convo) = model.messages.get_mut(sender) {
2423+ let mut changed = false;
2424+ for m in convo.iter_mut() {
2425+ if m.outgoing && pending.ids.contains(&m.id) && !m.delivered {
2426+ m.delivered = true;
2427+ changed = true;
2428+ }
2429+ }
2430+ if changed {
2431+ touched_convos.insert(sender.clone());
2432+ }
2433+ }
2434+ }
2435+
13982436 // Queue delivery acks, in batches the recipient will actually accept.
13992437 //
14002438 // `parse_payload` drops a `delivery.ack` carrying more than `MAX_ACK_IDS`
@@ -1410,11 +2448,14 @@ impl Skrepka {
14102448 let payload = Payload::DeliveryAck {
14112449 ack_ids: batch.to_vec(),
14122450 };
1413− model.outbox.push_back(OutboxItem {
1414− recipient: sender.clone(),
1415− envelope_json: protocol::serialize_payload(&payload, ack_ts),
1416− });
2451+ // Consecutive and same-recipient, so `flush_next` puts every one of
2452+ // a sender's ack batches into a single `/messages` request.
2453+ model.outbox.push_back(OutboxItem::new(
2454+ sender.clone(),
2455+ Arc::new(protocol::serialize_payload(&payload, ack_ts)),
2456+ ));
14172457 }
2458+ outbox_dirty = true;
14182459 }
14192460
14202461 // Persist everything touched.
@@ -1422,10 +2463,16 @@ impl Skrepka {
14222463 for peer in &touched_convos {
14232464 cmds.push(self.persist_messages(model, peer));
14242465 }
2466+ // Q18: Persist the dedup ID set whenever we touched conversations.
2467+ if !touched_convos.is_empty() {
2468+ cmds.push(self.persist_seen_ids(model));
2469+ }
14252470 if contacts_dirty {
14262471 cmds.push(self.persist_contacts(model));
14272472 }
1428− cmds.push(self.persist_outbox(model));
2473+ if outbox_dirty {
2474+ cmds.push(self.persist_outbox(model));
2475+ }
14292476 cmds.push(Command::event(Event::StartFlush));
14302477 Command::all(cmds)
14312478 }
@@ -1445,6 +2492,20 @@ fn backoff_ms(retries: u32) -> u64 {
14452492 (3000u64.saturating_mul(1u64 << retries.min(4))).min(30_000)
14462493}
14472494
2495+/// Insert a message into a conversation held in `ts` order.
2496+///
2497+/// `partition_point` lands *after* every message sharing the new one's `ts`, so
2498+/// ties keep arrival order — exactly what the stable `sort_by_key` this replaces
2499+/// produced, at O(log n) + a shift instead of O(n log n) on every message.
2500+///
2501+/// This is what makes "sorted by `ts`" an invariant rather than something
2502+/// `ingest_poll` restored after the fact, which is what `trim_history` has always
2503+/// assumed (it ages out the *front*) and what `view()` renders in order.
2504+fn insert_sorted(convo: &mut Vec<StoredMessage>, msg: StoredMessage) {
2505+ let pos = convo.partition_point(|m| m.ts <= msg.ts);
2506+ convo.insert(pos, msg);
2507+}
2508+
14482509/// Age out local history: keep only the most recent `MAX_MESSAGES_PER_PEER`
14492510/// messages of a conversation (PROTOCOL.md §9). Callers keep `convo` sorted by
14502511/// `ts`, so the oldest messages are at the front. The subsequent kv write
@@ -1455,31 +2516,36 @@ fn trim_history(convo: &mut Vec<StoredMessage>) {
14552516 }
14562517}
14572518
1458−/// Decode a kv `get` result into a typed value, ignoring errors / absence.
2519+/// Decode a kv `get` result into a typed value.
14592520///
1460−/// `None` conflates three different things: the key is absent (a fresh install),
1461−/// the read failed, and the bytes are present but don't deserialize. The caller
1462−/// keeps its default in all three, and the next mutation writes that default back
1463−/// — so a blob we merely *failed to read* is destroyed rather than left alone.
2521+/// Returns `Ok(Some(value))` when the key exists and deserializes, `Ok(None)`
2522+/// when the key is absent (a fresh install), and `Err` when the read itself
2523+/// failed (e.g. the file is locked or corrupt). The caller MUST NOT overwrite
2524+/// a key with a default when the read failed — the data is still on disk, and
2525+/// writing the default back destroys it. An absent key is safe to default.
14642526///
1465−/// The mitigation is upstream: every persisted type is `#[serde(default)]` (see
1466−/// `model.rs`), so adding a field can't make an old blob unreadable, which is by
1467−/// far the likeliest way this fires in practice. A genuinely corrupt blob is
1468−/// still lost. Fixing that properly means distinguishing the three cases here and
1469−/// refusing to overwrite on the third — a change to every caller and to the error
1470−/// surface, not a drive-by.
1471−fn parse_kv<T: for<'de> Deserialize<'de>>(res: KvData) -> Option<T> {
1472− let bytes = res.ok().flatten()?;
1473− serde_json::from_slice(&bytes).ok()
2527+/// The old `parse_kv` conflated read errors with absence, which meant a
2528+/// background wake while the device was locked (where `completeUnlessOpen`
2529+/// refuses to open existing files) would load an empty model, and the next
2530+/// `persist_*` would write that emptiness back over the real data.
2531+fn parse_kv<T: for<'de> Deserialize<'de>>(res: KvData) -> Result<Option<T>, ()> {
2532+ match res {
2533+ Ok(Some(bytes)) => serde_json::from_slice(&bytes)
2534+ .map(Some)
2535+ .map_err(|_| ()),
2536+ Ok(None) => Ok(None),
2537+ Err(_) => Err(()),
2538+ }
14742539}
14752540
14762541#[cfg(test)]
14772542mod tests {
14782543 use super::*;
14792544 use crate::crypto::Identity;
2545+ use crate::model::{MAX_OUTBOX_RETRIES, OUTBOX_TTL_MS};
14802546
14812547 fn with_identity() -> Model {
1482− let id = Identity::from_seed(&[3u8; 32]);
2548+ let id = Identity::from_seed(&[3u8; 32]).unwrap();
14832549 Model {
14842550 secret_key: Some(Zeroizing::new(id.secret_key.to_vec())),
14852551 my_pubkey: id.public_key_hex(),
@@ -1488,7 +2554,7 @@ mod tests {
14882554 }
14892555
14902556 fn peer_hex(seed: u8) -> String {
1491− Identity::from_seed(&[seed; 32]).public_key_hex()
2557+ Identity::from_seed(&[seed; 32]).unwrap().public_key_hex()
14922558 }
14932559
14942560 /// `Command::event` *queues* an event; it does not run it. The runtime drains
@@ -1511,7 +2577,7 @@ mod tests {
15112577
15122578 /// A poll page carrying one payload, encrypted from `sender_seed` to `me`.
15132579 fn page_from(sender_seed: u8, me: &Model, payload: &Payload, ts: i64) -> PollResp {
1514− let sender = Identity::from_seed(&[sender_seed; 32]);
2580+ let sender = Identity::from_seed(&[sender_seed; 32]).unwrap();
15152581 let recipient = Identity::from_secret_bytes(me.secret_key.as_ref().unwrap()).unwrap();
15162582 let json = protocol::serialize_payload(payload, ts);
15172583 let blob = crate::crypto::encrypt(
@@ -1536,16 +2602,905 @@ mod tests {
15362602 }
15372603 }
15382604
1539− /// PROTOCOL.md §4: a blocked peer's messages are not shown — and acking them
1540− /// would tell the blocked peer we are online and reading.
1541− #[test]
1542− fn a_blocked_senders_message_is_neither_stored_nor_acked() {
1543− let app = Skrepka;
1544− let mut m = with_identity();
1545− let peer = peer_hex(9);
1546− let mut contact = Contact::new(peer.clone(), "Bob".into(), 0);
1547− contact.blocked = true;
1548− m.contacts.insert(peer.clone(), contact);
2605+ fn queued(recipient: &str, body: &str) -> OutboxItem {
2606+ OutboxItem::new(
2607+ recipient.to_string(),
2608+ Arc::new(protocol::serialize_payload(&text(body, body), 1)),
2609+ )
2610+ }
2611+
2612+ /// The `/messages` batches a command actually puts on the wire. Reading them
2613+ /// off the effect is the only way to see what was *sent*, as opposed to what
2614+ /// the model thinks it sent.
2615+ fn sent_batches(cmd: &mut Command<Effect, Event>) -> Vec<Vec<Envelope>> {
2616+ #[derive(Deserialize)]
2617+ struct Sent {
2618+ messages: Vec<Envelope>,
2619+ }
2620+ cmd.effects()
2621+ .filter_map(|e| match e {
2622+ Effect::Http(req) if req.operation.url.ends_with("/messages") => {
2623+ serde_json::from_slice::<Sent>(&req.operation.body)
2624+ .ok()
2625+ .map(|b| b.messages)
2626+ }
2627+ _ => None,
2628+ })
2629+ .collect()
2630+ }
2631+
2632+ fn ok_response(status: u16) -> crux_http::Response<Vec<u8>> {
2633+ let status = crux_http::http::StatusCode::try_from(status).unwrap();
2634+ crux_http::testing::ResponseBuilder::with_status(status)
2635+ .body(Vec::new())
2636+ .build()
2637+ }
2638+
2639+ /// The same, plus one header — the only thing a relay can say to us beyond a
2640+ /// status code, and `Retry-After` is the one we act on.
2641+ fn response_with_header(status: u16, name: &str, value: &str) -> crux_http::Response<Vec<u8>> {
2642+ let status = crux_http::http::StatusCode::try_from(status).unwrap();
2643+ crux_http::testing::ResponseBuilder::with_status(status)
2644+ .header(name, value)
2645+ .body(Vec::new())
2646+ .build()
2647+ }
2648+
2649+ /// The delays a command actually asks the shell to wait, in milliseconds.
2650+ /// Asserting on the model alone cannot see these — a backoff lives entirely in
2651+ /// the effect.
2652+ fn scheduled_delays(cmd: &mut Command<Effect, Event>) -> Vec<u64> {
2653+ cmd.effects()
2654+ .filter_map(|e| match e {
2655+ Effect::Time(req) => match req.operation {
2656+ crux_time::TimeRequest::NotifyAfter { duration, .. } => {
2657+ Some(Duration::from(duration).as_millis() as u64)
2658+ }
2659+ _ => None,
2660+ },
2661+ _ => None,
2662+ })
2663+ .collect()
2664+ }
2665+
2666+ /// One full send round-trip: flush the outbox, then answer with `status`.
2667+ fn send_and_answer(app: &Skrepka, m: &mut Model, status: u16) {
2668+ let _ = app.update(Event::StartFlush, m);
2669+ let gen = m.flush_gen;
2670+ let _ = app.update(Event::SendResult(gen, Ok(ok_response(status))), m);
2671+ }
2672+
2673+ // -----------------------------------------------------------------------
2674+ // outbox: retry budget and TTL
2675+ // -----------------------------------------------------------------------
2676+
2677+ /// The outbox is a strict FIFO, so an item that can never be delivered used to
2678+ /// block every message queued behind it — forever.
2679+ #[test]
2680+ fn an_undeliverable_item_is_dropped_once_it_runs_out_of_retries() {
2681+ let app = Skrepka;
2682+ let mut m = with_identity();
2683+ m.token = Some("t".into());
2684+ let stuck = peer_hex(9);
2685+ let behind = peer_hex(11);
2686+ m.outbox.push_back(queued(&stuck, "wedged"));
2687+ m.outbox.push_back(queued(&behind, "stranded"));
2688+
2689+ // The relay keeps 500-ing on the head of the queue.
2690+ for i in 1..MAX_OUTBOX_RETRIES {
2691+ send_and_answer(&app, &mut m, 503);
2692+ assert_eq!(m.outbox.len(), 2, "still queued after {i} failure(s)");
2693+ assert_eq!(m.outbox[0].retries, i, "and its budget is being spent");
2694+ }
2695+
2696+ // The last one exhausts the budget: the head goes, and what was stuck
2697+ // behind it goes out.
2698+ let _ = app.update(Event::StartFlush, &mut m);
2699+ let mut cmd = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(503))), &mut m);
2700+
2701+ assert_eq!(m.outbox.len(), 1, "the undeliverable item is dropped");
2702+ assert_eq!(m.outbox[0].recipient, behind, "and the queue moves on");
2703+ assert_eq!(
2704+ sent_batches(&mut cmd).len(),
2705+ 1,
2706+ "the message behind it is sent immediately, not left for the next flush"
2707+ );
2708+ let err = m.error.expect("the user is told the message was given up on");
2709+ assert!(err.contains("gave up sending 1"), "got: {err}");
2710+ }
2711+
2712+ /// The counter alone is not enough: retries only accrue when a send is
2713+ /// attempted, so a client that goes online once a day would take a fortnight to
2714+ /// spend a ten-retry budget. The TTL bounds it in wall-clock time instead.
2715+ #[test]
2716+ fn an_item_older_than_the_ttl_is_dropped_on_its_next_failure() {
2717+ let app = Skrepka;
2718+ let mut m = with_identity();
2719+ m.token = Some("t".into());
2720+ let peer = peer_hex(9);
2721+
2722+ let mut old = queued(&peer, "ancient");
2723+ old.first_attempt = now_ms() - OUTBOX_TTL_MS - 1;
2724+ old.retries = 1; // nowhere near the retry cap
2725+ m.outbox.push_back(old);
2726+
2727+ send_and_answer(&app, &mut m, 503);
2728+
2729+ assert!(m.outbox.is_empty(), "the TTL alone is enough to drop it");
2730+ assert!(m.error.is_some_and(|e| e.contains("gave up sending")));
2731+ }
2732+
2733+ /// An item queued during a week offline must not be dropped the moment the
2734+ /// network returns: the TTL runs from the first *attempt*, not from when the
2735+ /// message was written. An outbox blob from a build with no `first_attempt`
2736+ /// field deserializes to 0, which must mean "never attempted", not "epoch".
2737+ #[test]
2738+ fn an_item_that_was_never_attempted_has_no_ttl_to_outlive() {
2739+ let item = OutboxItem::new(peer_hex(9), Arc::new("{}".into()));
2740+ assert_eq!(item.first_attempt, 0);
2741+ assert!(
2742+ !item.is_expired(now_ms()),
2743+ "an unsent item must not age out against the epoch"
2744+ );
2745+ }
2746+
2747+ /// The TTL clock has to survive a relaunch, or a permanently-stuck item is
2748+ /// handed a fresh 24 hours on every launch and the outbox wedges forever again.
2749+ #[test]
2750+ fn the_first_attempt_stamp_is_persisted_when_the_item_goes_out() {
2751+ let app = Skrepka;
2752+ let mut m = with_identity();
2753+ m.token = Some("t".into());
2754+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2755+ let before = now_ms();
2756+
2757+ let mut cmd = app.update(Event::StartFlush, &mut m);
2758+
2759+ assert!(m.outbox[0].first_attempt >= before, "the item is stamped");
2760+ // ...and the stamp is written to the `outbox` key, not just to memory.
2761+ let wrote_outbox = cmd.effects().any(|e| {
2762+ matches!(e, Effect::KeyValue(req)
2763+ if matches!(&req.operation, crux_kv::KeyValueOperation::Set { key, .. } if key == K_OUTBOX))
2764+ });
2765+ assert!(wrote_outbox, "the stamped outbox is persisted");
2766+ }
2767+
2768+ /// A transient failure below the budget changes nothing but the counter — the
2769+ /// message stays queued and goes out on the next flush.
2770+ #[test]
2771+ fn a_transient_failure_within_budget_keeps_the_message() {
2772+ let app = Skrepka;
2773+ let mut m = with_identity();
2774+ m.token = Some("t".into());
2775+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2776+
2777+ send_and_answer(&app, &mut m, 503);
2778+ assert_eq!(m.outbox.len(), 1);
2779+ assert_eq!(m.outbox[0].retries, 1);
2780+ assert!(m.error.is_none(), "a single 5xx is not worth shouting about");
2781+ assert!(!m.flushing, "and the guard is released so the next flush can run");
2782+
2783+ // The relay recovers; the message goes out and the item is gone.
2784+ send_and_answer(&app, &mut m, 200);
2785+ assert!(m.outbox.is_empty());
2786+ }
2787+
2788+ /// A 401 is not a delivery failure — it means our token expired. The batch must
2789+ /// not be charged a retry for it, or a long-lived client burns its whole budget
2790+ /// on routine re-auths.
2791+ #[test]
2792+ fn a_401_does_not_spend_the_retry_budget() {
2793+ let app = Skrepka;
2794+ let mut m = with_identity();
2795+ m.token = Some("t".into());
2796+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2797+
2798+ send_and_answer(&app, &mut m, 401);
2799+
2800+ assert_eq!(m.outbox.len(), 1, "the message is still queued");
2801+ assert_eq!(m.outbox[0].retries, 0, "and unpunished");
2802+ assert!(m.token.is_none(), "but the token is thrown away");
2803+ }
2804+
2805+ /// A 429 is the relay's load, not the message's fault. Charging the batch a
2806+ /// retry for it would let a busy relay drive perfectly good messages out of the
2807+ /// outbox — and the relay usually says exactly how long to wait, so wait that
2808+ /// long rather than guessing.
2809+ #[test]
2810+ fn a_429_waits_out_retry_after_without_spending_the_retry_budget() {
2811+ let app = Skrepka;
2812+ let mut m = with_identity();
2813+ m.token = Some("t".into());
2814+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2815+
2816+ let _ = app.update(Event::StartFlush, &mut m);
2817+ let mut cmd = app.update(
2818+ Event::SendResult(m.flush_gen, Ok(response_with_header(429, "retry-after", "2"))),
2819+ &mut m,
2820+ );
2821+
2822+ assert_eq!(m.outbox.len(), 1, "the message is still queued");
2823+ assert_eq!(m.outbox[0].retries, 0, "and unpunished — it did nothing wrong");
2824+ assert!(!m.flushing, "the guard is released so the retry can run");
2825+ assert_eq!(
2826+ scheduled_delays(&mut cmd),
2827+ vec![2_000],
2828+ "and we wait exactly as long as the relay asked"
2829+ );
2830+ }
2831+
2832+ /// Without the header there is nothing to honour, so fall back to our own
2833+ /// backoff rather than hammering the relay that just asked us to slow down.
2834+ ///
2835+ /// On the *send* loop's counter. `poll_retries` is reset by every page the poll
2836+ /// loop takes, so spending it here means a client that polls happily while the
2837+ /// relay throttles its sends restarts the send backoff at 3 s forever.
2838+ #[test]
2839+ fn a_429_without_header_uses_send_side_backoff() {
2840+ let app = Skrepka;
2841+ let mut m = with_identity();
2842+ m.token = Some("t".into());
2843+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2844+ // The poll loop is healthy and has just taken a page — exactly the state that
2845+ // used to reset the send backoff out from under itself.
2846+ m.poll_retries = 0;
2847+
2848+ let _ = app.update(Event::StartFlush, &mut m);
2849+ let mut cmd = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(429))), &mut m);
2850+
2851+ assert_eq!(m.outbox[0].retries, 0, "still not the message's fault");
2852+ assert_eq!(
2853+ scheduled_delays(&mut cmd),
2854+ vec![backoff_ms(0)],
2855+ "the first send-side backoff"
2856+ );
2857+ assert_eq!(m.send_retries, 1, "and the send loop's own counter is spent");
2858+
2859+ // A second 429 climbs, rather than restarting at 3 s.
2860+ m.flush_paused_until = 0;
2861+ let _ = app.update(Event::StartFlush, &mut m);
2862+ let mut cmd = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(429))), &mut m);
2863+ assert_eq!(scheduled_delays(&mut cmd), vec![backoff_ms(1)], "it climbs");
2864+ assert_eq!(m.send_retries, 2);
2865+ }
2866+
2867+ /// The `Retry-After` timer is not the only thing that fires `StartFlush` — a poll
2868+ /// page and a fresh `SendText` both do. Without a pause latched on the model the
2869+ /// wait is decorative: the next poll page walks through it and hammers the relay
2870+ /// that just asked us to stop.
2871+ #[test]
2872+ fn a_429_pauses_flush_until_the_delay_elapses() {
2873+ let app = Skrepka;
2874+ let mut m = with_identity();
2875+ m.token = Some("t".into());
2876+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2877+
2878+ let _ = app.update(Event::StartFlush, &mut m);
2879+ let _ = app.update(
2880+ Event::SendResult(m.flush_gen, Ok(response_with_header(429, "retry-after", "2"))),
2881+ &mut m,
2882+ );
2883+ assert!(
2884+ m.flush_paused_until > now_ms(),
2885+ "the relay's wait is latched on the model, not just on a timer"
2886+ );
2887+
2888+ // Anything else that wakes the send loop during the wait — a poll page, a new
2889+ // message — must find it closed.
2890+ let mut cmd = app.update(Event::StartFlush, &mut m);
2891+ assert!(
2892+ sent_batches(&mut cmd).is_empty(),
2893+ "nothing goes out while the relay has asked us to wait"
2894+ );
2895+ assert!(!m.flushing, "and the loop is left free to resume later");
2896+ assert_eq!(m.outbox.len(), 1, "the message is still queued");
2897+
2898+ // Time passes (the clock cannot be moved in a test, so retire the pause the
2899+ // way the elapsing of it would) and the timer's own `StartFlush` lands.
2900+ m.flush_paused_until = 0;
2901+ let mut cmd = app.update(Event::StartFlush, &mut m);
2902+ assert_eq!(
2903+ sent_batches(&mut cmd).len(),
2904+ 1,
2905+ "and once the wait is over the batch goes out"
2906+ );
2907+ }
2908+
2909+ /// A send the relay accepts means the throttle is off. Keeping the counter would
2910+ /// make the next 429 — hours later, under unrelated load — resume at whatever
2911+ /// height the last one climbed to.
2912+ #[test]
2913+ fn a_successful_send_clears_the_send_side_backoff() {
2914+ let app = Skrepka;
2915+ let mut m = with_identity();
2916+ m.token = Some("t".into());
2917+ m.send_retries = 4;
2918+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2919+
2920+ send_and_answer(&app, &mut m, 200);
2921+
2922+ assert_eq!(m.send_retries, 0, "the relay is taking our sends again");
2923+ }
2924+
2925+ /// `Retry-After` is a number a relay chooses and we obey. Unbounded, one of
2926+ /// them parks the outbox for thirty years — with nothing on screen to say why.
2927+ #[test]
2928+ fn an_absurd_retry_after_is_clamped() {
2929+ let app = Skrepka;
2930+ let mut m = with_identity();
2931+ m.token = Some("t".into());
2932+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
2933+
2934+ let _ = app.update(Event::StartFlush, &mut m);
2935+ let mut cmd = app.update(
2936+ Event::SendResult(m.flush_gen, Ok(response_with_header(429, "retry-after", "999999999"))),
2937+ &mut m,
2938+ );
2939+
2940+ assert_eq!(
2941+ scheduled_delays(&mut cmd),
2942+ vec![MAX_RETRY_AFTER_MS],
2943+ "we wait, but only as long as we are willing to"
2944+ );
2945+ }
2946+
2947+ // -----------------------------------------------------------------------
2948+ // outbox: batching
2949+ // -----------------------------------------------------------------------
2950+
2951+ /// Sending one message per request meant a round-trip per *ack* too, so
2952+ /// catching up on a hundred messages cost a hundred requests.
2953+ #[test]
2954+ fn consecutive_items_for_one_recipient_go_out_in_a_single_request() {
2955+ let app = Skrepka;
2956+ let mut m = with_identity();
2957+ m.token = Some("t".into());
2958+ let peer = peer_hex(9);
2959+ for i in 0..5 {
2960+ m.outbox.push_back(queued(&peer, &format!("m{i}")));
2961+ }
2962+
2963+ let mut cmd = app.update(Event::StartFlush, &mut m);
2964+
2965+ let batches = sent_batches(&mut cmd);
2966+ assert_eq!(batches.len(), 1, "one request, not five");
2967+ assert_eq!(batches[0].len(), 5, "carrying every message");
2968+ assert!(batches[0].iter().all(|e| e.to == peer));
2969+
2970+ // ...and its success clears the whole batch, not just the head.
2971+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
2972+ assert!(m.outbox.is_empty());
2973+ }
2974+
2975+ /// The batch stops at the first recipient change: a batch is delivered as a
2976+ /// unit, and hoisting a later item for the same peer over an earlier one for a
2977+ /// different peer would let one busy conversation starve the rest of the queue.
2978+ #[test]
2979+ fn a_batch_stops_at_the_first_recipient_change() {
2980+ let app = Skrepka;
2981+ let mut m = with_identity();
2982+ m.token = Some("t".into());
2983+ let a = peer_hex(9);
2984+ let b = peer_hex(11);
2985+ m.outbox.push_back(queued(&a, "a1"));
2986+ m.outbox.push_back(queued(&a, "a2"));
2987+ m.outbox.push_back(queued(&b, "b1"));
2988+ m.outbox.push_back(queued(&a, "a3"));
2989+
2990+ let mut cmd = app.update(Event::StartFlush, &mut m);
2991+ let batches = sent_batches(&mut cmd);
2992+ assert_eq!(batches.len(), 1);
2993+ assert_eq!(batches[0].len(), 2, "only the run at the head");
2994+ assert!(batches[0].iter().all(|e| e.to == a));
2995+
2996+ let mut cmd = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
2997+ assert_eq!(m.outbox.len(), 2);
2998+ let batches = sent_batches(&mut cmd);
2999+ assert_eq!(batches[0].len(), 1, "then b's single message");
3000+ assert_eq!(batches[0][0].to, b);
3001+ }
3002+
3003+ /// The relay answers `413 batch_too_large` past a hundred (PROTOCOL.md §7) —
3004+ /// which we would read as a transient failure and retry forever.
3005+ #[test]
3006+ fn a_batch_is_capped_at_the_relays_limit() {
3007+ let app = Skrepka;
3008+ let mut m = with_identity();
3009+ m.token = Some("t".into());
3010+ let peer = peer_hex(9);
3011+ for i in 0..(MAX_SEND_BATCH + 20) {
3012+ m.outbox.push_back(queued(&peer, &format!("m{i}")));
3013+ }
3014+
3015+ let mut cmd = app.update(Event::StartFlush, &mut m);
3016+ let batches = sent_batches(&mut cmd);
3017+ assert_eq!(batches[0].len(), MAX_SEND_BATCH);
3018+
3019+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
3020+ assert_eq!(m.outbox.len(), 20, "the rest stays queued for the next batch");
3021+ }
3022+
3023+ /// A hundred profile broadcasts each carrying a 64 KiB photo would build a
3024+ /// request far past the body-size cap a relay has by default — and the `413`
3025+ /// that came back would look transient, so we would retry it forever.
3026+ #[test]
3027+ fn a_batch_is_capped_by_body_size_as_well_as_count() {
3028+ let app = Skrepka;
3029+ let mut m = with_identity();
3030+ m.token = Some("t".into());
3031+ let peer = peer_hex(9);
3032+ // A body at the cap, and incompressible — `crypto::encrypt` deflates the
3033+ // plaintext, so a run of one character would ride out to nearly nothing and
3034+ // prove no cap at all.
3035+ let mut seed = 1u64;
3036+ let big: String = std::iter::repeat_with(|| {
3037+ seed = seed.wrapping_mul(6_364_136_223_846_793_005).wrapping_add(1);
3038+ char::from(b'a' + (seed >> 33) as u8 % 26)
3039+ })
3040+ .take(protocol::MAX_BODY_LEN)
3041+ .collect();
3042+ for i in 0..MAX_SEND_BATCH {
3043+ m.outbox.push_back(OutboxItem::new(
3044+ peer.clone(),
3045+ Arc::new(protocol::serialize_payload(&text(&format!("m{i}"), &big), 1)),
3046+ ));
3047+ }
3048+
3049+ let mut cmd = app.update(Event::StartFlush, &mut m);
3050+ let batches = sent_batches(&mut cmd);
3051+ let body: usize = batches[0].iter().map(|e| e.encrypted_blob.len()).sum();
3052+
3053+ assert!(batches[0].len() < MAX_SEND_BATCH, "the count cap is not the binding one");
3054+ assert!(!batches[0].is_empty(), "but something still goes out");
3055+ assert!(body <= MAX_SEND_BATCH_BYTES, "the body stays inside the budget");
3056+ }
3057+
3058+ /// `MAX_SEND_BATCH_BYTES` is a *guess* at a cap the protocol never publishes, and
3059+ /// a relay configured below it answers `413`. Read as a transient failure, that
3060+ /// `413` rebuilds the identical batch, is rejected identically, and repeats until
3061+ /// every item has burned its retry budget — the outbox drains without a single
3062+ /// message being delivered. So a `413` measures the cap instead of fighting it.
3063+ #[test]
3064+ fn a_413_halves_the_batch_budget_and_retries_smaller() {
3065+ let app = Skrepka;
3066+ let mut m = with_identity();
3067+ m.token = Some("t".into());
3068+ let peer = peer_hex(9);
3069+ for i in 0..5 {
3070+ m.outbox.push_back(queued(&peer, &format!("m{i}")));
3071+ }
3072+
3073+ // Nothing is known about this relay yet, so all five go out at once.
3074+ let mut cmd = app.update(Event::StartFlush, &mut m);
3075+ let first = sent_batches(&mut cmd);
3076+ assert_eq!(first[0].len(), 5, "the whole run goes out on the first attempt");
3077+ assert!(m.send_batch_budget.is_none(), "and we have assumed nothing");
3078+ let sent_bytes: usize = first[0].iter().map(|e| e.encrypted_blob.len()).sum();
3079+
3080+ // ...and the relay says that was too big.
3081+ let mut cmd = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(413))), &mut m);
3082+
3083+ assert_eq!(
3084+ m.send_batch_budget,
3085+ Some(sent_bytes / 2),
3086+ "the budget is halved against what actually failed, not against the constant"
3087+ );
3088+ assert_eq!(m.outbox.len(), 5, "a 413 delivered nothing, so nothing is popped");
3089+ assert!(
3090+ m.outbox.iter().all(|i| i.retries == 0),
3091+ "and the items are not charged for the relay being smaller than we guessed"
3092+ );
3093+
3094+ // The retry goes out at once, and it is smaller.
3095+ let second = sent_batches(&mut cmd);
3096+ assert_eq!(second.len(), 1, "retried immediately, not left for the next flush");
3097+ let shrunk = second[0].len();
3098+ assert!(shrunk < 5, "with a smaller batch, got {shrunk} items");
3099+ assert!(shrunk > 0, "but not an empty one");
3100+
3101+ // The relay takes the smaller batch, and exactly it is popped.
3102+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
3103+ assert_eq!(m.outbox.len(), 5 - shrunk, "exactly the batch that landed is gone");
3104+ assert_eq!(
3105+ m.send_batch_budget,
3106+ Some(sent_bytes / 2),
3107+ "and what we learned about the relay survives the success — its cap did not grow"
3108+ );
3109+ }
3110+
3111+ /// A batch of one cannot be split, and `flush_next` takes the first item whatever
3112+ /// it weighs — so halving the budget around a lone oversized item would rebuild
3113+ /// the same one-item batch forever, at full speed, with no retry ever charged.
3114+ /// It has to fall through to the retry budget, which is what eventually drops it.
3115+ #[test]
3116+ fn a_413_on_a_single_item_ages_out_instead_of_spinning() {
3117+ let app = Skrepka;
3118+ let mut m = with_identity();
3119+ m.token = Some("t".into());
3120+ m.outbox.push_back(queued(&peer_hex(9), "bigger than this relay allows"));
3121+
3122+ for i in 1..MAX_OUTBOX_RETRIES {
3123+ send_and_answer(&app, &mut m, 413);
3124+ assert_eq!(m.outbox.len(), 1, "still queued after {i} rejection(s)");
3125+ assert_eq!(m.outbox[0].retries, i, "and charged for each of them");
3126+ }
3127+ assert!(
3128+ m.send_batch_budget.is_none(),
3129+ "an unsplittable batch teaches us nothing about the cap"
3130+ );
3131+
3132+ send_and_answer(&app, &mut m, 413);
3133+ assert!(m.outbox.is_empty(), "the item that can never be sent is dropped");
3134+ assert!(
3135+ m.error.is_some_and(|e| e.contains("gave up sending")),
3136+ "and the user is told, rather than the message quietly vanishing"
3137+ );
3138+ }
3139+
3140+ /// What we learned is about *that relay*. A new one is entitled to a bigger cap,
3141+ /// and it will never send the `413` that would correct a budget carried over.
3142+ #[test]
3143+ fn changing_relay_forgets_the_learned_batch_budget() {
3144+ let app = Skrepka;
3145+ let mut m = with_identity();
3146+ m.send_batch_budget = Some(1024);
3147+
3148+ let _ = app.update(Event::SetServerUrl("https://other.example".into()), &mut m);
3149+
3150+ assert!(m.send_batch_budget.is_none());
3151+ }
3152+
3153+ /// An unusable key at the head still has to be discarded, batching or not —
3154+ /// and the discard must not take the rest of the queue with it.
3155+ #[test]
3156+ fn an_unsendable_head_is_dropped_and_the_batch_behind_it_still_goes_out() {
3157+ let app = Skrepka;
3158+ let mut m = with_identity();
3159+ m.token = Some("t".into());
3160+ let good = peer_hex(9);
3161+ m.outbox.push_back(queued(&hex::encode([0xabu8; 32]), "doomed"));
3162+ m.outbox.push_back(queued(&good, "fine"));
3163+ m.outbox.push_back(queued(&good, "also fine"));
3164+
3165+ let mut cmd = app.update(Event::StartFlush, &mut m);
3166+
3167+ assert_eq!(m.outbox.len(), 2, "only the unsendable item is dropped");
3168+ let batches = sent_batches(&mut cmd);
3169+ assert_eq!(batches[0].len(), 2, "and the batch behind it goes out whole");
3170+ assert!(m.error.is_some_and(|e| e.contains("invalid key")));
3171+ }
3172+
3173+ // -----------------------------------------------------------------------
3174+ // outbox: profile supersede
3175+ // -----------------------------------------------------------------------
3176+
3177+ /// A profile is state, not an event: only the newest one means anything. Five
3178+ /// quick edits used to queue five payloads per contact — each with the photo.
3179+ #[test]
3180+ fn repeated_profile_edits_supersede_rather_than_pile_up() {
3181+ let app = Skrepka;
3182+ let mut m = with_identity();
3183+ let a = peer_hex(9);
3184+ let b = peer_hex(11);
3185+ for peer in [&a, &b] {
3186+ m.contacts
3187+ .insert(peer.clone(), Contact::new(peer.clone(), String::new(), 0));
3188+ }
3189+
3190+ for name in ["One", "Two", "Three"] {
3191+ let _ = app.update(
3192+ Event::SaveProfile {
3193+ display_name: name.into(),
3194+ bio: String::new(),
3195+ photo: None,
3196+ },
3197+ &mut m,
3198+ );
3199+ }
3200+
3201+ assert_eq!(m.outbox.len(), 2, "one pending profile per contact, not three");
3202+ for item in &m.outbox {
3203+ assert!(item.is_profile());
3204+ let parsed = protocol::parse_payload(item.envelope_json.as_bytes()).unwrap();
3205+ match parsed.payload {
3206+ Payload::Profile { display_name, .. } => {
3207+ assert_eq!(display_name, Some("Three".to_string()), "and it is the latest one");
3208+ }
3209+ _ => panic!("expected a profile"),
3210+ }
3211+ }
3212+ }
3213+
3214+ /// Superseding must not reach into a payload that is already on the wire: its
3215+ /// ciphertext is built and gone, and `SendResult` pops it on success — so a
3216+ /// profile swapped in now would be dropped having never been sent.
3217+ #[test]
3218+ fn a_profile_already_in_flight_is_not_rewritten_under_the_send() {
3219+ let app = Skrepka;
3220+ let mut m = with_identity();
3221+ m.token = Some("t".into());
3222+ let peer = peer_hex(9);
3223+ m.contacts
3224+ .insert(peer.clone(), Contact::new(peer.clone(), String::new(), 0));
3225+
3226+ let _ = app.update(
3227+ Event::SaveProfile {
3228+ display_name: "Old".into(),
3229+ bio: String::new(),
3230+ photo: None,
3231+ },
3232+ &mut m,
3233+ );
3234+ // It goes out and is still in flight.
3235+ let _ = app.update(Event::StartFlush, &mut m);
3236+ assert!(m.flushing);
3237+
3238+ // A second edit lands mid-send. It must queue a *new* item rather than
3239+ // rewrite the one whose ciphertext is already gone.
3240+ let _ = app.update(
3241+ Event::SaveProfile {
3242+ display_name: "New".into(),
3243+ bio: String::new(),
3244+ photo: None,
3245+ },
3246+ &mut m,
3247+ );
3248+ assert_eq!(m.outbox.len(), 2, "the in-flight item is left alone");
3249+
3250+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
3251+ assert_eq!(m.outbox.len(), 1, "the sent one is popped");
3252+ let parsed = protocol::parse_payload(m.outbox[0].envelope_json.as_bytes()).unwrap();
3253+ match parsed.payload {
3254+ Payload::Profile { display_name, .. } => assert_eq!(
3255+ display_name, Some("New".to_string()),
3256+ "and the newer profile survives to be sent"
3257+ ),
3258+ _ => panic!("expected a profile"),
3259+ }
3260+ }
3261+
3262+ // -----------------------------------------------------------------------
3263+ // in-flight bookkeeping
3264+ // -----------------------------------------------------------------------
3265+
3266+ /// `SendResult` pops by count off the head of the outbox. If the items it sent
3267+ /// were removed from under it — the user blocked the peer mid-send — popping by
3268+ /// count anyway takes whatever slid into their place: another peer's mail.
3269+ #[test]
3270+ fn blocking_the_peer_mid_send_does_not_pop_someone_elses_messages() {
3271+ let app = Skrepka;
3272+ let mut m = with_identity();
3273+ m.token = Some("t".into());
3274+ let enemy = peer_hex(9);
3275+ let friend = peer_hex(11);
3276+ m.contacts
3277+ .insert(enemy.clone(), Contact::new(enemy.clone(), String::new(), 0));
3278+ m.outbox.push_back(queued(&enemy, "e1"));
3279+ m.outbox.push_back(queued(&enemy, "e2"));
3280+ m.outbox.push_back(queued(&friend, "f1"));
3281+
3282+ let _ = app.update(Event::StartFlush, &mut m);
3283+ assert_eq!(m.in_flight.as_ref().unwrap().count, 2);
3284+
3285+ // Blocked mid-flight: the two items in the air are dropped from the queue.
3286+ let _ = app.update(
3287+ Event::SetBlocked {
3288+ peer: enemy.clone(),
3289+ blocked: true,
3290+ },
3291+ &mut m,
3292+ );
3293+ assert_eq!(m.outbox.len(), 1);
3294+
3295+ // The send lands. It must pop nothing.
3296+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
3297+ assert_eq!(m.outbox.len(), 1, "the friend's message is untouched");
3298+ assert_eq!(m.outbox[0].recipient, friend);
3299+ }
3300+
3301+ // -----------------------------------------------------------------------
3302+ // delete contact
3303+ // -----------------------------------------------------------------------
3304+
3305+ /// Blocking only silences a peer; the entry stayed in the list forever.
3306+ #[test]
3307+ fn deleting_a_contact_forgets_the_contact_the_history_and_the_queue() {
3308+ let app = Skrepka;
3309+ let mut m = with_identity();
3310+ let peer = peer_hex(9);
3311+ let other = peer_hex(11);
3312+ for p in [&peer, &other] {
3313+ m.contacts
3314+ .insert(p.clone(), Contact::new(p.clone(), String::new(), 0));
3315+ m.messages.insert(
3316+ p.clone(),
3317+ vec![StoredMessage {
3318+ id: "m1".into(),
3319+ body: "hi".into(),
3320+ ts: 1,
3321+ outgoing: false,
3322+ delivered: false,
3323+ }],
3324+ );
3325+ m.outbox.push_back(queued(p, "queued"));
3326+ }
3327+ m.active_peer = Some(peer.clone());
3328+ m.page = Page::Chat;
3329+
3330+ let mut cmd = app.update(Event::DeleteContact { peer: peer.clone() }, &mut m);
3331+
3332+ assert!(!m.contacts.contains_key(&peer));
3333+ assert!(!m.messages.contains_key(&peer));
3334+ assert!(
3335+ m.outbox.iter().all(|i| i.recipient != peer),
3336+ "nothing more goes to a peer we have forgotten"
3337+ );
3338+ assert_eq!(m.page, Page::Conversations, "the open chat is closed");
3339+ assert!(m.active_peer.is_none());
3340+
3341+ // Everyone else is untouched.
3342+ assert!(m.contacts.contains_key(&other));
3343+ assert_eq!(m.messages[&other].len(), 1);
3344+ assert_eq!(m.outbox.len(), 1);
3345+
3346+ // The history blob is *deleted*, not left behind holding what the user just
3347+ // asked us to forget.
3348+ let deleted = cmd.effects().any(|e| {
3349+ matches!(e, Effect::KeyValue(req)
3350+ if matches!(&req.operation, crux_kv::KeyValueOperation::Delete { key } if key == &k_messages(&peer)))
3351+ });
3352+ assert!(deleted, "the messages:<peer> key is removed");
3353+ }
3354+
3355+ /// Deleting a peer we are not looking at must not throw the user out of the
3356+ /// chat they *are* looking at.
3357+ #[test]
3358+ fn deleting_another_contact_leaves_the_open_chat_alone() {
3359+ let app = Skrepka;
3360+ let mut m = with_identity();
3361+ let open = peer_hex(9);
3362+ let doomed = peer_hex(11);
3363+ for p in [&open, &doomed] {
3364+ m.contacts
3365+ .insert(p.clone(), Contact::new(p.clone(), String::new(), 0));
3366+ }
3367+ m.active_peer = Some(open.clone());
3368+ m.page = Page::Chat;
3369+
3370+ let _ = app.update(Event::DeleteContact { peer: doomed }, &mut m);
3371+
3372+ assert_eq!(m.page, Page::Chat);
3373+ assert_eq!(m.active_peer.as_deref(), Some(open.as_str()));
3374+ }
3375+
3376+ // -----------------------------------------------------------------------
3377+ // watermark clamping
3378+ // -----------------------------------------------------------------------
3379+
3380+ /// An ack at `ts = i64::MAX` used to park `last_ack_ts` a minute into the
3381+ /// future — and every honest ack that followed, the ones that actually mark our
3382+ /// messages delivered, read as stale and was dropped. A peer could silence its
3383+ /// own delivery receipts forever with one payload.
3384+ #[test]
3385+ fn a_far_future_ack_cannot_suppress_the_acks_that_follow_it() {
3386+ let app = Skrepka;
3387+ let mut m = with_identity();
3388+ let peer = peer_hex(9);
3389+ m.contacts
3390+ .insert(peer.clone(), Contact::new(peer.clone(), String::new(), 0));
3391+ m.messages.insert(
3392+ peer.clone(),
3393+ vec![StoredMessage {
3394+ id: "m1".into(),
3395+ body: "hi".into(),
3396+ ts: 1,
3397+ outgoing: true,
3398+ delivered: false,
3399+ }],
3400+ );
3401+
3402+ // The poisoned ack: acks nothing we sent, but sets the watermark.
3403+ let ack = Payload::DeliveryAck {
3404+ ack_ids: vec!["nothing".into()],
3405+ };
3406+ let page = page_from(9, &m, &ack, i64::MAX);
3407+ let _ = app.ingest_poll(&mut m, page);
3408+ assert!(
3409+ m.contacts[&peer].last_ack_ts <= now_ms(),
3410+ "the watermark cannot be pushed into the future"
3411+ );
3412+
3413+ // A perfectly ordinary ack, sent now. It must still land.
3414+ let ack = Payload::DeliveryAck {
3415+ ack_ids: vec!["m1".into()],
3416+ };
3417+ let page = page_from(9, &m, &ack, now_ms());
3418+ let _ = app.ingest_poll(&mut m, page);
3419+ assert!(
3420+ m.messages[&peer][0].delivered,
3421+ "an honest ack after a far-future one must still be honoured"
3422+ );
3423+ }
3424+
3425+ /// The same trick against `last_profile_ts`: a profile at `ts = i64::MAX` would
3426+ /// freeze the peer's own entry, since every honest update they sent afterwards
3427+ /// would read as a stale replay of itself.
3428+ #[test]
3429+ fn a_far_future_profile_cannot_freeze_the_peers_own_profile() {
3430+ let app = Skrepka;
3431+ let mut m = with_identity();
3432+ let peer = peer_hex(9);
3433+ m.contacts
3434+ .insert(peer.clone(), Contact::new(peer.clone(), String::new(), 0));
3435+
3436+ let profile = |name: &str| Payload::Profile {
3437+ display_name: Some(name.to_string()),
3438+ bio: Some(String::new()),
3439+ photo: None,
3440+ };
3441+ let page = page_from(9, &m, &profile("Far"), i64::MAX);
3442+ let _ = app.ingest_poll(&mut m, page);
3443+ let first_ts = m.contacts[&peer].last_profile_ts;
3444+ assert!(first_ts <= now_ms());
3445+
3446+ // A later profile at a greater ts must still apply — the clamping
3447+ // is what stops the far-future one from freezing the peer.
3448+ let page = page_from(9, &m, &profile("Now"), first_ts + 1);
3449+ let _ = app.ingest_poll(&mut m, page);
3450+ assert_eq!(
3451+ m.contacts[&peer].display_name, "Now",
3452+ "a later, honest profile must still apply"
3453+ );
3454+ }
3455+
3456+ // -----------------------------------------------------------------------
3457+ // conversation ordering
3458+ // -----------------------------------------------------------------------
3459+
3460+ /// The conversation is held in `ts` order rather than re-sorted per arrival.
3461+ /// `trim_history` ages out the *front*, so an out-of-order insert does not just
3462+ /// render wrong — it throws away the wrong message.
3463+ #[test]
3464+ fn messages_are_inserted_in_timestamp_order() {
3465+ let app = Skrepka;
3466+ let mut m = with_identity();
3467+ let peer = peer_hex(9);
3468+
3469+ // Arrive out of order, including a tie.
3470+ for (i, ts) in [300i64, 100, 200, 200].into_iter().enumerate() {
3471+ let page = page_from(9, &m, &text(&format!("m{i}"), "x"), ts);
3472+ let _ = app.ingest_poll(&mut m, page);
3473+ }
3474+ // ...and an outgoing message, which used to be appended blindly.
3475+ m.active_peer = Some(peer.clone());
3476+ m.compose = "mine".into();
3477+ let _ = app.update(Event::SendText, &mut m);
3478+
3479+ let convo = &m.messages[&peer];
3480+ assert!(
3481+ convo.windows(2).all(|w| w[0].ts <= w[1].ts),
3482+ "the conversation is sorted: {:?}",
3483+ convo.iter().map(|s| s.ts).collect::<Vec<_>>()
3484+ );
3485+ // Ties keep arrival order, exactly as the stable sort used to give.
3486+ let tied: Vec<&str> = convo
3487+ .iter()
3488+ .filter(|s| s.ts == 200)
3489+ .map(|s| s.id.as_str())
3490+ .collect();
3491+ assert_eq!(tied, vec!["m2", "m3"]);
3492+ }
3493+
3494+ /// PROTOCOL.md §4: a blocked peer's messages are not shown — and acking them
3495+ /// would tell the blocked peer we are online and reading.
3496+ #[test]
3497+ fn a_blocked_senders_message_is_neither_stored_nor_acked() {
3498+ let app = Skrepka;
3499+ let mut m = with_identity();
3500+ let peer = peer_hex(9);
3501+ let mut contact = Contact::new(peer.clone(), "Bob".into(), 0);
3502+ contact.blocked = true;
3503+ m.contacts.insert(peer.clone(), contact);
15493504
15503505 let page = page_from(9, &m, &text("m1", "hi"), now_ms());
15513506 let _ = app.ingest_poll(&mut m, page);
@@ -1577,8 +3532,11 @@ mod tests {
15773532 let (m, peer) = ingest_one_text_from_an_unblocked_peer();
15783533 assert_eq!(m.messages[&peer].len(), 1);
15793534 assert_eq!(m.messages[&peer][0].body, "hi");
1580− assert_eq!(m.outbox.len(), 1, "one delivery.ack is queued");
3535+ // D6-app: A profile broadcast is queued alongside the delivery.ack
3536+ // so the new contact sees our display name and avatar.
3537+ assert_eq!(m.outbox.len(), 2, "one delivery.ack + one profile queued");
15813538 assert_eq!(m.outbox[0].recipient, peer);
3539+ assert_eq!(m.outbox[1].recipient, peer);
15823540 }
15833541
15843542 /// A peer sending `ts = i64::MAX` used to pin itself to the top of the
@@ -1651,10 +3609,8 @@ mod tests {
16513609 let mut m = with_identity();
16523610 m.token = Some("t".into());
16533611 let bad = hex::encode([0xabu8; 32]); // 32 bytes, not a curve point
1654− m.outbox.push_back(OutboxItem {
1655− recipient: bad,
1656− envelope_json: "{}".into(),
1657− });
3612+ m.outbox
3613+ .push_back(OutboxItem::new(bad, Arc::new("{}".into())));
16583614
16593615 let _ = app.update(Event::StartFlush, &mut m);
16603616
@@ -1761,6 +3717,28 @@ mod tests {
17613717 assert!(m.error.is_some());
17623718 }
17633719
3720+ /// A stale error from a previous failed add is cleared on the next attempt,
3721+ /// so the AddContact form does not show an old error after the user fixes
3722+ /// the input and tries again.
3723+ #[test]
3724+ fn add_contact_clears_a_stale_error_on_success() {
3725+ let app = Skrepka;
3726+ let mut m = with_identity();
3727+ m.error = Some("invalid public key".into());
3728+
3729+ let peer = peer_hex(9);
3730+ let _ = app.update(
3731+ Event::AddContact {
3732+ input: peer.clone(),
3733+ nickname: "Bob".into(),
3734+ },
3735+ &mut m,
3736+ );
3737+
3738+ assert!(m.error.is_none(), "a successful add clears the stale error");
3739+ assert!(m.contacts.contains_key(&peer));
3740+ }
3741+
17643742 #[test]
17653743 fn send_text_enqueues_message_profile_and_outbox() {
17663744 let app = Skrepka;
@@ -1792,10 +3770,45 @@ mod tests {
17923770 let _ = app.update(Event::SendText, &mut m); // no active peer
17933771 assert!(m.outbox.is_empty());
17943772
1795− m.active_peer = Some(peer_hex(9));
1796− m.compose = " ".into();
1797− let _ = app.update(Event::SendText, &mut m); // whitespace only
1798− assert!(m.outbox.is_empty());
3773+ m.active_peer = Some(peer_hex(9));
3774+ m.compose = " ".into();
3775+ let _ = app.update(Event::SendText, &mut m); // whitespace only
3776+ assert!(m.outbox.is_empty());
3777+ }
3778+
3779+ /// The contact cap must be checked *before* mutating anything. The old
3780+ /// order cleared `compose` and inserted the message into `model.messages`
3781+ /// first, then hit the cap and returned early — losing the user's text and
3782+ /// leaving an invisible orphan conversation that was never persisted.
3783+ #[test]
3784+ fn send_text_to_a_new_peer_at_the_contact_cap_preserves_compose() {
3785+ let app = Skrepka;
3786+ let mut m = with_identity();
3787+ // Fill the contact list to the cap.
3788+ for i in 0..MAX_CONTACTS {
3789+ let k = format!("{i:064x}");
3790+ m.contacts.insert(k.clone(), Contact::new(k, String::new(), 0));
3791+ }
3792+ let new_peer = peer_hex(9);
3793+ m.active_peer = Some(new_peer.clone());
3794+ m.compose = "hello new friend".into();
3795+
3796+ let _ = app.update(Event::SendText, &mut m);
3797+
3798+ assert_eq!(
3799+ m.compose, "hello new friend",
3800+ "compose must not be cleared on rejection"
3801+ );
3802+ assert!(
3803+ m.messages.get(&new_peer).is_none_or(Vec::is_empty),
3804+ "no orphan conversation must be created"
3805+ );
3806+ assert!(m.outbox.is_empty(), "nothing must be queued");
3807+ assert!(!m.contacts.contains_key(&new_peer), "no contact created");
3808+ assert!(
3809+ m.error.as_ref().is_some_and(|e| e.contains("full")),
3810+ "the user is told why"
3811+ );
17993812 }
18003813
18013814 #[test]
@@ -1817,6 +3830,30 @@ mod tests {
18173830 assert!(vm.contacts.iter().any(|c| c.pubkey == peer && c.blocked));
18183831 }
18193832
3833+ /// Unblocking clears a stale "cannot send to a blocked contact" error, so the
3834+ /// chat error display does not persist after the user lifts the block.
3835+ #[test]
3836+ fn unblocking_clears_the_stale_send_error() {
3837+ let app = Skrepka;
3838+ let mut m = with_identity();
3839+ let peer = peer_hex(9);
3840+ let mut contact = Contact::new(peer.clone(), "Bob".into(), 0);
3841+ contact.blocked = true;
3842+ m.contacts.insert(peer.clone(), contact);
3843+ m.error = Some("cannot send to a blocked contact".into());
3844+
3845+ let _ = app.update(
3846+ Event::SetBlocked {
3847+ peer: peer.clone(),
3848+ blocked: false,
3849+ },
3850+ &mut m,
3851+ );
3852+
3853+ assert!(!m.contacts[&peer].blocked);
3854+ assert!(m.error.is_none(), "unblocking clears the stale error");
3855+ }
3856+
18203857 /// Gating ingest stops the acks we have not queued yet — but the ack for the
18213858 /// message that made the user hit "block" is already in the outbox, and an ack
18223859 /// is exactly the "we are online and reading you" signal the block exists to
@@ -1832,15 +3869,15 @@ mod tests {
18323869
18333870 // An ack to the peer we are about to block, plus unrelated mail.
18343871 for recipient in [&enemy, &friend] {
1835− m.outbox.push_back(OutboxItem {
1836− recipient: recipient.clone(),
1837− envelope_json: protocol::serialize_payload(
3872+ m.outbox.push_back(OutboxItem::new(
3873+ recipient.clone(),
3874+ Arc::new(protocol::serialize_payload(
18383875 &Payload::DeliveryAck {
18393876 ack_ids: vec!["m1".into()],
18403877 },
18413878 1,
1842− ),
1843− });
3879+ )),
3880+ ));
18443881 }
18453882
18463883 let _ = app.update(
@@ -1929,14 +3966,14 @@ mod tests {
19293966 let app = Skrepka;
19303967 let mut m = with_identity();
19313968 m.token = Some("t".into());
1932− m.flushing = true;
1933− m.outbox.push_back(OutboxItem {
1934− recipient: peer_hex(9),
1935− envelope_json: "{}".into(),
1936− });
3969+ m.outbox
3970+ .push_back(OutboxItem::new(peer_hex(9), Arc::new("{}".into())));
3971+
3972+ let _ = app.update(Event::StartFlush, &mut m);
3973+ assert!(m.flushing);
19373974
19383975 let resp = crux_http::testing::ResponseBuilder::ok().body(Vec::new()).build();
1939− let _ = app.update(Event::SendResult(Ok(resp)), &mut m);
3976+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(resp)), &mut m);
19403977
19413978 assert!(!m.flushing, "flushing must be cleared on the success path");
19423979 assert!(m.outbox.is_empty(), "the sent item is dropped from the outbox");
@@ -1947,11 +3984,10 @@ mod tests {
19473984 let app = Skrepka;
19483985 let mut m = with_identity();
19493986 m.token = Some("t".into());
1950− for _ in 0..2 {
1951− m.outbox.push_back(OutboxItem {
1952− recipient: peer_hex(9),
1953− envelope_json: "{}".into(),
1954− });
3987+ // Two different peers, or the batching would send both at once.
3988+ for seed in [9u8, 11] {
3989+ m.outbox
3990+ .push_back(OutboxItem::new(peer_hex(seed), Arc::new("{}".into())));
19553991 }
19563992 // First send goes out and marks the model as flushing.
19573993 let _ = app.update(Event::StartFlush, &mut m);
@@ -1959,7 +3995,7 @@ mod tests {
19593995
19603996 // Its success must both drop the item and let the *next* one go out.
19613997 let resp = crux_http::testing::ResponseBuilder::ok().body(Vec::new()).build();
1962− let _ = app.update(Event::SendResult(Ok(resp)), &mut m);
3998+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(resp)), &mut m);
19633999 assert_eq!(m.outbox.len(), 1);
19644000 assert!(m.flushing, "the second item is now in flight");
19654001 }
@@ -2102,6 +4138,7 @@ mod tests {
21024138 Event::LoadedProfile(Ok(None)),
21034139 Event::LoadedContacts(Ok(None)),
21044140 Event::LoadedCursor(Ok(None)),
4141+ Event::LoadedSeenIds(Ok(None)),
21054142 ]
21064143 .into_iter()
21074144 .enumerate()
@@ -2115,7 +4152,7 @@ mod tests {
21154152 assert_eq!(connects(&mut cmd), 0, "and none of them connects");
21164153 }
21174154
2118− // The fifth — and only the fifth — emits Connect.
4155+ // The sixth — and only the sixth — emits Connect.
21194156 let mut cmd = app.update(Event::LoadedOutbox(Ok(None)), &mut m);
21204157 assert_eq!(m.loads_pending, 0);
21214158 assert_eq!(connects(&mut cmd), 1, "the last load connects, exactly once");
@@ -2125,6 +4162,94 @@ mod tests {
21254162 assert_eq!(connects(&mut cmd), 0);
21264163 }
21274164
4165+ /// The sharpest edge of a failed read, and the one that costs the user real
4166+ /// messages: `ingest_poll` persists the outbox on *every* poll page, including
4167+ /// an empty one. So a single unreadable outbox — a background wake with the
4168+ /// device locked — followed by one idle poll used to write `[]` over a queue of
4169+ /// unsent mail. The client destroys the user's messages by doing nothing at all.
4170+ ///
4171+ /// A read failure is not an empty key. Nothing may be written until a launch
4172+ /// reads the key successfully.
4173+ #[test]
4174+ fn a_failed_read_never_writes_over_what_it_could_not_read() {
4175+ let app = Skrepka;
4176+ let mut m = with_identity();
4177+ m.loads_pending = STARTUP_LOADS;
4178+
4179+ let connects = |cmd: &mut Command<Effect, Event>| {
4180+ cmd.events()
4181+ .filter(|e| matches!(e, Event::Connect))
4182+ .count()
4183+ };
4184+ // Every key a command actually writes. The model's own view of what it saved
4185+ // cannot see these — the write lives entirely in the effect.
4186+ let kv_writes = |cmd: &mut Command<Effect, Event>| {
4187+ cmd.effects()
4188+ .filter_map(|e| match e {
4189+ Effect::KeyValue(req) => match &req.operation {
4190+ crux_kv::KeyValueOperation::Set { key, .. } => Some(key.clone()),
4191+ _ => None,
4192+ },
4193+ _ => None,
4194+ })
4195+ .collect::<Vec<_>>()
4196+ };
4197+
4198+ let _ = app.update(Event::LoadedSettings(Ok(None)), &mut m);
4199+ let _ = app.update(Event::LoadedProfile(Ok(None)), &mut m);
4200+ let _ = app.update(Event::LoadedContacts(Ok(None)), &mut m);
4201+ let _ = app.update(Event::LoadedCursor(Ok(None)), &mut m);
4202+ // The outbox is the one that could not be read — a background wake with the
4203+ // device locked. The model now believes it is empty; the disk says otherwise.
4204+ let mut cmd = app.update(
4205+ Event::LoadedOutbox(Err(crux_kv::error::KeyValueError::Io {
4206+ message: "device is locked".into(),
4207+ })),
4208+ &mut m,
4209+ );
4210+
4211+ assert!(m.kv_load_failed, "the model knows it has a hole in it");
4212+ assert!(m.error.is_some(), "and says so");
4213+ assert_eq!(
4214+ connects(&mut cmd),
4215+ 0,
4216+ "the last load does not connect: a poll would ack mail we cannot store"
4217+ );
4218+
4219+ // Every write path is closed, whatever tries to open it.
4220+ let mut cmd = app.update(
4221+ Event::AddContact {
4222+ input: peer_hex(9),
4223+ nickname: "n".into(),
4224+ },
4225+ &mut m,
4226+ );
4227+ assert!(
4228+ kv_writes(&mut cmd).is_empty(),
4229+ "contacts are not written over an unread model"
4230+ );
4231+
4232+ // And the regression itself. `ingest_poll` persists the outbox on every page,
4233+ // so one idle poll used to be enough to write `[]` over the queue on disk.
4234+ m.token = Some("t".into());
4235+ let resp = crux_http::testing::ResponseBuilder::ok()
4236+ .body(br#"{"events":[],"cursor":42}"#.to_vec())
4237+ .build();
4238+ let mut cmd = app.update(Event::PollResult(m.poll_gen, Ok(resp)), &mut m);
4239+ assert!(
4240+ kv_writes(&mut cmd).is_empty(),
4241+ "an empty poll writes nothing — not the outbox, not the cursor"
4242+ );
4243+
4244+ // The recovery is a relaunch, which re-runs the loads and clears the latch.
4245+ let sk = Identity::from_seed(&[3u8; 32]).unwrap().secret_key.to_vec();
4246+ let _ = app.update(Event::IdentityLoaded(sk), &mut m);
4247+ assert!(
4248+ !m.kv_load_failed,
4249+ "a fresh round of loads gets to answer for itself"
4250+ );
4251+ }
4252+
21284253 /// `Authenticate` is reachable from startup, a 401 on poll, a 401 on send and
21294254 /// a reconnect timer. Without a guard a network blip fires all of them, and
21304255 /// every token that comes back starts its own poll loop.
@@ -2224,8 +4349,8 @@ mod tests {
22244349 );
22254350
22264351 let profile = Payload::Profile {
2227− display_name: "Mallory".into(),
2228− bio: "spam".into(),
4352+ display_name: Some("Mallory".into()),
4353+ bio: Some("spam".into()),
22294354 photo: Some("aGk=".into()),
22304355 };
22314356 let page = page_from(9, &m, &profile, now_ms());
@@ -2306,8 +4431,8 @@ mod tests {
23064431 let peer = peer_hex(9);
23074432
23084433 let profile = Payload::Profile {
2309− display_name: "Mallory".into(),
2310− bio: String::new(),
4434+ display_name: Some("Mallory".into()),
4435+ bio: Some(String::new()),
23114436 photo: Some("aGk=".into()),
23124437 };
23134438 let page = page_from(9, &m, &profile, now_ms());
@@ -2322,6 +4447,43 @@ mod tests {
23224447 assert_eq!(m.contacts[&peer].display_name, "Mallory");
23234448 }
23244449
4450+ /// A relay cannot forge mail from us — the sender identity is signed inside the
4451+ /// AEAD — but it can *echo back* a blob we sent through it, and one addressed to
4452+ /// ourselves decrypts perfectly well. Nothing downstream would notice: it would
4453+ /// file our own words as incoming, put our own key in our contact list (which
4454+ /// `AddContact` explicitly refuses), and queue a delivery ack addressed to us —
4455+ /// which flushes, comes back, and is acked again.
4456+ #[test]
4457+ fn a_message_from_ourselves_is_dropped() {
4458+ let app = Skrepka;
4459+ let mut m = with_identity();
4460+ let me = Identity::from_secret_bytes(m.secret_key.as_ref().unwrap()).unwrap();
4461+
4462+ let json = protocol::serialize_payload(&text("m1", "echo"), now_ms());
4463+ let blob = crate::crypto::encrypt(
4464+ &mut rand_core::OsRng,
4465+ &me,
4466+ &me.public_key(),
4467+ json.as_bytes(),
4468+ )
4469+ .unwrap();
4470+ let page = PollResp {
4471+ events: vec![PollEvent {
4472+ encrypted_blob: hex::encode(blob),
4473+ }],
4474+ cursor: 1,
4475+ };
4476+
4477+ let _ = app.ingest_poll(&mut m, page);
4478+
4479+ assert!(
4480+ !m.contacts.contains_key(&m.my_pubkey),
4481+ "we are not our own contact"
4482+ );
4483+ assert!(m.messages.is_empty(), "and our own words are not incoming mail");
4484+ assert!(m.outbox.is_empty(), "and we do not ack ourselves");
4485+ }
4486+
23254487 /// `polling` gates the whole long-poll loop and is cleared only by a
23264488 /// `PollResult`. If the shell ever drops the HTTP effect, the client goes
23274489 /// silent forever with no visible error.
@@ -2482,7 +4644,7 @@ mod tests {
24824644
24834645 // One page holding more messages from one sender than fits in a single ack.
24844646 let count = protocol::MAX_ACK_IDS + 5;
2485− let sender = Identity::from_seed(&[9u8; 32]);
4647+ let sender = Identity::from_seed(&[9u8; 32]).unwrap();
24864648 let me = Identity::from_secret_bytes(m.secret_key.as_ref().unwrap()).unwrap();
24874649 let events = (0..count)
24884650 .map(|i| {
@@ -2532,4 +4694,334 @@ mod tests {
25324694 assert_eq!(vm.my_pubkey_hex, m.my_pubkey);
25334695 assert_eq!(vm.my_pubkey_ob.split('-').count(), 16);
25344696 }
4697+
4698+ /// A replayed delivery.ack with an older `ts` must be dropped, and
4699+ /// `last_ack_ts` must not regress — otherwise a relay re-delivering an old
4700+ /// page could flip messages back to "not delivered" or keep a stale ack live.
4701+ #[test]
4702+ fn a_replayed_delivery_ack_is_ignored() {
4703+ let app = Skrepka;
4704+ let mut m = with_identity();
4705+ let peer = peer_hex(9);
4706+ let mut contact = Contact::new(peer.clone(), "Bob".into(), 0);
4707+ contact.last_ack_ts = 100;
4708+ m.contacts.insert(peer.clone(), contact);
4709+ m.messages.insert(
4710+ peer.clone(),
4711+ vec![StoredMessage {
4712+ id: "m1".into(),
4713+ body: "hi".into(),
4714+ ts: 50,
4715+ outgoing: true,
4716+ delivered: false,
4717+ }],
4718+ );
4719+
4720+ // An ack with ts = 50 (< 100) is stale → ignored.
4721+ let ack = Payload::DeliveryAck {
4722+ ack_ids: vec!["m1".into()],
4723+ };
4724+ let page = page_from(9, &m, &ack, 50);
4725+ let _ = app.ingest_poll(&mut m, page);
4726+ assert!(
4727+ !m.messages[&peer][0].delivered,
4728+ "a stale ack must not mark the message delivered"
4729+ );
4730+ assert_eq!(
4731+ m.contacts[&peer].last_ack_ts, 100,
4732+ "last_ack_ts must not regress"
4733+ );
4734+
4735+ // An ack with ts = 200 (> 100) passes → message is marked delivered.
4736+ let ack = Payload::DeliveryAck {
4737+ ack_ids: vec!["m1".into()],
4738+ };
4739+ let page = page_from(9, &m, &ack, 200);
4740+ let _ = app.ingest_poll(&mut m, page);
4741+ assert!(
4742+ m.messages[&peer][0].delivered,
4743+ "a fresh ack must mark the message delivered"
4744+ );
4745+ assert_eq!(
4746+ m.contacts[&peer].last_ack_ts, 200,
4747+ "last_ack_ts advances to the fresh ack's ts"
4748+ );
4749+ }
4750+
4751+ // -----------------------------------------------------------------------
4752+ // cursor restoration on budget exhaustion
4753+ // -----------------------------------------------------------------------
4754+
4755+ /// The cursor is advanced to `page.cursor` before the event loop runs. If the
4756+ /// poll-byte budget is exhausted mid-page, the loop breaks — but the cursor
4757+ /// must be restored to its pre-page value. Otherwise the next poll acks the
4758+ /// whole page to the relay, which deletes every event we skipped: permanent
4759+ /// message loss.
4760+ #[test]
4761+ fn a_budget_exhausted_mid_page_restores_the_cursor() {
4762+ let app = Skrepka;
4763+ let mut m = with_identity();
4764+ let peer = peer_hex(9);
4765+ m.contacts
4766+ .insert(peer.clone(), Contact::new(peer.clone(), String::new(), 0));
4767+ m.cursor = 100;
4768+
4769+ // Two blobs, each at the per-blob ceiling (MAX_BLOB_LEN hex chars =
4770+ // MAX_BLOB_LEN/2 decoded bytes = 21 MiB). Individually they pass the
4771+ // per-blob size gate; together they exceed the 64 MiB page budget.
4772+ // The first passes the budget check (21 < 64) and fails decrypt (it's
4773+ // not a real blob); the second fails the budget check (21 + 21 + 21 > 64).
4774+ // Three blobs to be sure: 3 × 21 = 63 MiB (just under 64), so use four.
4775+ let big_hex = "ab".repeat(MAX_BLOB_LEN); // MAX_BLOB_LEN hex chars = MAX_BLOB_LEN/2 bytes
4776+ let page = PollResp {
4777+ events: (0..4)
4778+ .map(|_| PollEvent {
4779+ encrypted_blob: big_hex.clone(),
4780+ })
4781+ .collect(),
4782+ cursor: 200,
4783+ };
4784+ let _ = app.ingest_poll(&mut m, page);
4785+
4786+ assert_eq!(
4787+ m.cursor, 100,
4788+ "the cursor must be restored — the page was not fully processed"
4789+ );
4790+ assert!(
4791+ m.error.as_ref().is_some_and(|e| e.contains("oversized")),
4792+ "the user is told"
4793+ );
4794+ assert!(
4795+ m.messages.get(&peer).is_none_or(Vec::is_empty),
4796+ "nothing was stored from the oversized page"
4797+ );
4798+ }
4799+
4800+ // -----------------------------------------------------------------------
4801+ // send_text block check
4802+ // -----------------------------------------------------------------------
4803+
4804+ // -----------------------------------------------------------------------
4805+ // send_text body length check
4806+ // -----------------------------------------------------------------------
4807+
4808+ /// Blocking cuts a peer off in both directions. `send_text` must refuse to
4809+ /// enqueue a message to a blocked contact — otherwise the block only stops
4810+ /// their incoming mail while we keep sending them ours.
4811+ #[test]
4812+ fn send_text_to_a_blocked_peer_is_refused() {
4813+ let app = Skrepka;
4814+ let mut m = with_identity();
4815+ let peer = peer_hex(9);
4816+ let mut contact = Contact::new(peer.clone(), "Enemy".into(), 0);
4817+ contact.blocked = true;
4818+ m.contacts.insert(peer.clone(), contact);
4819+ m.active_peer = Some(peer.clone());
4820+ m.compose = "hello?".into();
4821+
4822+ let _ = app.update(Event::SendText, &mut m);
4823+
4824+ assert!(
4825+ m.outbox.is_empty(),
4826+ "no message is queued for a blocked peer"
4827+ );
4828+ assert!(
4829+ m.error.as_ref().is_some_and(|e| e.contains("blocked")),
4830+ "the user is told why"
4831+ );
4832+ // The compose buffer is not cleared — the user might want to unblock
4833+ // and resend, and losing their draft would be surprising.
4834+ assert_eq!(m.compose, "hello?");
4835+ }
4836+
4837+ /// A text body over `MAX_BODY_LEN` would be stored locally and sent to the
4838+ /// relay, but the recipient's `parse_payload` silently drops oversized text.
4839+ /// The sender would see it stuck as "sent" forever with no error.
4840+ #[test]
4841+ fn send_text_refuses_an_oversized_body() {
4842+ let app = Skrepka;
4843+ let mut m = with_identity();
4844+ let peer = peer_hex(9);
4845+ m.active_peer = Some(peer.clone());
4846+ m.compose = "x".repeat(protocol::MAX_BODY_LEN + 1);
4847+
4848+ let _ = app.update(Event::SendText, &mut m);
4849+
4850+ assert!(m.outbox.is_empty(), "nothing is queued");
4851+ assert!(m.messages.get(&peer).is_none_or(Vec::is_empty), "nothing stored");
4852+ assert!(!m.compose.is_empty(), "compose is preserved");
4853+ assert!(m.error.as_ref().is_some_and(|e| e.contains("too long")));
4854+ }
4855+
4856+ /// A stale error from a previous failed send must be cleared on the next
4857+ /// attempt, so the error display does not persist after the user fixes the
4858+ /// issue and sends again successfully.
4859+ #[test]
4860+ fn send_text_clears_a_stale_error_on_success() {
4861+ let app = Skrepka;
4862+ let mut m = with_identity();
4863+ let peer = peer_hex(9);
4864+ m.active_peer = Some(peer.clone());
4865+ // Simulate a prior failure that left an error behind.
4866+ m.error = Some("message too long".into());
4867+
4868+ m.compose = "hello".into();
4869+ let _ = app.update(Event::SendText, &mut m);
4870+
4871+ assert!(m.error.is_none(), "a successful send clears the stale error");
4872+ assert!(!m.outbox.is_empty(), "the message was queued");
4873+ }
4874+
4875+ // -----------------------------------------------------------------------
4876+ // SaveProfile field length checks
4877+ // -----------------------------------------------------------------------
4878+
4879+ #[test]
4880+ fn save_profile_rejects_an_oversized_display_name() {
4881+ let app = Skrepka;
4882+ let mut m = with_identity();
4883+
4884+ let _ = app.update(Event::SaveProfile {
4885+ display_name: "x".repeat(protocol::MAX_DISPLAY_NAME_LEN + 1),
4886+ bio: String::new(),
4887+ photo: None,
4888+ }, &mut m);
4889+
4890+ assert!(m.outbox.is_empty(), "no broadcast queued");
4891+ assert!(m.profile.display_name.is_empty(), "local profile not updated");
4892+ assert!(m.error.as_ref().is_some_and(|e| e.contains("display name")));
4893+ }
4894+
4895+ #[test]
4896+ fn save_profile_rejects_an_oversized_bio() {
4897+ let app = Skrepka;
4898+ let mut m = with_identity();
4899+
4900+ let _ = app.update(Event::SaveProfile {
4901+ display_name: "Alice".into(),
4902+ bio: "x".repeat(protocol::MAX_BIO_LEN + 1),
4903+ photo: None,
4904+ }, &mut m);
4905+
4906+ assert!(m.outbox.is_empty(), "no broadcast queued");
4907+ assert!(m.profile.bio.is_empty(), "local profile not updated");
4908+ assert!(m.error.as_ref().is_some_and(|e| e.contains("bio")));
4909+ }
4910+
4911+ #[test]
4912+ fn save_profile_rejects_an_oversized_photo() {
4913+ let app = Skrepka;
4914+ let mut m = with_identity();
4915+
4916+ let _ = app.update(Event::SaveProfile {
4917+ display_name: "Alice".into(),
4918+ bio: String::new(),
4919+ photo: Some("x".repeat(protocol::MAX_PHOTO_LEN + 1)),
4920+ }, &mut m);
4921+
4922+ assert!(m.outbox.is_empty(), "no broadcast queued");
4923+ assert!(m.profile.photo.is_none(), "local profile not updated");
4924+ assert!(m.error.as_ref().is_some_and(|e| e.contains("photo")));
4925+ }
4926+
4927+ // -----------------------------------------------------------------------
4928+ // AddContact nickname length check
4929+ // -----------------------------------------------------------------------
4930+
4931+ #[test]
4932+ fn add_contact_rejects_an_oversized_nickname() {
4933+ let app = Skrepka;
4934+ let mut m = with_identity();
4935+ let peer = peer_hex(9);
4936+
4937+ let _ = app.update(Event::AddContact {
4938+ input: peer.clone(),
4939+ nickname: "x".repeat(protocol::MAX_DISPLAY_NAME_LEN + 1),
4940+ }, &mut m);
4941+
4942+ assert!(!m.contacts.contains_key(&peer), "no contact created");
4943+ assert!(m.error.as_ref().is_some_and(|e| e.contains("nickname")));
4944+ }
4945+
4946+ // -----------------------------------------------------------------------
4947+ // FlushWatchdog unsticks a wedged send loop
4948+ // -----------------------------------------------------------------------
4949+
4950+ /// `flushing` is only cleared by `SendResult`. If the shell drops the HTTP
4951+ /// effect, the outbox is permanently stuck. The watchdog releases the guard
4952+ /// so the flush retries.
4953+ #[test]
4954+ fn the_flush_watchdog_unwedges_a_send_that_never_resolved() {
4955+ let app = Skrepka;
4956+ let mut m = with_identity();
4957+ m.token = Some("t".into());
4958+ let peer = peer_hex(9);
4959+ m.outbox.push_back(queued(&peer, "stuck"));
4960+
4961+ let _ = app.update(Event::StartFlush, &mut m);
4962+ assert!(m.flushing, "the send is in flight");
4963+ assert!(m.in_flight.is_some());
4964+
4965+ // The send never comes back. The watchdog fires, clears the stuck guard,
4966+ // and retries the flush — the message goes out again.
4967+ let mut cmd = app.update(Event::FlushWatchdog(m.flush_gen), &mut m);
4968+
4969+ assert!(m.flushing, "a fresh send is in flight (the retry)");
4970+ assert!(m.in_flight.is_some(), "in_flight is set for the retry");
4971+ let batches = sent_batches(&mut cmd);
4972+ assert_eq!(batches.len(), 1, "the message is re-sent");
4973+ }
4974+
4975+ /// A watchdog that fires after the send already completed is a no-op.
4976+ #[test]
4977+ fn a_stale_flush_watchdog_leaves_a_completed_send_alone() {
4978+ let app = Skrepka;
4979+ let mut m = with_identity();
4980+ m.token = Some("t".into());
4981+ m.outbox.push_back(queued(&peer_hex(9), "hi"));
4982+
4983+ let _ = app.update(Event::StartFlush, &mut m);
4984+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
4985+ assert!(!m.flushing);
4986+ assert!(m.outbox.is_empty());
4987+
4988+ // The watchdog for the completed send fires late.
4989+ let _ = app.update(Event::FlushWatchdog(m.flush_gen), &mut m);
4990+ assert!(!m.flushing, "a completed send is not re-armed");
4991+ assert!(m.outbox.is_empty());
4992+ }
4993+
4994+ /// A late `SendResult` from a superseded send is dropped by the generation
4995+ /// check. The watchdog abandoned the first send and retried under a new
4996+ /// generation; the late result's generation no longer matches, so it cannot
4997+ /// pop the retry's items or clear its guard. The retry's own `SendResult`
4998+ /// is what eventually pops them.
4999+ #[test]
5000+ fn a_late_send_result_after_the_watchdog_is_dropped_by_generation() {
5001+ let app = Skrepka;
5002+ let mut m = with_identity();
5003+ m.token = Some("t".into());
5004+ let peer = peer_hex(9);
5005+ m.outbox.push_back(queued(&peer, "stuck"));
5006+
5007+ let _ = app.update(Event::StartFlush, &mut m);
5008+ let first_gen = m.flush_gen;
5009+ // The watchdog fires and retries the flush under a new generation.
5010+ let _ = app.update(Event::FlushWatchdog(first_gen), &mut m);
5011+ assert_eq!(m.outbox.len(), 1, "the item is still queued (re-sent)");
5012+ assert_ne!(m.flush_gen, first_gen, "the generation was bumped");
5013+ assert!(m.flushing, "the retry is in flight");
5014+
5015+ // The original send's result arrives late. Its generation no longer
5016+ // matches, so it is dropped — it cannot pop the retry's items or
5017+ // clear the retry's guard.
5018+ let _ = app.update(Event::SendResult(first_gen, Ok(ok_response(200))), &mut m);
5019+ assert!(m.flushing, "the retry's guard is untouched");
5020+ assert_eq!(m.outbox.len(), 1, "the late result popped nothing");
5021+
5022+ // The retry's own result arrives and pops the items.
5023+ let _ = app.update(Event::SendResult(m.flush_gen, Ok(ok_response(200))), &mut m);
5024+ assert!(m.outbox.is_empty(), "the retry's result pops the items");
5025+ assert!(!m.flushing, "and the guard is released");
5026+ }
25355027}
core/src/crypto.rs+413−80
@@ -15,25 +15,89 @@
1515
1616use std::io::Read;
1717
18−use chacha20poly1305::aead::Aead;
18+use chacha20poly1305::aead::{Aead, Payload as AeadPayload};
1919use chacha20poly1305::{Key, KeyInit, XChaCha20Poly1305, XNonce};
2020use curve25519_dalek::edwards::CompressedEdwardsY;
21−use ed25519_dalek::{Signer, SigningKey, Verifier, VerifyingKey};
21+use ed25519_dalek::{Signer, SigningKey, VerifyingKey};
2222use hkdf::Hkdf;
2323use rand_core::{CryptoRng, RngCore};
2424use sha2::{Digest, Sha256, Sha512};
2525use zeroize::{Zeroize, ZeroizeOnDrop, Zeroizing};
2626
27−/// HKDF `info` string (PROTOCOL.md §3 / Constants.hkdfInfo). Fixed.
28−const HKDF_INFO: &[u8] = b"skrepka-v1";
27+/// HKDF `info` string (PROTOCOL.md §3). Derived from the wire version so a
28+/// future crypto revision that bumps the version byte also changes the KDF
29+/// label automatically — the two must always move together (N2).
30+const HKDF_INFO: &[u8] = b"skrepka-v2";
2931/// Domain-separation tag for the auth challenge signature (PROTOCOL.md §6).
3032const AUTH_TAG: &str = "skrepka-auth-v1:";
3133
34+/// Domain-separation tag for per-message signatures (PROTOCOL.md §3).
35+/// Prevents cross-protocol signature reuse: an auth challenge signature
36+/// begins with "skrepka-auth-v1:" while a message signature begins with
37+/// this tag, so the same key cannot sign in one context and have it
38+/// validate in another.
39+const MSG_TAG: &[u8] = b"skrepka-msg-v2:";
40+
41+/// Wire-format version byte prepended to every encrypted blob (PROTOCOL.md §3).
42+///
43+/// Version 0x02 adds AEAD associated data (AAD): the cleartext header
44+/// `version_byte || ephemeral_public || nonce` is authenticated alongside
45+/// the ciphertext, so a relay that tampers with any envelope field —
46+/// including swapping the `to` recipient — causes AEAD decryption to fail
47+/// before the blob is ever acked (N1). The recipient's Ed25519 public key
48+/// is also included in the AAD, binding the envelope `to` field to the
49+/// inner signed recipient, so a `to`-swap is detected as an AEAD failure
50+/// rather than a silent misdelivery.
51+const WIRE_VERSION: u8 = 2;
52+
53+/// Build the AAD for AEAD: `version || ephemeral_pub || nonce || recipient_pub`.
54+/// All envelope-level fields the relay can see are now cryptographically
55+/// bound to the ciphertext (N1).
56+fn aad(version: u8, eph_pub: &[u8; 32], nonce: &[u8; NONCE_LEN], recipient_pub: &[u8; 32]) -> Vec<u8> {
57+ let mut aad = Vec::with_capacity(1 + 32 + NONCE_LEN + 32);
58+ aad.push(version);
59+ aad.extend_from_slice(eph_pub);
60+ aad.extend_from_slice(nonce);
61+ aad.extend_from_slice(recipient_pub);
62+ aad
63+}
64+
3265pub const ED25519_SECRET_LEN: usize = 64;
3366pub const ED25519_PUBLIC_LEN: usize = 32;
3467pub const NONCE_LEN: usize = 24;
35−/// 32 (eph) + 24 (nonce) + 32 (sender pub) + 64 (sig) + 16 (AEAD tag).
36−pub const MIN_BLOB_LEN: usize = 32 + NONCE_LEN + 32 + 64 + 16;
68+/// `1+32+24+32+64+4+16` bytes = version, eph pubkey, nonce, sender pub, sig,
69+/// compressed_len, AEAD tag. The 4-byte compressed_len field sits inside the AEAD
70+/// ciphertext. The version byte, ephemeral pubkey, nonce, and recipient pubkey are
71+/// AEAD AAD (v0x02).
72+pub const MIN_BLOB_LEN: usize = 1 + 32 + NONCE_LEN + 32 + 64 + 4 + 16;
73+
74+/// Blob sizes are padded up to these boundaries so the on-wire length does not
75+/// reveal the exact plaintext (compressed) size to relays and network observers.
76+/// Below 65536 we round up to the nearest bucket; above it we round to the next
77+/// multiple of 65536 (MAX_BLOB_LEN is exactly 672 × 65536, so we never exceed it).
78+const PADDING_BUCKETS: [usize; 9] = [256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536];
79+
80+/// Round `actual` up to the nearest padding boundary.
81+fn padded_len(actual: usize) -> usize {
82+ if actual == 0 {
83+ return PADDING_BUCKETS[0];
84+ }
85+ for &bucket in &PADDING_BUCKETS {
86+ if actual <= bucket {
87+ return bucket;
88+ }
89+ }
90+ // Above 65536: round to the next multiple of 65536.
91+ let remainder = actual % 65536;
92+ if remainder == 0 {
93+ // D6: When actual is an exact multiple of 65536 above 65536,
94+ // returning `actual` would give zero padding, revealing the exact
95+ // compressed size. Always add at least one bucket of padding.
96+ actual + 65536
97+ } else {
98+ actual + 65536 - remainder
99+ }
100+}
37101/// Upper bound on a blob we will even attempt to decrypt, in *decoded* bytes —
38102/// rejected on length before it costs us a scalar mult or an AEAD pass.
39103///
@@ -98,9 +162,17 @@ impl std::error::Error for CryptoError {}
98162///
99163/// `ZeroizeOnDrop` wipes the seed when the value goes away. `Identity` is cloned
100164/// freely (once per encrypt/decrypt), so each of those copies is wiped too.
165+///
166+/// The derived X25519 keys (`x25519_priv`, `x25519_pub`) are computed once at
167+/// construction and cached: `decrypt` is called per-blob in a poll page, and
168+/// recomputing the SHA-512 + Edwards decompress on every call is a measurable
169+/// CPU multiplier under a flood of small blobs. Both are `Zeroizing` so the
170+/// private half is wiped on drop alongside the seed.
101171#[derive(Clone, ZeroizeOnDrop)]
102172pub struct Identity {
103173 pub secret_key: [u8; ED25519_SECRET_LEN],
174+ x25519_priv: [u8; 32],
175+ x25519_pub: [u8; 32],
104176}
105177
106178impl Identity {
@@ -125,24 +197,24 @@ impl Identity {
125197 return Err(CryptoError::BadKeyLength);
126198 }
127199
128− Ok(Identity { secret_key })
200+ Identity::with_x25519(secret_key)
129201 }
130202
131203 /// Generate a fresh identity from a CSPRNG.
132− pub fn generate(rng: &mut (impl RngCore + CryptoRng)) -> Self {
204+ pub fn generate(rng: &mut (impl RngCore + CryptoRng)) -> Result<Self, CryptoError> {
133205 let mut seed = Zeroizing::new([0u8; 32]);
134206 rng.fill_bytes(&mut *seed);
135207 Self::from_seed(&seed)
136208 }
137209
138210 /// Build the 64-byte secret key (`seed || pub`) from a 32-byte seed.
139− pub fn from_seed(seed: &[u8; 32]) -> Self {
211+ pub fn from_seed(seed: &[u8; 32]) -> Result<Self, CryptoError> {
140212 let signing = SigningKey::from_bytes(seed);
141213 let public = signing.verifying_key();
142214 let mut secret_key = [0u8; ED25519_SECRET_LEN];
143215 secret_key[..32].copy_from_slice(seed);
144216 secret_key[32..].copy_from_slice(public.as_bytes());
145− Identity { secret_key }
217+ Identity::with_x25519(secret_key)
146218 }
147219
148220 pub fn public_key(&self) -> [u8; ED25519_PUBLIC_LEN] {
@@ -161,6 +233,46 @@ impl Identity {
161233 SigningKey::from_bytes(&seed)
162234 }
163235
236+ /// Compute the cached X25519 keys from the Ed25519 secret key.
237+ ///
238+ /// Q49: Also checks that the derived X25519 public key is not an all-zero
239+ /// (low-order) point. The probability of generating such a key is negligible,
240+ /// but if it ever happened every encryption to this identity would fail with
241+ /// `InvalidEphemeralKey` and the user would be unable to receive messages
242+ /// with no indication of why. Catching it at construction time gives a
243+ /// clear error instead.
244+ fn with_x25519(secret_key: [u8; ED25519_SECRET_LEN]) -> Result<Self, CryptoError> {
245+ let x25519_priv = *ed25519_sk_to_x25519(&secret_key);
246+ let x25519_pub = x25519_dalek::x25519(x25519_priv, x25519_dalek::X25519_BASEPOINT_BYTES);
247+ // D33: Return an error instead of just printing a warning when the
248+ // derived X25519 public key is all-zero (low-order point). The
249+ // probability of generating such a key is negligible, but if it ever
250+ // happened every encryption to this identity would fail with
251+ // `InvalidEphemeralKey` and the user would be unable to receive
252+ // messages with no indication of why. Catching it at construction time
253+ // gives a clear error instead.
254+ if x25519_pub.iter().all(|b| *b == 0) {
255+ return Err(CryptoError::InvalidPublicKey);
256+ }
257+ Ok(Identity {
258+ secret_key,
259+ x25519_priv,
260+ x25519_pub,
261+ })
262+ }
263+
264+ /// Cached X25519 private key derived from the Ed25519 seed (libsodium
265+ /// `crypto_sign_ed25519_sk_to_curve25519`). Avoids a per-decrypt SHA-512.
266+ fn x25519_private(&self) -> &[u8; 32] {
267+ &self.x25519_priv
268+ }
269+
270+ /// Cached X25519 public key derived from the Ed25519 public key (libsodium
271+ /// `crypto_sign_ed25519_pk_to_curve25519`). Avoids a per-decrypt decompress.
272+ fn x25519_public(&self) -> &[u8; 32] {
273+ &self.x25519_pub
274+ }
275+
164276 /// Sign the auth challenge: `ed25519(sk, "skrepka-auth-v1:" + host + ":" + challenge)`.
165277 /// `server_host` must already be the bare lowercased hostname.
166278 ///
@@ -182,7 +294,14 @@ fn ed25519_pk_to_x25519(ed_pub: &[u8; 32]) -> Result<[u8; 32], CryptoError> {
182294 let point = compressed
183295 .decompress()
184296 .ok_or(CryptoError::InvalidPublicKey)?;
185− Ok(point.to_montgomery().to_bytes())
297+ let montgomery = point.to_montgomery().to_bytes();
298+ // D3: A 32-byte all-zero input is the Ed25519 identity point, which
299+ // produces an all-zero Montgomery u-coordinate — a low-order point.
300+ // Reject it explicitly, separate from the x25519 shared-secret check.
301+ if montgomery.iter().all(|&b| b == 0) {
302+ return Err(CryptoError::InvalidPublicKey);
303+ }
304+ Ok(montgomery)
186305}
187306
188307/// libsodium `crypto_sign_ed25519_sk_to_curve25519`: clamp(SHA-512(seed)[..32]).
@@ -213,7 +332,7 @@ fn x25519(scalar: &[u8; 32], point: &[u8; 32]) -> Result<Zeroizing<[u8; 32]>, Cr
213332 Ok(shared)
214333}
215334
216−/// HKDF-SHA256(ikm=raw_secret, salt=eph_pub || recip_x_pub, info="skrepka-v1", 32).
335+/// HKDF-SHA256(ikm=raw_secret, salt=eph_pub || recip_x_pub, info="skrepka-v2", 32).
217336fn derive_key(
218337 raw_secret: &[u8; 32],
219338 eph_pub: &[u8; 32],
@@ -231,7 +350,7 @@ fn derive_key(
231350
232351fn compress(plaintext: &[u8]) -> Vec<u8> {
233352 // zstd frame with embedded content size; decodable without a capacity hint.
234− zstd::encode_all(plaintext, 0).expect("zstd compression is infallible for in-memory input")
353+ zstd::encode_all(plaintext, 3).expect("zstd compression is infallible for in-memory input")
235354}
236355
237356/// Decompress a zstd frame, refusing to produce more than `MAX_PLAINTEXT_LEN`.
@@ -242,7 +361,15 @@ fn compress(plaintext: &[u8]) -> Vec<u8> {
242361/// *would* overrun is detected rather than silently truncated.
243362fn decompress(data: &[u8]) -> Result<Vec<u8>, CryptoError> {
244363 let mut decoder = zstd::stream::Decoder::new(data).map_err(|_| CryptoError::Decompress)?;
245− let mut out = Vec::new();
364+ // Cap the decoder's window buffer so a crafted frame declaring a huge
365+ // windowLog (up to 27 = 128 MiB by default) cannot force a matching
366+ // allocation before the output-size cap even applies. 2^21 = 2 MiB is
367+ // comfortably above `MAX_PLAINTEXT_LEN` (1 MiB), so every legitimate frame
368+ // still decodes; frames declaring a larger window are rejected.
369+ decoder
370+ .window_log_max(21)
371+ .map_err(|_| CryptoError::Decompress)?;
372+ let mut out = Vec::with_capacity(4096);
246373 (&mut decoder)
247374 .take(MAX_PLAINTEXT_LEN as u64 + 1)
248375 .read_to_end(&mut out)
@@ -261,6 +388,12 @@ pub fn encrypt(
261388 recipient_ed_pub: &[u8; 32],
262389 plaintext: &[u8],
263390) -> Result<Vec<u8>, CryptoError> {
391+ // D28: Reject a plaintext over the cap before compressing and encrypting
392+ // — the recipient will reject it on decompression anyway, so the work
393+ // is wasted. CryptoError::Encrypt signals an encryption-side failure.
394+ if plaintext.len() > MAX_PLAINTEXT_LEN {
395+ return Err(CryptoError::Encrypt);
396+ }
264397 let sender_pub = sender.public_key();
265398
266399 // Ephemeral raw X25519 keypair (libsodium crypto_box_keypair).
@@ -272,29 +405,66 @@ pub fn encrypt(
272405 let raw_secret = x25519(&eph_priv, &recip_x)?;
273406 let key = derive_key(&raw_secret, &eph_pub, &recip_x);
274407
275− let compressed = compress(plaintext);
408+ let compressed = Zeroizing::new(compress(plaintext));
409+
410+ // Compute padding: round the full on-wire blob size up to a bucket boundary
411+ // so relays and network observers cannot tell the exact (compressed) length.
412+ // unpadded = 1 (version) + 32 (eph_pub) + 24 (nonce) + inner + 16 (AEAD tag)
413+ // = 1 + 32 + 24 + (32 + 64 + 4 + compressed.len()) + 16
414+ // = 173 + compressed.len()
415+ let unpadded_blob_len = 1 + 32 + NONCE_LEN + 32 + 64 + 4 + compressed.len() + 16;
416+ let target = padded_len(unpadded_blob_len);
417+ let pad_len = target - unpadded_blob_len;
418+
419+ let mut padding = Zeroizing::new(vec![0u8; pad_len]);
420+ rng.fill_bytes(&mut padding);
276421
277− // Sign recipient_pub || compressed (binds the blob to the recipient).
278− let mut signed = Vec::with_capacity(32 + compressed.len());
422+ let compressed_len_bytes = (compressed.len() as u32).to_be_bytes();
423+
424+ // Sign recipient_pub || compressed_len_bytes || compressed || padding
425+ // (i.e. recipient_pub || everything after the 96-byte header in inner).
426+ let mut signed = Zeroizing::new(Vec::with_capacity(MSG_TAG.len() + 32 + 4 + compressed.len() + padding.len()));
427+ signed.extend_from_slice(MSG_TAG);
279428 signed.extend_from_slice(recipient_ed_pub);
429+ signed.extend_from_slice(&compressed_len_bytes);
280430 signed.extend_from_slice(&compressed);
431+ signed.extend_from_slice(&padding);
281432 let signature = sender.signing_key().sign(&signed);
282433
283− // inner = sender_pub(32) || sig(64) || compressed
284− let mut inner = Vec::with_capacity(32 + 64 + compressed.len());
434+ // inner = sender_pub(32) || sig(64) || compressed_len(4) || compressed || padding
435+ //
436+ // `Zeroizing` so the sender's pubkey, signature, and the compressed plaintext
437+ // are wiped from memory even on the AEAD failure path — the `?` below returns
438+ // early, and a plain `Vec` would be dropped without zeroization. Every other
439+ // sensitive intermediate here (`compressed`, `signed`, `padding`) is already
440+ // `Zeroizing`; `inner` holds copies of all of them plus the sender identity.
441+ let mut inner = Zeroizing::new(Vec::with_capacity(32 + 64 + 4 + compressed.len() + padding.len()));
285442 inner.extend_from_slice(&sender_pub);
286443 inner.extend_from_slice(&signature.to_bytes());
444+ inner.extend_from_slice(&compressed_len_bytes);
287445 inner.extend_from_slice(&compressed);
446+ inner.extend_from_slice(&padding);
288447
289448 let mut nonce = [0u8; NONCE_LEN];
290449 rng.fill_bytes(&mut nonce);
291450 let cipher = XChaCha20Poly1305::new(Key::from_slice(&*key));
451+ // AAD binds the envelope header (version, ephemeral pubkey, nonce) and
452+ // the recipient identity to the ciphertext (N1). A relay that swaps the
453+ // `to` field causes the wrong recipient to fail AEAD decryption, and the
454+ // original recipient's message stays in the mailbox instead of being
455+ // silently misdelivered.
456+ let aad_buf = aad(WIRE_VERSION, &eph_pub, &nonce, recipient_ed_pub);
457+ let payload = AeadPayload {
458+ msg: inner.as_ref(),
459+ aad: &aad_buf,
460+ };
292461 let ciphertext = cipher
293− .encrypt(XNonce::from_slice(&nonce), inner.as_ref())
462+ .encrypt(XNonce::from_slice(&nonce), payload)
294463 .map_err(|_| CryptoError::Encrypt)?;
295464 inner.zeroize();
296465
297− let mut blob = Vec::with_capacity(32 + NONCE_LEN + ciphertext.len());
466+ let mut blob = Vec::with_capacity(1 + 32 + NONCE_LEN + ciphertext.len());
467+ blob.push(WIRE_VERSION);
298468 blob.extend_from_slice(&eph_pub);
299469 blob.extend_from_slice(&nonce);
300470 blob.extend_from_slice(&ciphertext);
@@ -302,9 +472,14 @@ pub fn encrypt(
302472}
303473
304474/// Result of decrypting a blob: the plaintext and the sender's Ed25519 pubkey (hex).
475+///
476+/// `plaintext` is `Zeroizing<Vec<u8>>` so the decrypted message content is wiped
477+/// from memory when the value is dropped, not left in freed memory for a heap
478+/// inspection or a jetsam snapshot. `Deref` makes `&dec.plaintext` work as `&[u8]`
479+/// via auto-deref, so callers that only read the bytes need no change.
305480#[derive(Debug, Clone)]
306481pub struct Decrypted {
307− pub plaintext: Vec<u8>,
482+ pub plaintext: Zeroizing<Vec<u8>>,
308483 pub sender_hex: String,
309484}
310485
@@ -316,23 +491,36 @@ pub fn decrypt(recipient: &Identity, blob: &[u8]) -> Result<Decrypted, CryptoErr
316491 if blob.len() > MAX_BLOB_LEN {
317492 return Err(CryptoError::BlobTooLong);
318493 }
494+ // Version byte — reject any blob we don't know how to handle.
495+ if blob[0] != WIRE_VERSION {
496+ return Err(CryptoError::Decrypt);
497+ }
319498 let mut eph_pub = [0u8; 32];
320− eph_pub.copy_from_slice(&blob[..32]);
499+ eph_pub.copy_from_slice(&blob[1..33]);
321500 let mut nonce = [0u8; NONCE_LEN];
322− nonce.copy_from_slice(&blob[32..32 + NONCE_LEN]);
323− let ciphertext = &blob[32 + NONCE_LEN..];
501+ nonce.copy_from_slice(&blob[33..33 + NONCE_LEN]);
502+ let ciphertext = &blob[33 + NONCE_LEN..];
324503
325− let recip_x_priv = ed25519_sk_to_x25519(&recipient.secret_key);
326− let raw_secret = x25519(&recip_x_priv, &eph_pub)?;
327− let recip_x_pub = ed25519_pk_to_x25519(&recipient.public_key())?;
328− let key = derive_key(&raw_secret, &eph_pub, &recip_x_pub);
504+ let recip_x_priv = recipient.x25519_private();
505+ let raw_secret = x25519(recip_x_priv, &eph_pub)?;
506+ let recip_x_pub = recipient.x25519_public();
507+ let key = derive_key(&raw_secret, &eph_pub, recip_x_pub);
329508
330509 let cipher = XChaCha20Poly1305::new(Key::from_slice(&*key));
331− let mut inner = cipher
332− .decrypt(XNonce::from_slice(&nonce), ciphertext)
333− .map_err(|_| CryptoError::Decrypt)?;
334−
335− if inner.len() < 32 + 64 {
510+ // Reconstruct the same AAD used during encryption: the envelope header
511+ // and the recipient identity. This binds the envelope `to` field to the
512+ // ciphertext — a relay that swapped `to` causes AEAD failure here, not
513+ // a silent misdelivery (N1).
514+ let recip_pub = recipient.public_key();
515+ let aad_buf = aad(blob[0], &eph_pub, &nonce, &recip_pub);
516+ let payload = AeadPayload { msg: ciphertext, aad: &aad_buf };
517+ let mut inner = Zeroizing::new(
518+ cipher
519+ .decrypt(XNonce::from_slice(&nonce), payload)
520+ .map_err(|_| CryptoError::Decrypt)?,
521+ );
522+
523+ if inner.len() < 32 + 64 + 4 {
336524 inner.zeroize();
337525 return Err(CryptoError::BlobTooShort);
338526 }
@@ -340,21 +528,40 @@ pub fn decrypt(recipient: &Identity, blob: &[u8]) -> Result<Decrypted, CryptoErr
340528 sender_pub.copy_from_slice(&inner[..32]);
341529 let mut sig_bytes = [0u8; 64];
342530 sig_bytes.copy_from_slice(&inner[32..96]);
343− let compressed = &inner[96..];
344531
345− // Verify signature over recipient_pub || compressed.
532+ let compressed_len = u32::from_be_bytes([
533+ inner[96],
534+ inner[97],
535+ inner[98],
536+ inner[99],
537+ ]) as usize;
538+ if compressed_len > inner.len().saturating_sub(100) {
539+ inner.zeroize();
540+ return Err(CryptoError::Decrypt);
541+ }
542+ let compressed = &inner[100..100 + compressed_len];
543+
544+ // Verify signature over recipient_pub || inner[96..]
545+ // (covers compressed_len_bytes || compressed || padding).
346546 let verifying = VerifyingKey::from_bytes(&sender_pub).map_err(|_| CryptoError::BadSignature)?;
347547 let signature = ed25519_dalek::Signature::from_bytes(&sig_bytes);
348− let mut signed = Vec::with_capacity(32 + compressed.len());
548+ let mut signed = Zeroizing::new(Vec::with_capacity(MSG_TAG.len() + 32 + (inner.len() - 96)));
549+ signed.extend_from_slice(MSG_TAG);
349550 signed.extend_from_slice(&recipient.public_key());
350− signed.extend_from_slice(compressed);
551+ signed.extend_from_slice(&inner[96..]);
351552 verifying
352− .verify(&signed, &signature)
553+ .verify_strict(&signed, &signature)
353554 .map_err(|_| CryptoError::BadSignature)?;
354555
355556 let plaintext = decompress(compressed)?;
557+ // `inner` and `signed` hold the decrypted sender identity and message
558+ // content; zeroize them explicitly on the success path too, not just on
559+ // errors (the `Zeroizing` wrapper handles drop, but being explicit here
560+ // keeps the success and error paths symmetric).
561+ inner.zeroize();
562+ signed.zeroize();
356563 Ok(Decrypted {
357− plaintext,
564+ plaintext: Zeroizing::new(plaintext),
358565 sender_hex: hex::encode(sender_pub),
359566 })
360567}
@@ -371,12 +578,12 @@ mod tests {
371578
372579 #[test]
373580 fn identity_pub_is_last_32_bytes_and_consistent() {
374− let id = Identity::generate(&mut rng(1));
581+ let id = Identity::generate(&mut rng(1)).unwrap();
375582 assert_eq!(&id.secret_key[32..], &id.public_key());
376583 // Re-deriving from the seed yields the same public key.
377584 let mut seed = [0u8; 32];
378585 seed.copy_from_slice(&id.secret_key[..32]);
379− let id2 = Identity::from_seed(&seed);
586+ let id2 = Identity::from_seed(&seed).unwrap();
380587 assert_eq!(id.public_key(), id2.public_key());
381588 }
382589
@@ -384,7 +591,7 @@ mod tests {
384591 /// under one identity while claiming another.
385592 #[test]
386593 fn from_secret_bytes_rejects_a_seed_pubkey_mismatch() {
387− let id = Identity::from_seed(&[3u8; 32]);
594+ let id = Identity::from_seed(&[3u8; 32]).unwrap();
388595 assert!(Identity::from_secret_bytes(&id.secret_key).is_ok());
389596
390597 let mut tampered = id.secret_key;
@@ -397,31 +604,31 @@ mod tests {
397604
398605 #[test]
399606 fn round_trip_recovers_plaintext_and_sender() {
400− let alice = Identity::generate(&mut rng(10));
401− let bob = Identity::generate(&mut rng(20));
607+ let alice = Identity::generate(&mut rng(10)).unwrap();
608+ let bob = Identity::generate(&mut rng(20)).unwrap();
402609 let msg = br#"{"type":"text","id":"abc","body":"hello bob","ts":1700000000000}"#;
403610
404611 let blob = encrypt(&mut rng(99), &alice, &bob.public_key(), msg).unwrap();
405612 assert!(blob.len() >= MIN_BLOB_LEN);
406613
407614 let out = decrypt(&bob, &blob).unwrap();
408− assert_eq!(out.plaintext, msg);
615+ assert_eq!(out.plaintext.as_slice(), msg);
409616 assert_eq!(out.sender_hex, alice.public_key_hex());
410617 }
411618
412619 #[test]
413620 fn wrong_recipient_cannot_decrypt() {
414− let alice = Identity::generate(&mut rng(1));
415− let bob = Identity::generate(&mut rng(2));
416− let eve = Identity::generate(&mut rng(3));
621+ let alice = Identity::generate(&mut rng(1)).unwrap();
622+ let bob = Identity::generate(&mut rng(2)).unwrap();
623+ let eve = Identity::generate(&mut rng(3)).unwrap();
417624 let blob = encrypt(&mut rng(4), &alice, &bob.public_key(), b"secret").unwrap();
418625 assert_eq!(decrypt(&eve, &blob).unwrap_err(), CryptoError::Decrypt);
419626 }
420627
421628 #[test]
422629 fn tampered_ciphertext_is_rejected() {
423− let alice = Identity::generate(&mut rng(1));
424− let bob = Identity::generate(&mut rng(2));
630+ let alice = Identity::generate(&mut rng(1)).unwrap();
631+ let bob = Identity::generate(&mut rng(2)).unwrap();
425632 let mut blob = encrypt(&mut rng(4), &alice, &bob.public_key(), b"secret").unwrap();
426633 let last = blob.len() - 1;
427634 blob[last] ^= 0xff;
@@ -430,23 +637,25 @@ mod tests {
430637
431638 #[test]
432639 fn blob_layout_offsets() {
433− let alice = Identity::generate(&mut rng(1));
434− let bob = Identity::generate(&mut rng(2));
640+ let alice = Identity::generate(&mut rng(1)).unwrap();
641+ let bob = Identity::generate(&mut rng(2)).unwrap();
435642 let blob = encrypt(&mut rng(7), &alice, &bob.public_key(), b"x").unwrap();
436− // eph_pub occupies the first 32 bytes and equals x25519 basepoint * eph_priv;
643+ // Version byte at offset 0.
644+ assert_eq!(blob[0], WIRE_VERSION);
645+ // eph_pub occupies bytes 1..33 and equals x25519 basepoint * eph_priv;
437646 // we can't recompute eph_priv, but the nonce region must differ run-to-run.
438647 let blob2 = encrypt(&mut rng(8), &alice, &bob.public_key(), b"x").unwrap();
439− assert_ne!(&blob[..32], &blob2[..32], "ephemeral pubkey must be random");
648+ assert_ne!(&blob[1..33], &blob2[1..33], "ephemeral pubkey must be random");
440649 assert_ne!(
441− &blob[32..32 + NONCE_LEN],
442− &blob2[32..32 + NONCE_LEN],
650+ &blob[33..33 + NONCE_LEN],
651+ &blob2[33..33 + NONCE_LEN],
443652 "nonce must be random"
444653 );
445654 }
446655
447656 #[test]
448657 fn too_short_blob_errors() {
449− let bob = Identity::generate(&mut rng(2));
658+ let bob = Identity::generate(&mut rng(2)).unwrap();
450659 assert_eq!(
451660 decrypt(&bob, &[0u8; 10]).unwrap_err(),
452661 CryptoError::BlobTooShort
@@ -457,7 +666,7 @@ mod tests {
457666 /// scalar mult, an AEAD pass, or a decompression.
458667 #[test]
459668 fn too_long_blob_errors() {
460− let bob = Identity::generate(&mut rng(2));
669+ let bob = Identity::generate(&mut rng(2)).unwrap();
461670 let huge = vec![0u8; MAX_BLOB_LEN + 1];
462671 assert_eq!(decrypt(&bob, &huge).unwrap_err(), CryptoError::BlobTooLong);
463672 }
@@ -474,50 +683,123 @@ mod tests {
474683 );
475684 assert_eq!(decompress(&bomb).unwrap_err(), CryptoError::Decompress);
476685
477− // ...and the same bomb wrapped in a well-formed, correctly signed blob
478− // (i.e. from a real peer) dies at the same wall.
479− let alice = Identity::generate(&mut rng(1));
480− let bob = Identity::generate(&mut rng(2));
481− let blob = encrypt(
482− &mut rng(3),
483− &alice,
484− &bob.public_key(),
485− &vec![0u8; MAX_PLAINTEXT_LEN + 1],
486− )
487− .unwrap();
488− assert_eq!(decrypt(&bob, &blob).unwrap_err(), CryptoError::Decompress);
686+ // ...and the same bomb sent through encrypt is rejected before
687+ // compression/encryption work is done (D28).
688+ let alice = Identity::generate(&mut rng(1)).unwrap();
689+ let bob = Identity::generate(&mut rng(2)).unwrap();
690+ assert_eq!(
691+ encrypt(
692+ &mut rng(3),
693+ &alice,
694+ &bob.public_key(),
695+ &vec![0u8; MAX_PLAINTEXT_LEN + 1],
696+ )
697+ .unwrap_err(),
698+ CryptoError::Encrypt,
699+ );
489700 }
490701
491702 /// A plaintext right at the cap still round-trips: the bound is inclusive.
492703 #[test]
493704 fn a_plaintext_at_the_cap_still_round_trips() {
494− let alice = Identity::generate(&mut rng(1));
495− let bob = Identity::generate(&mut rng(2));
705+ let alice = Identity::generate(&mut rng(1)).unwrap();
706+ let bob = Identity::generate(&mut rng(2)).unwrap();
496707 let msg = vec![7u8; MAX_PLAINTEXT_LEN];
497708 let blob = encrypt(&mut rng(3), &alice, &bob.public_key(), &msg).unwrap();
498− assert_eq!(decrypt(&bob, &blob).unwrap().plaintext, msg);
709+ assert_eq!(decrypt(&bob, &blob).unwrap().plaintext.as_slice(), msg.as_slice());
499710 }
500711
501712 /// A low-order ephemeral point makes every recipient derive the same shared
502713 /// secret, so the sender's "encryption" is forgeable. Reject it.
503714 #[test]
504715 fn a_low_order_ephemeral_point_is_rejected() {
505− let bob = Identity::generate(&mut rng(2));
716+ let bob = Identity::generate(&mut rng(2)).unwrap();
506717 // eph_pub = 0 is the canonical low-order point; x25519 with it yields
507718 // an all-zero shared secret for any scalar.
508719 let mut blob = vec![0u8; MIN_BLOB_LEN + 1];
509− blob[..32].fill(0);
720+ blob[0] = WIRE_VERSION;
721+ blob[1..33].fill(0);
510722 assert_eq!(
511723 decrypt(&bob, &blob).unwrap_err(),
512724 CryptoError::InvalidEphemeralKey
513725 );
514726 }
515727
728+ /// A short message must be padded so the blob size lands on a bucket boundary.
729+ #[test]
730+ fn blob_is_padded_to_bucket_size() {
731+ let alice = Identity::generate(&mut rng(1)).unwrap();
732+ let bob = Identity::generate(&mut rng(2)).unwrap();
733+
734+ // Short message → should round up to the smallest bucket (256).
735+ let blob_small = encrypt(&mut rng(7), &alice, &bob.public_key(), b"x").unwrap();
736+ assert!(
737+ PADDING_BUCKETS.contains(&blob_small.len()),
738+ "blob len {} is not a bucket boundary",
739+ blob_small.len()
740+ );
741+ assert_eq!(blob_small.len(), 256);
742+
743+ // A larger message should also land on a bucket boundary.
744+ let large_msg = vec![0u8; 300];
745+ let blob_large = encrypt(&mut rng(8), &alice, &bob.public_key(), &large_msg).unwrap();
746+ assert!(
747+ PADDING_BUCKETS.contains(&blob_large.len()) || blob_large.len().is_multiple_of(65536),
748+ "blob len {} is not a bucket boundary",
749+ blob_large.len()
750+ );
751+ }
752+
753+ /// The same plaintext encrypted with different RNG seeds must produce the
754+ /// same blob size (same bucket) but different blob contents (random padding).
755+ #[test]
756+ fn padding_is_random_per_message() {
757+ let alice = Identity::generate(&mut rng(1)).unwrap();
758+ let bob = Identity::generate(&mut rng(2)).unwrap();
759+ let msg = b"hello bob, this is a test message";
760+
761+ let blob1 = encrypt(&mut rng(100), &alice, &bob.public_key(), msg).unwrap();
762+ let blob2 = encrypt(&mut rng(200), &alice, &bob.public_key(), msg).unwrap();
763+
764+ // Same bucket → same size.
765+ assert_eq!(blob1.len(), blob2.len(), "same plaintext must have same blob size");
766+
767+ // Different RNG → different ephemeral key, nonce, and padding → different bytes.
768+ assert_ne!(&blob1[..], &blob2[..], "different RNG must produce different blobs");
769+
770+ // Both must decrypt correctly.
771+ assert_eq!(decrypt(&bob, &blob1).unwrap().plaintext.as_slice(), msg);
772+ assert_eq!(decrypt(&bob, &blob2).unwrap().plaintext.as_slice(), msg);
773+ }
774+
775+ /// The compressed_len field must be parsed correctly so the decompressor
776+ /// never sees trailing padding bytes.
777+ #[test]
778+ fn compressed_len_field_is_parsed_correctly() {
779+ let alice = Identity::generate(&mut rng(1)).unwrap();
780+ let bob = Identity::generate(&mut rng(2)).unwrap();
781+
782+ // Normal round-trip.
783+ let msg = b"round trip test with some content";
784+ let blob = encrypt(&mut rng(7), &alice, &bob.public_key(), msg).unwrap();
785+ assert_eq!(decrypt(&bob, &blob).unwrap().plaintext.as_slice(), msg);
786+
787+ // A message whose compressed size happens to produce a blob that lands
788+ // exactly on a bucket boundary (zero padding). We can't easily engineer
789+ // this, but we can verify the decrypt path works with the actual data.
790+ // Just verify that every bucket-sized blob round-trips.
791+ for size in [1usize, 10, 100, 200, 500, 1000, 5000] {
792+ let m = vec![0xABu8; size];
793+ let b = encrypt(&mut rng(42), &alice, &bob.public_key(), &m).unwrap();
794+ assert_eq!(decrypt(&bob, &b).unwrap().plaintext.as_slice(), m.as_slice());
795+ }
796+ }
797+
516798 /// A recipient key that isn't a curve point can't be encrypted to, and the
517799 /// error says so rather than blaming decryption.
518800 #[test]
519801 fn encrypting_to_an_off_curve_key_reports_an_invalid_public_key() {
520− let alice = Identity::generate(&mut rng(1));
802+ let alice = Identity::generate(&mut rng(1)).unwrap();
521803 let not_a_point = [0xabu8; 32];
522804 assert_eq!(
523805 encrypt(&mut rng(2), &alice, &not_a_point, b"x").unwrap_err(),
@@ -527,7 +809,7 @@ mod tests {
527809
528810 #[test]
529811 fn sk_to_x25519_clamps() {
530− let id = Identity::generate(&mut rng(5));
812+ let id = Identity::generate(&mut rng(5)).unwrap();
531813 let scalar = ed25519_sk_to_x25519(&id.secret_key);
532814 assert_eq!(scalar[0] & 7, 0);
533815 assert_eq!(scalar[31] & 64, 64);
@@ -536,7 +818,7 @@ mod tests {
536818
537819 #[test]
538820 fn challenge_signature_is_deterministic_and_host_bound() {
539− let id = Identity::from_seed(&[7u8; 32]);
821+ let id = Identity::from_seed(&[7u8; 32]).unwrap();
540822 let a = id.sign_challenge("relay.example.com", "deadbeef").unwrap();
541823 let b = id.sign_challenge("relay.example.com", "deadbeef").unwrap();
542824 let c = id.sign_challenge("other.example.com", "deadbeef").unwrap();
@@ -548,7 +830,7 @@ mod tests {
548830 /// We sign whatever a not-yet-trusted relay hands us, so its size is bounded.
549831 #[test]
550832 fn an_oversized_challenge_is_not_signed() {
551− let id = Identity::from_seed(&[7u8; 32]);
833+ let id = Identity::from_seed(&[7u8; 32]).unwrap();
552834 let huge = "a".repeat(MAX_CHALLENGE_LEN + 1);
553835 assert_eq!(
554836 id.sign_challenge("relay.example.com", &huge).unwrap_err(),
@@ -558,4 +840,55 @@ mod tests {
558840 let at_cap = "a".repeat(MAX_CHALLENGE_LEN);
559841 assert!(id.sign_challenge("relay.example.com", &at_cap).is_ok());
560842 }
843+
844+ /// A blob encrypted to Bob cannot be decrypted by Charlie — the key
845+ /// derivation itself binds the recipient (the AEAD key is a function
846+ /// of the recipient's private key and the ephemeral public key). The
847+ /// AAD additionally authenticates the recipient pubkey, but the tag
848+ /// check would fail even without it, because Charlie derives a
849+ /// different key. The AAD is defense-in-depth: it makes the binding
850+ /// explicit rather than implicit in the KDF.
851+ #[test]
852+ fn wrong_recipient_cannot_decrypt_aead_fails() {
853+ let alice = Identity::generate(&mut rng(1)).unwrap();
854+ let bob = Identity::generate(&mut rng(2)).unwrap();
855+ let charlie = Identity::generate(&mut rng(3)).unwrap();
856+
857+ let blob = encrypt(&mut rng(4), &alice, &bob.public_key(), b"hi bob").unwrap();
858+ assert_eq!(
859+ decrypt(&charlie, &blob).unwrap_err(),
860+ CryptoError::Decrypt,
861+ "wrong recipient must fail AEAD — key derivation binds the recipient"
862+ );
863+ }
864+
865+ /// Tampering with the version byte causes failure via the explicit
866+ /// version check (`blob[0] != WIRE_VERSION`) before the AEAD even runs.
867+ /// The AAD includes the version as defense-in-depth, but the explicit
868+ /// check fires first.
869+ #[test]
870+ fn tampered_version_byte_is_rejected() {
871+ let alice = Identity::generate(&mut rng(1)).unwrap();
872+ let bob = Identity::generate(&mut rng(2)).unwrap();
873+ let mut blob = encrypt(&mut rng(3), &alice, &bob.public_key(), b"hi").unwrap();
874+ blob[0] ^= 0xff;
875+ assert_eq!(
876+ decrypt(&bob, &blob).unwrap_err(),
877+ CryptoError::Decrypt,
878+ "version byte tampering is rejected"
879+ );
880+ }
881+
882+ /// Tampering with the ephemeral pubkey causes key derivation to produce
883+ /// a different key, so the AEAD tag check fails. The AAD additionally
884+ /// authenticates the eph_pub, but the KDF mismatch is what actually
885+ /// catches this.
886+ #[test]
887+ fn tampered_ephemeral_pubkey_is_rejected() {
888+ let alice = Identity::generate(&mut rng(1)).unwrap();
889+ let bob = Identity::generate(&mut rng(2)).unwrap();
890+ let mut blob = encrypt(&mut rng(3), &alice, &bob.public_key(), b"hi").unwrap();
891+ blob[5] ^= 0x01;
892+ assert!(decrypt(&bob, &blob).is_err());
893+ }
561894}
core/src/ffi.rs+5
@@ -39,6 +39,11 @@ impl Default for CoreFFI {
3939/// `AssertUnwindSafe` is sound here because a poisoned `Bridge` is never read
4040/// again for correctness: the worst case is a dropped effect batch, and the next
4141/// event starts a fresh `update`.
42+///
43+/// NOTE: A panic mid-`update` leaves the `Model` in a partially-mutated state.
44+/// The next `update` call operates on this potentially-corrupted state. A
45+/// proper fix requires snapshotting the Model before `update` and restoring on
46+/// panic, or marking the Bridge as poisoned. This is an accepted limitation.
4247fn guard(f: impl FnOnce() -> Vec<u8>) -> Vec<u8> {
4348 catch_unwind(AssertUnwindSafe(f)).unwrap_or_default()
4449}
core/src/model.rs+65−2
@@ -1,6 +1,8 @@
11//! Domain types: persisted state (stored in the kv capability as JSON) and the
22//! `ViewModel` types the Swift shell renders.
33
4+use std::sync::Arc;
5+
46use facet::Facet;
57use serde::{Deserialize, Serialize};
68
@@ -58,6 +60,8 @@ pub struct Contact {
5860 pub blocked: bool,
5961 /// `ts` of the last applied profile message (drop older replays).
6062 pub last_profile_ts: i64,
63+ /// `ts` of the last applied delivery.ack (drop older replays).
64+ pub last_ack_ts: i64,
6165 pub added_at: i64,
6266}
6367
@@ -71,6 +75,7 @@ impl Contact {
7175 photo: None,
7276 blocked: false,
7377 last_profile_ts: 0,
78+ last_ack_ts: 0,
7479 added_at,
7580 }
7681 }
@@ -98,13 +103,72 @@ pub struct StoredMessage {
98103 pub delivered: bool,
99104}
100105
106+/// Transient send failures one outbox item may absorb before it is given up on.
107+///
108+/// Without a ceiling the head of the outbox is retried forever, and because the
109+/// outbox is a strict FIFO an item that can never be delivered blocks every
110+/// message queued behind it — permanently.
111+pub const MAX_OUTBOX_RETRIES: u32 = 10;
112+
113+/// ...and a wall-clock bound on the same thing, for the case where the retries
114+/// come in slowly enough that the counter alone would take days to run out. 24h.
115+pub const OUTBOX_TTL_MS: i64 = 86_400_000;
116+
101117/// A queued outbound payload awaiting encryption + send.
102118#[derive(Serialize, Deserialize, Clone, Debug, Default)]
103119#[serde(default)]
104120pub struct OutboxItem {
105121 pub recipient: String,
106122 /// The serialized plaintext payload JSON (encrypted only at send time).
107− pub envelope_json: String,
123+ pub envelope_json: Arc<String>,
124+ /// `Some("profile")` for a profile broadcast, `None` for everything else.
125+ ///
126+ /// A profile is *state*, not an event: only the latest one matters, so
127+ /// `SaveProfile` overwrites the pending item for a recipient rather than
128+ /// queueing another. Without the marker there is nothing to overwrite by, and
129+ /// five quick profile edits mean five payloads (photo and all) per contact.
130+ pub kind: Option<String>,
131+ /// Transient send failures this item has absorbed so far.
132+ pub retries: u32,
133+ /// `now_ms()` when this item was first put on the wire, or `0` if it never
134+ /// has been. The TTL runs from here, so an item queued during a week offline
135+ /// still gets its full retry budget once the network comes back.
136+ pub first_attempt: i64,
137+}
138+
139+impl OutboxItem {
140+ pub fn new(recipient: String, envelope_json: Arc<String>) -> Self {
141+ OutboxItem {
142+ recipient,
143+ envelope_json,
144+ kind: None,
145+ retries: 0,
146+ first_attempt: 0,
147+ }
148+ }
149+
150+ /// A profile broadcast — the one payload kind that supersedes rather than
151+ /// accumulates (see `kind`).
152+ pub fn profile(recipient: String, envelope_json: Arc<String>) -> Self {
153+ OutboxItem {
154+ kind: Some("profile".to_string()),
155+ ..OutboxItem::new(recipient, envelope_json)
156+ }
157+ }
158+
159+ pub fn is_profile(&self) -> bool {
160+ self.kind.as_deref() == Some("profile")
161+ }
162+
163+ /// Has this item exhausted its retry budget or outlived the TTL?
164+ ///
165+ /// `first_attempt == 0` means it has never been sent (or was queued by a build
166+ /// that predates the field), so the TTL has nothing to measure from and only
167+ /// the counter applies.
168+ pub fn is_expired(&self, now: i64) -> bool {
169+ self.retries >= MAX_OUTBOX_RETRIES
170+ || (self.first_attempt > 0 && now.saturating_sub(self.first_attempt) > OUTBOX_TTL_MS)
171+ }
108172}
109173
110174// ---------------------------------------------------------------------------
@@ -187,6 +251,5 @@ pub struct ViewModel {
187251 pub active_peer_ob: String,
188252 pub active_peer_blocked: bool,
189253 pub messages: Vec<MessageVM>,
190− pub compose: String,
191254 pub error: String,
192255}
core/src/phonemic.rs+65−6
@@ -3,6 +3,9 @@
33//! Each byte pair `[hi, lo]` encodes as `prefixes[hi] ++ suffixes[lo]` (6 chars);
44//! pairs are joined with `-`. A 32-byte key -> 16 six-char syllables.
55
6+use std::collections::HashMap;
7+use std::sync::OnceLock;
8+
69const PREFIXES: [&str; 256] = [
710 "doz", "mar", "bin", "wan", "sam", "lit", "sig", "hid", "fid", "lis", "sog", "dir", "wac",
811 "sab", "wis", "sib", "rig", "sol", "dop", "mod", "fog", "lid", "hop", "dar", "dor", "lor",
@@ -49,12 +52,40 @@ const SUFFIXES: [&str; 256] = [
4952 "fyr", "mur", "tel", "rep", "teg", "pec", "nel", "nev", "fes",
5053];
5154
55+/// Reverse tables for decoding. Built once, on first `from_ob`.
56+///
57+/// Correctness rests on both tables being duplicate-free: a `HashMap` keeps the
58+/// *last* of any repeated syllable, where the linear scan this replaced returned
59+/// the *first*. `tables_are_full_and_distinct` pins that invariant down.
60+static PREFIX_MAP: OnceLock<HashMap<&'static str, u8>> = OnceLock::new();
61+static SUFFIX_MAP: OnceLock<HashMap<&'static str, u8>> = OnceLock::new();
62+
63+fn prefix_map() -> &'static HashMap<&'static str, u8> {
64+ PREFIX_MAP.get_or_init(|| {
65+ PREFIXES
66+ .iter()
67+ .enumerate()
68+ .map(|(i, &s)| (s, i as u8))
69+ .collect()
70+ })
71+}
72+
73+fn suffix_map() -> &'static HashMap<&'static str, u8> {
74+ SUFFIX_MAP.get_or_init(|| {
75+ SUFFIXES
76+ .iter()
77+ .enumerate()
78+ .map(|(i, &s)| (s, i as u8))
79+ .collect()
80+ })
81+}
82+
5283fn prefix_index(s: &str) -> Option<u8> {
53− PREFIXES.iter().position(|p| *p == s).map(|i| i as u8)
84+ prefix_map().get(s).copied()
5485}
5586
5687fn suffix_index(s: &str) -> Option<u8> {
57− SUFFIXES.iter().position(|p| *p == s).map(|i| i as u8)
88+ suffix_map().get(s).copied()
5889}
5990
6091/// Encode bytes as a hyphen-joined `@p` string. `None` for an odd-length input.
@@ -65,6 +96,11 @@ fn suffix_index(s: &str) -> Option<u8> {
6596/// Keys are always 32 bytes, so no caller is affected — but a display helper
6697/// must not quietly invent a byte.
6798pub fn to_ob(bytes: &[u8]) -> Option<String> {
99+ // P1: Empty input produces an empty string, which is a valid but
100+ // meaningless @p — return None instead so the round-trip is symmetric.
101+ if bytes.is_empty() {
102+ return None;
103+ }
68104 if !bytes.len().is_multiple_of(2) {
69105 return None;
70106 }
@@ -120,7 +156,7 @@ pub fn try_parse_pubkey(input: &str) -> Option<String> {
120156 if let Some(hex) = from_ob(trimmed).as_deref().and_then(valid_pubkey_hex) {
121157 return Some(hex);
122158 }
123− if let Ok(bytes) = hex::decode(trimmed.to_lowercase()) {
159+ if let Ok(bytes) = hex::decode(trimmed) {
124160 return valid_pubkey_hex(&bytes);
125161 }
126162 None
@@ -130,12 +166,29 @@ pub fn try_parse_pubkey(input: &str) -> Option<String> {
130166mod tests {
131167 use super::*;
132168
169+ /// The name always claimed distinctness; now the decode path depends on it.
170+ /// A duplicate syllable would collapse a map entry, so a table of 256 that
171+ /// maps to fewer than 256 keys is the exact failure this must catch.
133172 #[test]
134173 fn tables_are_full_and_distinct() {
135174 assert_eq!(PREFIXES.len(), 256);
136175 assert_eq!(SUFFIXES.len(), 256);
137176 assert_eq!(PREFIXES[0], "doz");
138177 assert_eq!(SUFFIXES[0], "zod");
178+ assert_eq!(prefix_map().len(), 256, "prefix table has a duplicate");
179+ assert_eq!(suffix_map().len(), 256, "suffix table has a duplicate");
180+ }
181+
182+ /// Every index must survive encode -> decode. Guards the map against being
183+ /// built off-by-one or with a truncated cast.
184+ #[test]
185+ fn every_syllable_index_round_trips() {
186+ for i in 0..=255u8 {
187+ assert_eq!(prefix_index(PREFIXES[i as usize]), Some(i));
188+ assert_eq!(suffix_index(SUFFIXES[i as usize]), Some(i));
189+ }
190+ assert_eq!(prefix_index("zod"), None, "suffix must not decode as prefix");
191+ assert_eq!(suffix_index("doz"), None, "prefix must not decode as suffix");
139192 }
140193
141194 #[test]
@@ -159,13 +212,13 @@ mod tests {
159212 fn odd_length_input_has_no_spelling() {
160213 assert_eq!(to_ob(&[7u8]), None);
161214 assert_eq!(to_ob(&[7u8, 0]), Some("hidzod".to_string()));
162− assert_eq!(to_ob(&[]), Some(String::new()));
215+ assert_eq!(to_ob(&[]), None);
163216 }
164217
165218 /// A real Ed25519 public key. `try_parse_pubkey` now checks that a key is a
166219 /// curve point, so tests can't use an arbitrary byte pattern.
167220 fn real_key() -> [u8; 32] {
168− crate::crypto::Identity::from_seed(&[7u8; 32]).public_key()
221+ crate::crypto::Identity::from_seed(&[7u8; 32]).unwrap().public_key()
169222 }
170223
171224 /// 32 bytes that decode fine but are *not* on the curve — the case that used
@@ -214,7 +267,13 @@ mod tests {
214267 let mixed: String = ob
215268 .chars()
216269 .enumerate()
217− .map(|(i, c)| if i % 2 == 0 { c.to_ascii_uppercase() } else { c })
270+ .map(|(i, c)| {
271+ if i.is_multiple_of(2) {
272+ c.to_ascii_uppercase()
273+ } else {
274+ c
275+ }
276+ })
218277 .collect();
219278 assert_eq!(try_parse_pubkey(&mixed), Some(hex_str));
220279 }
core/src/protocol.rs+77−32
@@ -4,6 +4,8 @@
44//! millisecond `ts`. Unknown types are ignored (return `None`).
55
66use serde::{Deserialize, Serialize};
7+use base64::prelude::*;
8+use base64::Engine;
79
810/// Caps on the attacker-chosen fields of an incoming payload.
911///
@@ -33,8 +35,8 @@ pub enum Payload {
3335 ack_ids: Vec<String>,
3436 },
3537 Profile {
36− display_name: String,
37− bio: String,
38+ display_name: Option<String>,
39+ bio: Option<String>,
3840 photo: Option<String>,
3941 },
4042}
@@ -75,10 +77,16 @@ pub fn serialize_payload(payload: &Payload, ts: i64) -> String {
7577 } => {
7678 let mut obj = serde_json::json!({
7779 "type": "profile",
78− "display_name": display_name,
79− "bio": bio,
8080 "ts": ts,
8181 });
82+ // D13: Only include the field when present — absent means
83+ // "don't change", while present (even empty) means "set to this".
84+ if let Some(name) = display_name {
85+ obj["display_name"] = serde_json::Value::String(name.clone());
86+ }
87+ if let Some(b) = bio {
88+ obj["bio"] = serde_json::Value::String(b.clone());
89+ }
8290 // Omit `photo` entirely when there isn't one, rather than sending an
8391 // explicit null: "no photo" and "field absent" mean the same thing to
8492 // a reader, and the null costs bytes in every broadcast.
@@ -91,6 +99,38 @@ pub fn serialize_payload(payload: &Payload, ts: i64) -> String {
9199 value.to_string()
92100}
93101
102+/// D14: Filter out control characters, bidirectional control characters, and
103+/// zero-width characters from a received string. Applied on the receiving side
104+/// (parse_payload) so the sender's input is preserved as-is on send, but the
105+/// recipient is protected from invisible character tricks.
106+///
107+/// Filters:
108+/// - Control characters U+0000–U+001F (except U+0009 tab, U+000A newline,
109+/// U+000D carriage return)
110+/// - Bidirectional control characters (U+200E LRM, U+200F RLM, U+202A–U+202E,
111+/// U+2066–U+2069)
112+/// - Zero-width characters (U+200B, U+200C, U+200D, U+FEFF)
113+fn sanitize_text(s: &str) -> String {
114+ s.chars()
115+ .filter(|c| {
116+ let cp = *c as u32;
117+ // Control characters U+0000–U+001F, except tab/newline/CR
118+ if cp <= 0x001F && cp != 0x0009 && cp != 0x000A && cp != 0x000D {
119+ return false;
120+ }
121+ // Bidirectional control characters
122+ if matches!(cp, 0x200E | 0x200F | 0x202A..=0x202E | 0x2066..=0x2069) {
123+ return false;
124+ }
125+ // Zero-width characters
126+ if matches!(cp, 0x200B | 0x200C | 0x200D | 0xFEFF) {
127+ return false;
128+ }
129+ true
130+ })
131+ .collect()
132+}
133+
94134/// Parse a plaintext payload. Returns `None` for unknown/malformed types so the
95135/// caller silently ignores them (forward compatibility, PROTOCOL.md §4).
96136pub fn parse_payload(bytes: &[u8]) -> Option<ParsedPayload> {
@@ -100,7 +140,7 @@ pub fn parse_payload(bytes: &[u8]) -> Option<ParsedPayload> {
100140 let payload = match ty {
101141 "text" => {
102142 let id = v.get("id")?.as_str()?.to_string();
103− let body = v.get("body")?.as_str()?.to_string();
143+ let body = sanitize_text(v.get("body")?.as_str()?);
104144 if id.len() > MAX_ID_LEN || body.len() > MAX_BODY_LEN {
105145 return None;
106146 }
@@ -115,29 +155,34 @@ pub fn parse_payload(bytes: &[u8]) -> Option<ParsedPayload> {
115155 .iter()
116156 .filter_map(|x| x.as_str().map(str::to_string))
117157 .collect();
118− if ack_ids.iter().any(|id| id.len() > MAX_ID_LEN) {
158+ // Re-check after filtering: a peer could pack the array with
159+ // non-string junk that passes the raw count but leaves more
160+ // real ids than the cap allows after filtering. The raw check
161+ // above is an early out; this is the authoritative one.
162+ if ack_ids.len() > MAX_ACK_IDS || ack_ids.iter().any(|id| id.len() > MAX_ID_LEN) {
119163 return None;
120164 }
121165 Payload::DeliveryAck { ack_ids }
122166 }
123167 "profile" => {
124− let display_name = v
125− .get("display_name")
126− .and_then(|x| x.as_str())
127− .unwrap_or("")
128− .to_string();
129− let bio = v
130− .get("bio")
131− .and_then(|x| x.as_str())
132− .unwrap_or("")
133− .to_string();
168+ // D13: Use Option<String> — None when the field is absent (don't
169+ // change the recipient's cached value), Some(value) when present
170+ // (even if empty, meaning "set to this value").
171+ let display_name = v.get("display_name").and_then(|x| x.as_str()).map(sanitize_text);
172+ let bio = v.get("bio").and_then(|x| x.as_str()).map(sanitize_text);
134173 let photo = v
135174 .get("photo")
136175 .and_then(|x| x.as_str())
137176 .map(str::to_string);
138− if display_name.chars().count() > MAX_DISPLAY_NAME_LEN
139− || bio.chars().count() > MAX_BIO_LEN
177+ if display_name.as_ref().is_some_and(|d| d.chars().count() > MAX_DISPLAY_NAME_LEN)
178+ || bio.as_ref().is_some_and(|b| b.chars().count() > MAX_BIO_LEN)
140179 || photo.as_ref().is_some_and(|p| p.len() > MAX_PHOTO_LEN)
180+ || photo.as_ref().is_some_and(|p| {
181+ // Reject a photo that isn't valid base64 — a peer can put
182+ // any string in the field, and the shell attempts to decode
183+ // it as an image on every render.
184+ BASE64_STANDARD.decode(p).is_err()
185+ })
141186 {
142187 return None;
143188 }
@@ -183,14 +228,14 @@ mod tests {
183228 #[test]
184229 fn profile_round_trip_with_and_without_photo() {
185230 let with = Payload::Profile {
186− display_name: "Alice".into(),
187− bio: "writing".into(),
231+ display_name: Some("Alice".into()),
232+ bio: Some("writing".into()),
188233 photo: Some("aGVsbG8=".into()),
189234 };
190235 assert_eq!(reparse(&with, 1).payload, with);
191236 let without = Payload::Profile {
192− display_name: "Bob".into(),
193− bio: "".into(),
237+ display_name: Some("Bob".into()),
238+ bio: Some("".into()),
194239 photo: None,
195240 };
196241 assert_eq!(reparse(&without, 1).payload, without);
@@ -230,8 +275,8 @@ mod tests {
230275
231276 let long_bio = serialize_payload(
232277 &Payload::Profile {
233− display_name: "A".into(),
234− bio: "b".repeat(MAX_BIO_LEN + 1),
278+ display_name: Some("A".into()),
279+ bio: Some("b".repeat(MAX_BIO_LEN + 1)),
235280 photo: None,
236281 },
237282 1,
@@ -240,8 +285,8 @@ mod tests {
240285
241286 let long_name = serialize_payload(
242287 &Payload::Profile {
243− display_name: "n".repeat(MAX_DISPLAY_NAME_LEN + 1),
244− bio: String::new(),
288+ display_name: Some("n".repeat(MAX_DISPLAY_NAME_LEN + 1)),
289+ bio: Some(String::new()),
245290 photo: None,
246291 },
247292 1,
@@ -250,8 +295,8 @@ mod tests {
250295
251296 let big_photo = serialize_payload(
252297 &Payload::Profile {
253− display_name: String::new(),
254− bio: String::new(),
298+ display_name: Some(String::new()),
299+ bio: Some(String::new()),
255300 photo: Some("p".repeat(MAX_PHOTO_LEN + 1)),
256301 },
257302 1,
@@ -285,8 +330,8 @@ mod tests {
285330 fn a_photoless_profile_omits_the_field() {
286331 let json = serialize_payload(
287332 &Payload::Profile {
288− display_name: "A".into(),
289− bio: "B".into(),
333+ display_name: Some("A".into()),
334+ bio: Some("B".into()),
290335 photo: None,
291336 },
292337 1,
@@ -297,8 +342,8 @@ mod tests {
297342 #[test]
298343 fn snake_case_field_names_on_wire() {
299344 let p = Payload::Profile {
300− display_name: "A".into(),
301− bio: "B".into(),
345+ display_name: Some("A".into()),
346+ bio: Some("B".into()),
302347 photo: None,
303348 };
304349 let json = serialize_payload(&p, 1);
install.sh+13−9
@@ -154,18 +154,21 @@ fetch_to "$DOWNLOAD_URL" "$TMP_BIN"
154154# HTTPS, but that authenticates GitHub's CDN, not the artifact — a compromised or
155155# swapped release asset would otherwise be installed and launched unquestioned.
156156#
157−# The check is best-effort by necessity: releases cut before CI began publishing
158−# .sha256 files have no checksum to compare against, and refusing to install from
159−# them would break upgrades from every existing deployment. So a *missing*
160−# checksum warns and proceeds, while a checksum that is present and does *not*
161−# match is fatal — the case that actually indicates tampering.
157+# N15: Verification is mandatory. A missing checksum, a missing sha256sum tool,
158+# or a mismatch are all fatal — the binary is refused.
159+# N15: Checksum verification is mandatory for all installs. A missing
160+# checksum file indicates either a pre-checksum release or a supply-chain
161+# attack that removed the checksum. We refuse to install without verification
162+# rather than silently proceeding.
162163if fetch_to "$CHECKSUM_URL" "$TMP_SUM" 2>/dev/null; then
163164 EXPECTED=$(cut -d' ' -f1 < "$TMP_SUM")
164165 ACTUAL=$(sha256_of "$TMP_BIN")
165166 if [ -z "$ACTUAL" ]; then
166− echo "warning: no sha256sum/shasum available; skipping checksum verification" >&2
167+ echo "error: no sha256sum/shasum available; cannot verify binary integrity" >&2
168+ exit 1
167169 elif [ -z "$EXPECTED" ]; then
168− echo "warning: checksum file is empty; skipping verification" >&2
170+ echo "error: checksum file is empty; refusing to install unverified binary" >&2
171+ exit 1
169172 elif [ "$EXPECTED" != "$ACTUAL" ]; then
170173 echo "error: checksum verification FAILED for ${ASSET}" >&2
171174 echo " expected: ${EXPECTED}" >&2
@@ -176,8 +179,9 @@ if fetch_to "$CHECKSUM_URL" "$TMP_SUM" 2>/dev/null; then
176179 echo "Checksum verified (${ACTUAL})"
177180 fi
178181else
179− echo "warning: no published checksum at ${CHECKSUM_URL}; skipping verification" >&2
180− echo " (releases predating checksum publication have none)" >&2
182+ echo "error: no published checksum at ${CHECKSUM_URL}; refusing to install unverified binary" >&2
183+ echo " (releases predating checksum publication have none — install from a recent release)" >&2
184+ exit 1
181185fi
182186
183187chmod 755 "$TMP_BIN"
server.knot+692−400
@@ -72,34 +72,73 @@ messageMaxAge = 2592000000
7272-- Max length of a hex-encoded message body / opaque blob (40 MiB hex ≈ 20 MiB bytes).
7373maxBlobLen : Int
7474maxBlobLen = 41943040
75−-- Min length of a hex-encoded blob: 336 chars = 168 bytes. A well-formed blob is
76−-- `ephemeral_x25519_pubkey (32) || nonce (24) || ciphertext`, and the ciphertext
77−-- seals at minimum `sender_pubkey (32) || signature (64)` plus the 16-byte
78−-- Poly1305 tag — so 32 + 24 + 32 + 64 + 16 = 168 bytes is the floor for a blob
79−-- any client could possibly decrypt (PROTOCOL.md §3). Anything shorter is
80−-- garbage by construction: it cannot carry a sender identity, and storing it only
75+-- Min length of a hex-encoded blob: 346 chars = 173 bytes. A well-formed blob is
76+-- `version (1) || ephemeral_x25519_pubkey (32) || nonce (24) || ciphertext`, and the
77+-- ciphertext seals at minimum `sender_pubkey (32) || signature (64) || compressed_len (4)`
78+-- plus the 16-byte Poly1305 tag — so 1 + 32 + 24 + 32 + 64 + 4 + 16 = 173 bytes is the
79+-- floor for a blob any client could possibly decrypt (PROTOCOL.md §3). Anything shorter
80+-- is garbage by construction: it cannot carry a sender identity, and storing it only
8181-- burns mailbox rows and the recipient's poll bandwidth. Reject at the boundary.
8282minBlobLen : Int
83−minBlobLen = 336
83+minBlobLen = 346
8484-- Cap on items in a batched send request.
8585maxBatchSize : Int
8686maxBatchSize = 100
8787-- Cap on gossip events accepted or emitted in a single federation exchange.
8888maxGossipEvents : Int
8989maxGossipEvents = 100
90+-- N13: Cap on newly-online keys per gossip batch that trigger forward sweeps.
91+-- Without this, a single gossip request with 100 `online` events triggers 100
92+-- mailbox scans (O(100 × |messages|)). Capping at 10 limits the amplification
93+-- while still allowing reasonable multi-key presence announcements. Remaining
94+-- newly-online keys are still written to `*presence` — only the forward sweep
95+-- is deferred until the next presence re-announce or a poll triggers
96+-- `forwardQueuedToServer` naturally.
97+maxNewlyOnlineForwards : Int
98+maxNewlyOnlineForwards = 10
9099-- Cap on events returned by one long-poll response.
91100maxPollEvents : Int
92101maxPollEvents = 50
93102-- Per-peer ceiling on outstanding forward attempts.
94103maxForwardsPerServer : Int
95104maxForwardsPerServer = 2000
105+-- S9: Cap on distinct remote servers a single message is immediately forwarded
106+-- to at send time. Separate from `maxForwardsPerServer` (which bounds outstanding
107+-- forwards *per peer*), this bounds the fan-out breadth. A recipient is unlikely
108+-- to be visible on more than 100 servers; the previous reuse of
109+-- `maxForwardsPerServer` (2000) for this purpose was an overload that could
110+-- spawn up to 2000 immediate HTTP forwards per message.
111+maxRemoteServersPerMessage : Int
112+maxRemoteServersPerMessage = 100
113+-- Global ceiling on the `*forwards` outbox. `maxForwardsPerServer` bounds any one
114+-- peer, but a recipient gossiped as present on many servers fans one blob out to
115+-- all of them, so the total is bounded only by (peers x per-peer cap). This caps
116+-- the whole outbox.
117+--
118+-- Evicts the *highest*-retry entries first: those are the ones closest to
119+-- `maxForwardRetries` (about to be abandoned anyway), so pressure is shed onto
120+-- failing peers rather than healthy ones. Freshly-staged rows carry `retries: 0`
121+-- and so always survive their own capping.
122+--
123+-- Dropping a forward is not message loss: the `*messages` row it points at stays
124+-- put, so the recipient still gets the blob by polling here, and a later presence
125+-- announce re-stages the forward via `forwardQueuedToServer`.
126+maxForwardsTotal : Int
127+maxForwardsTotal = 50000
96128-- Max accepted length of a server hostname.
97129maxServerNameLen : Int
98130maxServerNameLen = 128
99131-- Ceiling on outstanding auth challenges held in memory.
100132maxChallenges : Int
101133maxChallenges = 10000
102−-- Ceiling on concurrent active sessions.
134+-- Ceiling on concurrent active sessions. Enforced by `capList` in
135+-- `handleVerifyAuth`, which LRU-evicts the soonest-to-expire sessions once the
136+-- pool is full.
137+--
138+-- LIMITATION — global LRU eviction is Sybil-floodable: an attacker with enough
139+-- IPs can evict live users' sessions. Bounded by `maxSessionsPerKey` and per-IP
140+-- `authRateLimit`; a per-IP session cap was rejected (collapses without XFF,
141+-- punishes carrier-NAT). A real fix prices session creation, not IPs. See PROTOCOL.md §10.
103142maxSessions : Int
104143maxSessions = 10000
105144-- Per-pubkey ceiling on outstanding challenges (prevents one key from exhausting the pool).
@@ -107,19 +146,66 @@ maxChallengesPerKey : Int
107146maxChallengesPerKey = 5
108147-- Per-pubkey ceiling on concurrent sessions.
109148--
110−-- LIMITATION — concurrent sessions for the *same* keypair are not supported, and
111−-- this cap does not make them safe; it only bounds how many can exist. The mailbox
112−-- is keyed by pubkey, not by session, and /poll treats a cursor advance as an ack
113−-- that *deletes* rows (`ackPolledMessages`), so two devices sharing one keypair
114−-- poll the same mailbox and each one's ack destroys messages the other has not
115−-- read yet — whichever polls first wins, and the loser silently never sees them.
116−-- The expected model is one keypair per device (PROTOCOL.md §2: "Each device
117−-- generates its own independent keypair and is treated as a separate identity").
118−-- The cap exists so a key cannot exhaust the global `maxSessions` pool, not to
119−-- make key-sharing work. Fixing key-sharing needs per-session delivery cursors
120−-- instead of destructive acks — out of scope for v0.1.
149+-- LIMITATION — concurrent sessions for the same keypair are not supported: the
150+-- mailbox is keyed by pubkey, so two devices sharing a key poll one mailbox and
151+-- each ack destroys messages the other hasn't read. The model is one keypair per
152+-- device (PROTOCOL.md §2). This cap only bounds pool exhaustion, not key-sharing.
153+-- A fix needs per-session delivery cursors — out of scope for v0.1.
121154maxSessionsPerKey : Int
122155maxSessionsPerKey = 10
156+-- Ceiling on gossip-learned (remote) presence rows.
157+--
158+-- `/federation/gossip` is unauthenticated and pubkeys are free to invent, so
159+-- without a cap one peer can grow `*presence` without bound. `handleRecvGossip`
160+-- LRU-evicts (`capList`) down to this ceiling.
161+--
162+-- Local rows are exempt: they're bounded by `maxSessions` and a shared ceiling
163+-- would let gossip floods evict our own online users (local TTL 60 min < gossip
164+-- TTL 90 min, so `capList` drops local rows first). See PROTOCOL.md §10.
165+maxPresence : Int
166+maxPresence = 100000
167+-- Per-peer-server ceiling on gossip-learned presence rows, so a single peer cannot
168+-- consume the whole `maxPresence` pool and evict every other peer's routing
169+-- information. Filling the global pool then requires many distinct hostnames that
170+-- each pass `isBadServerName`.
171+maxPresencePerServer : Int
172+maxPresencePerServer = 5000
173+-- Per-recipient ceiling on stored mailbox rows. Without a cap a single
174+-- authenticated sender can queue unbounded data for one recipient
175+-- (`maxBatchSize` 100 messages/request x `sendRateLimit` 60 requests/min =
176+-- 6000/min, each blob up to 20 MiB) and only the 30-day `messageMaxAge` TTL
177+-- ever reclaims it. Past the cap `appendMessage` drops the oldest rows (lowest
178+-- `receivedAt`) — the same rows the TTL would eventually drop, just sooner.
179+--
180+-- The recipient's client bounds what it *processes* per poll (MAX_POLL_TOTAL_BYTES
181+-- in core/src/app.rs), but nothing bounded what the server *stores* before this.
182+--
183+-- Dropping a row orphans any `*forwards` entry for it; `pruneExpired` collects
184+-- those (it drops forwards whose message no longer exists). Its `deliveredTo`
185+-- set is lost with it, which is harmless — the blob is gone, so there is
186+-- nothing left to re-forward.
187+--
188+-- LIMITATION — evicting on overflow means a flood can now *destroy* mail, not
189+-- just pile it up: an attacker who fills a recipient's mailbox pushes that
190+-- recipient's genuine undelivered messages out of the window. Pubkeys are free
191+-- to mint, so "authenticated sender" is no barrier. This is a trade, not a fix
192+-- — the alternative (reject once full) hands the same attacker a permanent
193+-- block on *all* new mail to that recipient, which is strictly worse: here at
194+-- least the newest messages always land. It only bites a recipient who is
195+-- offline long enough to accumulate `maxMessagesPerRecipient`, since polling
196+-- drains the mailbox (`ackPolledMessages`). A real fix prices sending — see
197+-- the same argument for sessions on `maxSessions`, and PROTOCOL.md §10.
198+maxMessagesPerRecipient : Int
199+maxMessagesPerRecipient = 10000
200+-- Global ceiling on total stored messages across all recipients (S6). Every
201+-- other state ref has a global cap (*sessions, *challenges, *presence,
202+-- *forwards); *messages had only a per-recipient cap, so total storage was
203+-- bounded only by (distinct recipient keys x maxMessagesPerRecipient), and an
204+-- attacker minting fresh invalid pubkeys could fill the disk (bounded only by
205+-- rate limits and the 30-day TTL). On overflow this evicts the globally-oldest
206+-- rows, symmetric with the other refs. See PROTOCOL.md §10.
207+maxMessagesTotal : Int
208+maxMessagesTotal = 1000000
123209-- Validity window for an auth challenge before it must be re-issued (1 min).
124210challengeExpiry : Int<Ms>
125211challengeExpiry = 60000
@@ -158,22 +244,13 @@ pollTimeoutMs = 25000
158244rateLimitWindow : Int<Ms>
159245rateLimitWindow = 60000
160246-- Per-client-IP budget for /auth/challenge and /auth/verify per `rateLimitWindow`.
161−-- The normal handshake is one challenge + one verify, so a healthy flow uses 2;
162−-- the budget leaves room for many clients behind one NAT. (Keyed on IP, not on
163−-- the submitted pubkey: keypairs are free to generate, so a pubkey-keyed bucket
164−-- hands an attacker a fresh budget with every rotation — a Sybil flood could
165−-- then mint sessions until `maxSessions` is hit and evict live ones. A pubkey
166−-- key is also abusable in the other direction: flooding a *victim's* pubkey
167−-- would exhaust that victim's login budget. Per-pubkey exhaustion of the
168−-- challenge/session pools is still bounded, by `maxChallengesPerKey` and
169−-- `maxSessionsPerKey` in the handlers.)
247+-- A healthy handshake is one challenge + one verify, so the budget leaves ample
248+-- room for many clients behind one NAT.
170249authRateLimit : Int
171250authRateLimit = 60
172−-- Per-client-IP budget for /poll per `rateLimitWindow`. Clients reconnect
173−-- after `pollTimeoutMs`, so steady state is ~3/min per client; the budget
174−-- leaves room for several clients behind one NAT. (Keyed on IP, not bearer
175−-- token — token-keyed buckets let an attacker mint a fresh bucket per
176−-- invented bearer value.)
251+-- Per-client-IP budget for /poll per `rateLimitWindow`. Clients reconnect after
252+-- `pollTimeoutMs`, so steady state is ~3/min per client; the budget leaves room
253+-- for several clients behind one NAT.
177254pollRateLimit : Int
178255pollRateLimit = 60
179256-- Per-client-IP budget for /messages per `rateLimitWindow`. Each call may
@@ -225,13 +302,14 @@ federationEnabled = False {}
225302seedPeers : Text
226303seedPeers = ""
227304
228−-- `seedPeers` split on commas, trimmed, with blanks dropped. Deliberately *not*
229−-- filtered through `isBadServerName` here: every federation egress site applies
230−-- the deny-list itself, so a denylisted seed is refused at exactly the same choke
231−-- point as a denylisted gossip-learned peer, and the parse stays purely
232−-- syntactic.
305+-- `seedPeers` split on commas, trimmed, with blanks and our own hostname dropped.
306+-- Deliberately *not* filtered through `isBadServerName` here: every federation
307+-- egress site applies the deny-list itself, so a denylisted seed is refused at
308+-- exactly the same choke point as a denylisted gossip-learned peer.
309+-- Filtering `serverHost` out at parse time lets `gossipTargets` drop its
310+-- `isLocalServer` guard (the only other source, `collectPeers`, already filters it).
233311seedPeerList : [Text]
234−seedPeerList = filter (\s -> s != "") (splitOnComma seedPeers)
312+seedPeerList = filter (\s -> s != "" && not isLocalServer s) (splitOnComma seedPeers)
235313
236314federationUrl : Text -> Text
237315federationUrl = \server -> federationScheme ++ server
@@ -259,25 +337,13 @@ type PollEvent = {encryptedBlob: BlobHex}
259337-- fallback (the old `GossipUnknown` variant).
260338type GossipEvent = {eventType: Text, pubkey: Maybe Text}
261339
262−-- /messages is all-or-nothing per call: either every message in the batch is
263−-- enqueued (delivered, federated, or buffered for federation), or none are
264−-- and the call returns a non-2xx HTTP status. The per-message rejection code
265−-- "self_send" surfaces in the HTTP error body. Per-client-IP rate limiting is
266−-- enforced by the route's `rateLimit` clause, which short-circuits with 429
267−-- before the handler runs.
268−-- The sender's UI treats every success the same and learns "they got it"
269−-- only via the recipient's E2E ack.
270−
271−-- True when `s` is non-empty lowercase hex of even length, with `maxLen` ceiling.
272−isValidBoundedHex : Int -> Text -> Bool
273−isValidBoundedHex = \maxLen s -> length s <= maxLen && isValidHex s
274340-- True when `s` is lowercase hex of exactly `exactLen` characters (even by definition).
275341isValidExactHex : Int -> Text -> Bool
276342isValidExactHex = \exactLen s -> length s == exactLen && isValidHex s
277343-- True when `s` is lowercase hex within [`minBlobLen`, `maxBlobLen`]. The floor
278344-- rejects blobs too short to be a real envelope; see `minBlobLen`.
279345isValidBlobHex : Text -> Bool
280−isValidBlobHex = \s -> length s >= minBlobLen && isValidBoundedHex maxBlobLen s
346+isValidBlobHex = \s -> length s >= minBlobLen && length s <= maxBlobLen && isValidHex s
281347-- Hex-encoded Ed25519 public key (32 bytes → 64 chars exact).
282348type PubkeyHex = Text where isValidExactHex 64
283349-- Hex-encoded ciphertext or opaque blob; bounded to [`minBlobLen`, `maxBlobLen`]
@@ -290,6 +356,19 @@ type SignatureHex = Text where isValidExactHex 128
290356-- (`handleRecvGossip`); keeping it out of the type predicate lets the default
291357-- `serverHost = "localhost"` flow through presence rows in a non-federated
292358-- single-node deployment.
359+--
360+-- WHY SERVER NAMES STAY `Text` IN STATE (the canonical note; other sites point
361+-- here). Every server name held in `*presence`, `*forwards`, `*forwardFailures`
362+-- and `Message.deliveredTo` is plain `Text`, never `ServerName`. They all
363+-- originate in `serverHost` — a startup-overridable scalar, so a refined type
364+-- cannot be given a bare literal default and the predicate can only be checked at
365+-- runtime (`localServerName`). `ServerName` is therefore enforced exactly where it
366+-- can be: at the `/federation/gossip` route boundary, where the name is
367+-- peer-supplied (`fromServer: ServerName`). Handlers that receive the refined type
368+-- widen it once, up front (`let server = (serverName : Text)`), because Knot does
369+-- not implicitly coerce between a refined type and its base inside a comparison —
370+-- `f.toServer == server` would otherwise fail to typecheck. Widening is always
371+-- sound (the predicate only adds constraints); narrowing is what needs `refine`.
293372isValidServerName : Text -> Bool
294373isValidServerName = \s -> length s <= maxServerNameLen && s == toLower (stripTrailingDot s)
295374type ServerName = Text where isValidServerName
@@ -309,10 +388,6 @@ type Session = {token: Text, pubkey: PubkeyHex, expiresAt: Timestamp, ip: Text}
309388-- presence re-announce of `toKey` doesn't trigger a duplicate delivery.
310389-- (Single-field record rows, not bare names: the Knot runtime cannot persist
311390-- a nested relation of scalars.)
312−-- Server names are plain `Text`, not `ServerName`: they are sourced from
313−-- `serverHost`, which is a startup-overridable scalar the predicate cannot be
314−-- checked on at declaration time (see `localServerName`). Pubkeys are refined —
315−-- every write site can prove the predicate.
316391type Message = {toKey: PubkeyHex, encryptedBlob: BlobHex, receivedAt: Timestamp, deliveredTo: [{server: Text}]}
317392-- Last-known location of a pubkey, either local (`server == serverHost`) or
318393-- learned from a peer via gossip. Multiple entries per pubkey are allowed.
@@ -347,6 +422,8 @@ type ForwardFailure = {server: Text, failedAt: Timestamp, failures: Int}
347422-- Mailbox: ciphertexts addressed to local recipients, awaiting poll or federation forward.
348423*messages : [Message]
349424-- Last-known location of each pubkey (local sessions and gossiped remote presence).
425+-- Remote (gossiped) rows are capped by `maxPresence` / `maxPresencePerServer` in
426+-- `handleRecvGossip`; local rows are exempt and bounded by `maxSessions` instead.
350427*presence : [PresenceEntry]
351428-- Cross-server outbox: messages queued for delivery to a peer, with retry counts.
352429*forwards : [ForwardEntry]
@@ -372,17 +449,22 @@ type ForwardFailure = {server: Text, failedAt: Timestamp, failures: Int}
372449-- runs before the handler, so it cannot tell a valid session from an invented
373450-- one, and an attacker varying a self-chosen value would get a fresh bucket per
374451-- value. That rules out the bearer token (any string) and the submitted pubkey
375−-- (any keypair) alike — see `authRateLimit`. Each route has an independent
376−-- bucket store, so endpoints using the same key strategy don't share budget
377−-- across routes. Buckets persist in the runtime's `_knot_rate_limits` SQLite
378−-- table; rejection responds 429 before the handler runs.
452+-- (any keypair) alike. A pubkey key is abusable in both directions: an attacker
453+-- rotating keypairs draws a fresh budget with every rotation (a Sybil flood could
454+-- then push sessions through until `maxSessions` starts evicting live ones), and
455+-- flooding a *victim's* pubkey would exhaust that victim's own login budget.
456+-- Per-pubkey exhaustion of the challenge/session pools is bounded separately, by
457+-- `maxChallengesPerKey` and `maxSessionsPerKey` in the handlers. Each route has an
458+-- independent bucket store, so endpoints using the same key strategy don't share
459+-- budget across routes. Buckets persist in the runtime's `_knot_rate_limits`
460+-- SQLite table; rejection responds 429 before the handler runs.
379461
380462-- Suffix of `s` after its last comma, trimmed. X-Forwarded-For is a
381463-- comma-separated chain that each proxy appends to; only the final entry —
382464-- the one written by the nearest trusted proxy — is reliable for bucketing.
383465lastForwardedHop : Text -> Text
384466lastForwardedHop = \s -> if contains "," s
385−then lastForwardedHop (drop 1 s)
467+then lastForwardedHop (afterComma s)
386468else trim s
387469
388470-- The client address for rate-limit bucketing: the last X-Forwarded-For hop
@@ -390,8 +472,8 @@ else trim s
390472-- otherwise the TCP connection address.
391473pickClientIp : Maybe Text -> Text -> Text
392474pickClientIp = \h connIp -> case h of
393− Just {value: ips} -> if trustForwardedFor && lastForwardedHop ips != ""
394− then lastForwardedHop ips
475+ Just {value: ips} -> if trustForwardedFor
476+ then let hop = lastForwardedHop ips in if hop != "" then hop else connIp
395477 else connIp
396478 Nothing {} -> connIp
397479
@@ -448,17 +530,44 @@ capList = \items maxN -> drop (max 0 (count items - maxN)) (sortBy (\x -> x.expi
448530capPerKey : [{pubkey: PubkeyHex, expiresAt: Timestamp | r}] -> PubkeyHex -> Int -> [{pubkey: PubkeyHex, expiresAt: Timestamp | r}]
449531capPerKey = \items pubkey maxN -> union (filter (\x -> not (x.pubkey == pubkey)) items) (capList (filter (\x -> x.pubkey == pubkey) items) (maxN - 1))
450532
533+-- Cap entries matching `server` to maxN, leaving every other server's entries
534+-- untouched. Same shape as `capPerKey` on a different field, but caps to `maxN`
535+-- rather than `maxN - 1`: the sole caller (`handleRecvGossip`) applies this
536+-- *after* merging the peer's new rows in, not before adding one more. Keeps one
537+-- peer from crowding every other peer out of the `maxPresence` pool.
538+capPerServer : [{server: Text, expiresAt: Timestamp | r}] -> Text -> Int -> [{server: Text, expiresAt: Timestamp | r}]
539+capPerServer = \items server maxN -> union (filter (\x -> not (x.server == server)) items) (capList (filter (\x -> x.server == server) items) maxN)
540+
541+-- Cap the whole forwards outbox to `maxForwardsTotal`, evicting the highest-retry
542+-- entries first — see `maxForwardsTotal` for why those and not the oldest.
543+-- Deliberately not `capList`: that keys on `expiresAt`, and `ForwardEntry` carries
544+-- no timestamp (the same reason `retryPendingForwards` has to sort on the blob).
545+-- Applied by both writers that grow `*forwards` (`forwardQueuedToServer` and
546+-- `handleSendMessages`); the retry sweep only ever shrinks it.
547+--
548+-- N4: Sort by `(retries, encryptedBlob)` for determinism. Without the secondary
549+-- key, a `sortBy retries` alone is unstable when many entries share `retries: 0`,
550+-- and any of them could be dropped — including a fresh forward for a healthy
551+-- peer. The blob is a unique secondary key (the dedup invariant guarantees
552+-- `(toKey, encryptedBlob, toServer)` uniqueness), so the sort is total and
553+-- deterministic.
554+capForwards : [ForwardEntry] -> [ForwardEntry]
555+capForwards = \fwds -> take maxForwardsTotal (sortBy (\f -> {retries: f.retries, blob: f.encryptedBlob}) fwds)
556+
451557-- Random hex token: one random hex char per recursive call. `n` is the
452558-- desired length in characters (so n=48 yields 24 random bytes of entropy).
453559-- Session bearers, /auth challenges, and federation auth nonces all use n=48
454560-- (192 bits of entropy, well beyond birthday bound).
455−genToken : Int -> IO {random} Text
456−genToken = \n -> if n <= 0
457−then yield ""
561+-- Tail-recursive: builds the string left-to-right via an accumulator (`acc`),
562+-- appending one hex char per call. Each `acc ++ ...` copies the accumulator,
563+-- so the total work is O(n²) in the length — but n is 48 (192 bits), so this
564+-- is a fixed ~1 KB of copying and not worth a more complex builder.
565+genToken : Int -> Text -> IO {random} Text
566+genToken = \n acc -> if n <= 0
567+then yield acc
458568else do
459569 d <- randomInt 16
460− rest <- genToken (n - 1)
461− yield (take 1 (drop d "0123456789abcdef") ++ rest)
570+ genToken (n - 1) (acc ++ take 1 (drop d "0123456789abcdef"))
462571
463572-- True when `s` is non-empty, even-length, and only lowercase hex digits.
464573-- `chars` yields the *distinct* character set (relations dedupe), which is
@@ -523,14 +632,12 @@ authHost = \s -> if take 1 s == "["
523632then throughBracket s
524633else beforeColon s
525634
526−-- True when the host part is a bare integer (no dots) — a decimal or octal
527−-- "dword" IP like `2130706433` or `017700000001` (both = 127.0.0.1). These
528−-- carry no dotted octets, so the prefix list below never matches them, yet
529−-- they resolve to the same internal addresses.
635+-- True when the host is a bare integer (no dots) — a decimal or octal "dword" IP
636+-- like `2130706433` or `017700000001` (both = 127.0.0.1). These carry no dotted
637+-- octets, so the octet checks below never match them, yet they resolve to the same
638+-- internal addresses. Takes the already-port-stripped host (`beforeColon sn`).
530639isNumericHost : Text -> Bool
531−isNumericHost = \sn ->
532− let host = beforeColon sn in
533− host != "" && all (\c -> contains c "0123456789") (chars host)
640+isNumericHost = \host -> host != "" && all (\c -> contains c "0123456789") (chars host)
534641
535642-- Decimal value of a single hex/ascii digit character.
536643digitValue : Text -> Int
@@ -539,6 +646,17 @@ digitValue = \c -> if c == "0" then 0 else if c == "1" then 1 else if c == "2" t
539646-- Value of an all-digits string (e.g. "172" -> 172); -1 when empty or
540647-- non-numeric. `chars` is fine for the membership guard (set semantics don't
541648-- matter there); the actual parse walks the string in order via take/drop.
649+--
650+-- The accumulator saturates at 2^32 so an overlong all-digits octet cannot
651+-- overflow i64 and panic the handler. `isBadServerName` reaches this via
652+-- `isReservedIPv4` on a peer-supplied name (`/federation/gossip`'s `fromServer`
653+-- only passes a length/lowercase check at the route boundary), so a 19+-digit
654+-- octet like "9999999999999999999.0.0.1" would otherwise abort the request with
655+-- an unhandled `integer overflow in ... * 10`. A real IPv4 octet is 0-255 and
656+-- every `isReservedIPv4` comparison is against a constant <= 255, so saturating
657+-- above that range preserves the result for valid octets while an oversized
658+-- first octet still reads as `>= 224` (reserved → fail-closed). The `* 10`
659+-- stays safe because `acc` is capped at 2^32 before each step.
542660decimalValue : Text -> Int
543661decimalValue = \s -> if s == "" || not all (\c -> contains c "0123456789") (chars s)
544662then -1
@@ -546,7 +664,7 @@ else decimalValueGo 0 s
546664decimalValueGo : Int -> Text -> Int
547665decimalValueGo = \acc s -> if s == ""
548666then acc
549−else decimalValueGo (acc * 10 + digitValue (take 1 s)) (drop 1 s)
667+else decimalValueGo (min 4294967296 (acc * 10 + digitValue (take 1 s))) (drop 1 s)
550668
551669-- Substring of `s` before / after its first ",". Same shape as `beforeDot` /
552670-- `afterDot`, on a different separator.
@@ -565,6 +683,14 @@ else afterComma (drop 1 s)
565683-- is the usual beforeX/afterX recursion. Empty fields survive the split (",,a"
566684-- yields "" twice — relations dedupe, so once) and are dropped by the caller;
567685-- see `seedPeerList`.
686+--
687+-- The `beforeComma`/`afterComma`/`beforeDot`/`afterDot`/`beforeColon` family
688+-- looks ripe to fold into one generic `beforeChar sep s` / `afterChar sep s`.
689+-- Do NOT: routing *this* function's tail recursion through a partially-applied
690+-- `afterChar ","` hangs the Knot compiler indefinitely (confirmed 2026-07-11 —
691+-- a 9-line repro of `splitOnComma = ... splitOnComma (afterChar "," s)` never
692+-- finishes compiling, while the bespoke single-argument `afterComma` compiles
693+-- in ~1 s). The per-separator helpers stay bespoke on purpose.
568694splitOnComma : Text -> [Text]
569695splitOnComma = \s -> if s == ""
570696then ([] : [Text])
@@ -610,85 +736,48 @@ isReservedIPv4 = \host ->
610736-- outright. Gated by `isDottedNumeric` so a digit-led hostname label like
611737-- "0foo.example.com" is never caught (it isn't all-digits-and-dots).
612738hasLeadingZeroOctet : Text -> Bool
613−hasLeadingZeroOctet = \host -> isDottedNumeric host && anyOctetLeadingZero host
614−anyOctetLeadingZero : Text -> Bool
615−anyOctetLeadingZero = \host ->
616− let octet = beforeDot host in
617− let rest = afterDot host in
618− (length octet > 1 && take 1 octet == "0") || (rest != "" && anyOctetLeadingZero rest)
739+hasLeadingZeroOctet = \host ->
740+ isDottedNumeric host &&
741+ (let octet = beforeDot host in
742+ let rest = afterDot host in
743+ (length octet > 1 && take 1 octet == "0") || (rest != "" && hasLeadingZeroOctet rest))
744+
745+-- True when the host's first two labels name a reserved IPv4 range: the zero net
746+-- (0/8), loopback (127/8), and the RFC1918 blocks 10/8, 172.16/12, 192.168/16,
747+-- plus link-local 169.254/16.
748+--
749+-- Deliberately *not* gated on `isDottedNumeric`, unlike `isReservedIPv4` below:
750+-- these run as leading string labels too, matching the literal `"10."` / `"172.16."`
751+-- prefix tests this replaces. So "10.example.com" stays blocked. A non-numeric
752+-- first label parses to -1 via `decimalValue` and matches nothing, so an ordinary
753+-- hostname is never caught.
754+isReservedOctetPrefix : Text -> Bool
755+isReservedOctetPrefix = \host ->
756+ let o1 = decimalValue (beforeDot host) in
757+ let o2 = decimalValue (beforeDot (afterDot host)) in
758+ o1 == 0 || o1 == 10 || o1 == 127 || (o1 == 172 && o2 >= 16 && o2 <= 31) || (o1 == 192 && o2 == 168) || (o1 == 169 && o2 == 254)
619759
620760-- Block private/reserved/internal hostnames (SSRF defense).
621761--
622−-- LIMITATION — this check is purely lexical: it inspects the *string* a peer
623−-- gave us, never the address that string resolves to. An attacker who controls
624−-- DNS for a name that looks perfectly public (`relay.attacker.example`) can
625−-- point it at 127.0.0.1 / 169.254.169.254 / an RFC1918 host and this returns
626−-- False, so `fetch` dials the internal target anyway. Nothing here rules that
627−-- out, and re-resolving before the request wouldn't either (the resolver is
628−-- free to answer differently the second time — a DNS-rebinding TOCTOU). Closing
629−-- it needs resolution and connection to be fused: resolve the name, reject the
630−-- resulting IP against the same reserved ranges, and connect to *that* IP —
631−-- which the `fetch` in use does not expose. Treat the list below as a guard
632−-- against accidental and naive-literal SSRF, not against a motivated attacker
633−-- with a nameserver. Same class of gap as the percent-encoding one noted next.
762+-- LIMITATION — purely lexical: inspects the string, never the resolved address.
763+-- DNS-rebinding TOCTOU and percent-encoding tricks bypass it. A real fix needs
764+-- resolve-then-pin (fuse resolution with connection), which `fetch` doesn't
765+-- expose. See PROTOCOL.md §10. Treat as a guard against naive-literal SSRF, not
766+-- a motivated attacker with a nameserver.
634767--
635−-- Skips percent-encoding
636−-- tricks but covers the high-value cases: `localhost`, RFC1918 ranges (10/8,
637−-- 172.16/12, 192.168/16) plus link-local
638−-- 169.254/16, the IPv4 zero net, CGNAT 100.64/10, benchmarking 198.18/15,
639−-- the TEST-NET ranges 192.0.2/24 and 203.0.113/24, and multicast/reserved
640−-- 224/4+240/4 (any first octet >= 224, via `isReservedIPv4`), bare IPv6
641−-- literals (any string with more than one `:` — covers loopback
642−-- `::`/`::1`, link-local `fe80::/10`, ULA `fc00::/7`, globals like `2001:db8::1`),
643−-- bracketed IPv6 literals, integer/octal "dword" IPv4 (`isNumericHost`), the
644−-- `0x`-prefixed hex form, octal dotted-octet IPv4 (any leading-zero octet, via
645−-- `hasLeadingZeroOctet` — the resolver reads "0177.0.0.1" as 127.0.0.1), and the
646−-- `.local` / `.internal` / `.arpa` / `.onion`
647−-- suffixes. Enforced on inbound requests (`handleRecvGossip`, so a peer can't
648−-- claim a bogus `fromServer`) and again at every federation egress site
768+-- Enforced on inbound (`handleRecvGossip`) and at every egress site
649769-- (`sendBatchedGossip`, `retryPendingForwards`, `forkForwardsTo`) as
650−-- defense-in-depth — state persisted before a denylist tightening, or any
651−-- future ingress gap, must not steer a `fetch` at an internal host.
652−-- A legitimate `host:port` server name has exactly one `:`, so the multi-colon
653−-- check leaves that case intact.
770+-- defense-in-depth — persisted state from before a denylist tightening must
771+-- not steer a `fetch` at an internal host.
654772--
655−-- The name is trailing-dot-stripped (`stripTrailingDot`) before every check.
656−-- The system resolver treats `localhost.` / `foo.internal.` (DNS root form) the
657−-- same as the dotless name, but the bare `== "localhost"` and `.internal`-suffix
658−-- tests would miss the dotted form. Peer-supplied names already arrive stripped
659−-- (`isValidServerName` rejects a trailing dot at the `/federation/gossip`
660−-- boundary), so the only unstripped ingress is `seedPeers`; normalizing here
661−-- keeps the deny-list sound independently of that upstream check — the same
662−-- "don't trust prior validation" posture the rest of this note describes.
773+-- A legitimate `host:port` has exactly one `:`, so the multi-colon check
774+-- rejects bare IPv6 literals. The name is trailing-dot-stripped before every
775+-- check so `localhost.` / `foo.internal.` (DNS root form) are caught.
663776isBadServerName : Text -> Bool
664−isBadServerName = \raw -> let sn = stripTrailingDot raw in sn == "" || sn == "localhost" || hasPrefix "localhost:" sn || isNumericHost sn || isReservedIPv4 (beforeColon sn) || hasLeadingZeroOctet (beforeColon sn) || hasPrefix "0x" sn || any (\c -> not contains c "0123456789abcdefghijklmnopqrstuvwxyz-.:") (chars sn) || countChar ":" sn > 1 || any (\p -> hasPrefix p sn) [
665− ".",
666− ":",
667− "[",
668− "127.",
669− "10.",
670− "192.168.",
671− "169.254.",
672− "192.0.2.",
673− "203.0.113.",
674− "0.",
675− "172.16.",
676− "172.17.",
677− "172.18.",
678− "172.19.",
679− "172.20.",
680− "172.21.",
681− "172.22.",
682− "172.23.",
683− "172.24.",
684− "172.25.",
685− "172.26.",
686− "172.27.",
687− "172.28.",
688− "172.29.",
689− "172.30.",
690− "172.31."
691−] || any (\s -> hasSuffix s sn) [".localhost", ".local", ".internal", ".arpa", ".onion"]
777+isBadServerName = \raw ->
778+ let sn = stripTrailingDot raw in
779+ let host = beforeColon sn in
780+ sn == "" || sn == "localhost" || hasPrefix "localhost:" sn || isNumericHost host || isReservedOctetPrefix host || isReservedIPv4 host || hasLeadingZeroOctet host || hasPrefix "0x" sn || any (\c -> not contains c "0123456789abcdefghijklmnopqrstuvwxyz-.:") (chars sn) || countChar ":" sn > 1 || any (\p -> hasPrefix p sn) [".", ":", "192.0.2.", "198.51.100.", "203.0.113."] || any (\s -> hasSuffix s sn) [".localhost", ".local", ".internal", ".arpa", ".onion"]
692781
693782-- ============================================
694783-- Auth helpers
@@ -729,6 +818,23 @@ clientIpOf = \h -> case h of
729818
730819-- Resolve a Bearer token to its session pubkey if the session is unexpired and
731820-- the client IP matches. Returns Nothing on missing/invalid token.
821+--
822+-- TIMING SIDE-CHANNEL (known gap, not fixable in Knot today). `s.token == token`
823+-- is ordinary string equality, which almost certainly short-circuits on the first
824+-- differing byte. An attacker who can time the response therefore learns how many
825+-- leading characters of a guess were correct, and can in principle extend a guessed
826+-- prefix one hex char at a time instead of searching the whole space. Two things
827+-- bound that today, neither of which is a fix:
828+-- * the token is 48 random hex chars (192 bits, `genToken`), so a blind guess is
829+-- hopeless and the attacker is forced onto the timing channel to make progress;
830+-- * `/poll` and `/messages` are per-IP rate limited, and the linear scan over
831+-- `*sessions` adds noise on the order of the comparison itself, so the number
832+-- of samples needed to resolve a per-byte difference over a network is large.
833+-- Neither argument is a security guarantee — they raise the cost of the attack, they
834+-- do not remove it. The correct fix is a `constantTimeEquals : Text -> Text -> Bool`
835+-- primitive in the Knot runtime (a byte-wise XOR-and-accumulate compare that always
836+-- reads both strings in full); swap the `s.token == token` conjunct for it as soon as
837+-- one exists. See PROTOCOL.md §6, *Error Responses*.
732838authedPubkey : Text -> Int<Ms> -> Text -> IO {r *sessions} (Maybe PubkeyHex)
733839authedPubkey = \authorization t clientIp -> do
734840 ses <- *sessions
@@ -820,12 +926,8 @@ hasLocalPresence = \pres pk t -> any (\p -> p.pubkey == pk && isLocalServer p.se
820926-- Project items through `getServer`, drop our own hostname, and dedupe.
821927-- Used to derive peer recipient lists from forwards/presence/etc.
822928--
823−-- Returns `[Text]`, the base type of `ServerName`. Server names stay unrefined
824−-- internally: they originate in `serverHost`, a startup-overridable scalar whose
825−-- predicate can only be checked at runtime (`localServerName`). The refined
826−-- `ServerName` is enforced where it can be — at the `/federation/gossip` route
827−-- boundary (`fromServer: ServerName`) and at federation egress, where
828−-- `isBadServerName` applies the SSRF deny-list the predicate deliberately omits.
929+-- Returns `[Text]`, the base type of `ServerName` — see `type ServerName` for why
930+-- server names stay unrefined everywhere in state.
829931collectPeers : [a] -> (a -> Text) -> [Text]
830932collectPeers = \items getServer -> filter (\s -> not isLocalServer s) (map getServer items)
831933
@@ -839,18 +941,77 @@ currentSeq = \rows -> fold (\acc r -> max acc r.value) (0 : Timestamp) rows
839941-- Append one ciphertext to the local mailbox under a fresh monotonic
840942-- sequence. Row-level STM retry on `*messages` wakes any parked /poll
841943-- transaction whose filter matches the new row. Caller wraps in `atomic`.
944+--
945+-- Idempotent on (toKey, encryptedBlob): an identical ciphertext already in the
946+-- mailbox is left alone rather than appended again. Both ingress paths need this
947+-- — a client retry after a lost response (`handleSendMessages`) and a peer's
948+-- re-forward after a lost 200 (`handleForwardMessage`) carry the identical blob,
949+-- and the fresh `seqTs` below would otherwise make `union` keep both rows and
950+-- double-deliver. Re-reading `*messages` per call also collapses duplicate blobs
951+-- appearing twice within one batch.
952+--
953+-- N3: This O(n) scan is a CPU amplification vector. A batch of 100 identical
954+-- blobs to the same recipient triggers 100 × O(|messages|) comparisons. With
955+-- |messages| = 10000, that's 1M comparisons per request, bounded by the 60/min
956+-- rate limit. A real fix needs an index on (toKey, encryptedBlob) or a
957+-- hash-based dedup set — both require runtime support not available in Knot
958+-- today. Documented as an accepted DoS surface.
842959appendMessage : PubkeyHex -> BlobHex -> Int<Ms> -> IO {rw *messages, rw *seqCounter} {}
843960appendMessage = \toKey encryptedBlob t -> do
844961 msgs <- *messages
845− seqRows <- *seqCounter
846− let seqTs = max t (currentSeq seqRows + 1)
847− *seqCounter = [{value: seqTs}]
848− *messages = union msgs [{toKey, encryptedBlob, receivedAt: seqTs, deliveredTo: []}]
849−
850−-- True when `f` is the queued forward of `blob` to `server`. Used to dedupe
851−-- per-(blob, server) entries on the forwards outbox.
852−forwardMatches : BlobHex -> Text -> ForwardEntry -> Bool
853−forwardMatches = \blob server f -> f.encryptedBlob == blob && f.toServer == server
962+ when (not any (\m -> m.toKey == toKey && m.encryptedBlob == encryptedBlob) msgs) (do
963+ seqRows <- *seqCounter
964+ let seqTs = max t (currentSeq seqRows + 1)
965+ *seqCounter = [{value: seqTs}]
966+ -- Enforce `maxMessagesPerRecipient` before the append: evict the oldest rows
967+ -- for this recipient so the post-append count lands exactly on the ceiling.
968+ -- `- 1` reserves the slot the new row is about to take.
969+ --
970+ -- S4: Instead of building an `evicted` list and checking membership (which
971+ -- is O(|messages| × |evicted|)), compute the eviction threshold — the
972+ -- receivedAt of the (maxMessagesPerRecipient - 1)th oldest message for this
973+ -- recipient — and keep only messages newer than it. This is O(|messages|)
974+ -- with no inner scan.
975+ let forRecipient = filter (\m -> m.toKey == toKey) msgs
976+ let excess = max 0 (count forRecipient - (maxMessagesPerRecipient - 1))
977+ let sortedRecipient = sortBy (\m -> m.receivedAt) forRecipient
978+ -- The threshold: the receivedAt of the last row we want to evict.
979+ -- Rows with receivedAt <= threshold are evicted; rows > threshold survive.
980+ let evictionThreshold = if excess > 0
981+ then case take excess sortedRecipient of
982+ [] -> 0
983+ xs -> case last xs of
984+ {receivedAt: r} -> r
985+ else 0
986+ let kept = filter (\m -> not (m.toKey == toKey && m.receivedAt <= evictionThreshold && excess > 0)) msgs
987+ -- Global cap (S6): after the per-recipient eviction, bound the total mailbox
988+ -- across all recipients by dropping the globally-oldest rows. Only runs on
989+ -- overflow, so the O(n log n) sort is off the hot path. Dropped rows may
990+ -- belong to other recipients; their orphaned *forwards are reclaimed by
991+ -- `pruneExpired`, and their lost `deliveredTo` is harmless (the blob is gone).
992+ let globallyCapped = if count kept > maxMessagesTotal
993+ then drop (count kept - maxMessagesTotal) (sortBy (\m -> m.receivedAt) kept)
994+ else kept
995+ *messages = union globallyCapped [{toKey, encryptedBlob, receivedAt: seqTs, deliveredTo: []}])
996+
997+-- Record that `server` has accepted a federated forward of this message, so a
998+-- later presence re-announce of `toKey` doesn't re-forward the same blob to a peer
999+-- that already has it. No-op when the peer is already listed. Caller wraps in
1000+-- `atomic`.
1001+markDelivered : PubkeyHex -> BlobHex -> Text -> IO {rw *messages} {}
1002+markDelivered = \toKey blob server -> do
1003+ msgs <- *messages
1004+ *messages = map (\m -> if m.toKey == toKey && m.encryptedBlob == blob && not any (\d -> d.server == server) m.deliveredTo
1005+ then {m.toKey, m.encryptedBlob, m.receivedAt, deliveredTo: union m.deliveredTo [{server}]}
1006+ else m) msgs
1007+
1008+-- True when `f` is the queued forward of `blob` to `toKey` at `server`. Used to
1009+-- dedupe entries on the forwards outbox. All three fields matter: the same blob
1010+-- can legitimately be queued to the same peer for two *different* recipients (a
1011+-- sender fanning one ciphertext out to several keys), and matching on
1012+-- (blob, server) alone would let completing one of them drop the others.
1013+forwardMatches : PubkeyHex -> BlobHex -> Text -> ForwardEntry -> Bool
1014+forwardMatches = \toKey blob server f -> f.toKey == toKey && f.encryptedBlob == blob && f.toServer == server
8541015
8551016-- Replace any local presence rows for `pubkey` with one fresh row at
8561017-- `expiry`, and return the post-update peer broadcast set. Caller wraps in
@@ -866,27 +1027,40 @@ refreshLocalPresence = \pubkey expiry -> do
8661027-- ============================================
8671028-- Pruning
8681029-- ============================================
869−-- Single sweep that drops expired entries from every state ref in one atomic
870−-- block. Returns the locally-expired presence rows whose pubkey has no other
871−-- live local session, so the caller can broadcast offline gossip for them.
8721030
8731031-- One sweep over every state ref: drops expired rows in a single atomic block.
8741032-- Returns the locally-expired presence rows whose pubkey has no other live
8751033-- local session, so the caller can broadcast offline gossip for them.
876−pruneExpired : Int<Ms> -> IO {rw *challenges, rw *forwardFailures, rw *messages, rw *presence, rw *sessions} [PubkeyHex]
1034+-- Also prunes orphaned *forwards entries whose message has been removed by
1035+-- the TTL sweep — a 404-deferred forward (recipient never online at the peer)
1036+-- would otherwise stay forever with retries=0, retried every sweep indefinitely.
1037+pruneExpired : Int<Ms> -> IO {rw *challenges, rw *forwardFailures, rw *forwards, rw *messages, rw *presence, rw *sessions} [PubkeyHex]
8771038pruneExpired = \t -> atomic do
8781039 ch <- *challenges
8791040 *challenges = filter (\x -> x.expiresAt > t) ch
8801041 ses <- *sessions
8811042 *sessions = filter (\x -> x.expiresAt > t) ses
8821043 msgs <- *messages
883− *messages = filter (\m -> t - m.receivedAt < messageMaxAge) msgs
1044+ let surviving = filter (\m -> t - m.receivedAt < messageMaxAge) msgs
1045+ *messages = surviving
1046+ -- Prune forwards whose message was removed by the TTL sweep above.
1047+ -- ForwardEntry carries no timestamp, so match against the surviving
1048+ -- messages (the post-sweep list, not the pre-sweep snapshot).
1049+ --
1050+ -- S5: This is O(|forwards| × |surviving|) — a quadratic scan. In practice
1051+ -- |forwards| is usually far below maxForwardsTotal (50000) and |surviving|
1052+ -- is bounded by maxMessagesTotal (1000000), so the cost is modest. A real
1053+ -- fix needs a set/index keyed on (toKey, encryptedBlob), which the Knot
1054+ -- runtime does not expose today. Documented as an accepted design tradeoff.
1055+ fw <- *forwards
1056+ *forwards = filter (\f -> any (\m -> m.toKey == f.toKey && m.encryptedBlob == f.encryptedBlob) surviving) fw
8841057 ff <- *forwardFailures
8851058 *forwardFailures = filter (\f -> t - f.failedAt < forwardFailureMaxAge) ff
8861059 -- presence: remember locally-expired keys for offline gossip
8871060 pres <- *presence
888− *presence = filter (\p -> p.expiresAt > t) pres
889− let liveLocalPubkeys = map (\p -> p.pubkey) (filter (\p -> isLocalServer p.server && p.expiresAt > t) pres)
1061+ let live = filter (\p -> p.expiresAt > t) pres
1062+ *presence = live
1063+ let liveLocalPubkeys = map (\p -> p.pubkey) (filter (\p -> isLocalServer p.server) live)
8901064 yield (map (\p -> p.pubkey) (filter (\p -> p.expiresAt <= t && isLocalServer p.server && not elem p.pubkey liveLocalPubkeys) pres))
8911065
8921066-- ============================================
@@ -909,7 +1083,7 @@ pruneExpired = \t -> atomic do
9091083-- rows, and from then on it is reachable through the `peers` half of this union
9101084-- like any other peer.
9111085gossipTargets : [Text] -> [Text]
912−gossipTargets = \peers -> filter (\s -> not isLocalServer s) (union peers seedPeerList)
1086+gossipTargets = \peers -> union peers seedPeerList
9131087
9141088-- Fan out one bundle of gossip events to each peer (presence-learned peers and
9151089-- bootstrap seeds alike), skipping denylisted peers and peers in backoff. No-op
@@ -940,48 +1114,70 @@ sendBatchedGossip = \peers events -> case localServerName of
9401114-- comes online: any messages already buffered for that pubkey are enqueued
9411115-- as forwards to the newly-known server.
9421116
943−-- Attempt every forward in `batch` to one peer, in order, and report whether any
944−-- attempt failed. Drops successful entries from `*forwards` and records the peer
945−-- on the message's `deliveredTo`; on failure bumps the retry count and gives up
946−-- after `maxForwardRetries`.
1117+-- Attempt every forward in `batch` to one peer, in order, and report both whether
1118+-- any attempt was a genuine peer failure (`anyFailed`) and whether any attempt
1119+-- genuinely succeeded (`anySucceeded`). Drops successful entries from `*forwards`
1120+-- and records the peer on the message's `deliveredTo`; every attempt (success,
1121+-- failure, or 404) bumps the retry count and gives up after `maxForwardRetries`.
1122+--
1123+-- INVARIANT — this must not touch `*forwardFailures`. The caller records at most one
1124+-- failure per peer per sweep, from the `anyFailed` flag returned here; recording per
1125+-- failing *message* would let one unreachable peer with N buffered messages take N
1126+-- backoff steps in a single sweep and pin itself at `retryBackoffMax` for
1127+-- `forwardFailureMaxAge`. The counter counts consecutive failed *sweeps*.
9471128--
948−-- Deliberately does *not* touch `*forwardFailures` — the caller records at most
949−-- one failure per peer per sweep from the Bool this returns. Recording per failing
950−-- *message* (as this loop used to) let a peer holding N buffered messages take N
951−-- backoff steps in a single sweep: one unreachable peer with a full outbox jumped
952−-- straight to `retryBackoffMax` and `forwardFailureMaxAge` then pinned it there for
953−-- 24 h, so the peer stayed un-retried long after it came back. The counter is meant
954−-- to count consecutive failed *sweeps*, and now does.
1129+-- A 404 is NOT a peer failure. `handleForwardMessage` answers 404 `no_presence`
1130+-- whenever the recipient is not *currently* online at that peer, which is an
1131+-- expected, retryable outcome (PROTOCOL.md §7) — the peer is healthy and answering.
1132+-- `fetch` returns `Err` for every status >= 400, so treating any `Err` as a failure
1133+-- would feed a routine 404 into `recordFailure`, and `*forwardFailures` is shared
1134+-- with gossip: one stale-presence 404 would suppress all forwards *and* all gossip to
1135+-- that peer for a full backoff step (30 s–8 min). So a 404 leaves the peer's backoff
1136+-- untouched (`anyFailed` stays false for it) and never clears it (`anySucceeded`
1137+-- stays false too).
1138+--
1139+-- But a 404 DOES bump the forward's retry count now (S1). It previously left the row
1140+-- entirely untouched, so a forward whose recipient never came online at the peer was
1141+-- retried every sweep for the full 30-day message TTL — the counter never advanced,
1142+-- so `maxForwardRetries` was never reached. Counting the attempt (without charging
1143+-- the peer's backoff) lets the forward hit the cap and be dropped after
1144+-- `maxForwardRetries` sweeps while still not penalizing a healthy peer.
9551145--
9561146-- Recursive rather than `forEach` because the result has to be accumulated across
9571147-- iterations; `sortBy` fixes the iteration order that `head`/`drop 1` then walk.
958−retryForwardsTo : Text -> [ForwardEntry] -> IO {rw *forwards, rw *messages, network} Bool
1148+retryForwardsTo : Text -> [ForwardEntry] -> IO {rw *forwards, rw *messages, network} {anyFailed: Bool, anySucceeded: Bool}
9591149retryForwardsTo = \server batch -> case head batch of
960− Nothing {} -> yield (False {})
1150+ Nothing {} -> yield {anyFailed: False {}, anySucceeded: False {}}
9611151 Just {value: f} -> do
9621152 result <- fetch (federationUrl server) (ForwardMessage {f.toKey, f.encryptedBlob})
963− let success = case result of
964− Err _ -> False {}
965− Ok _ -> True {}
966− let isMatch = forwardMatches f.encryptedBlob server
1153+ let status = case result of
1154+ Err {error: e} -> e.status
1155+ Ok _ -> 200
1156+ let success = status < 400
1157+ -- Recipient simply isn't online at the peer yet: hold the peer blameless, but
1158+ -- still count the attempt so the row can't outlive the message TTL (S1).
1159+ let deferred = status == 404
1160+ let isMatch = forwardMatches f.toKey f.encryptedBlob server
9671161 let isDone = \x -> isMatch x && (success || x.retries + 1 >= maxForwardRetries)
9681162 atomic (do
9691163 cur <- *forwards
1164+ -- Count the attempt regardless of outcome: a 404 still consumes a retry slot
1165+ -- so a forward that never finds the recipient online is eventually dropped
1166+ -- (S1). On success or after `maxForwardRetries`, `isDone` filters the row out
1167+ -- first, so the increment then no-ops on an absent row.
9701168 *forwards = map (\x -> if isMatch x
9711169 then {x.toServer, x.toKey, x.encryptedBlob, retries: x.retries + 1}
9721170 else x) (filter (\x -> not isDone x) cur)
973− when success (do
974− msgs <- *messages
975− *messages = map (\m -> if m.toKey == f.toKey && m.encryptedBlob == f.encryptedBlob && not any (\d -> d.server == server) m.deliveredTo
976− then {m.toKey, m.encryptedBlob, m.receivedAt, deliveredTo: union m.deliveredTo [{server}]}
977− else m) msgs))
978− restFailed <- retryForwardsTo server (drop 1 batch)
979− yield (not success || restFailed)
1171+ when success (markDelivered f.toKey f.encryptedBlob server))
1172+ rest <- retryForwardsTo server (drop 1 batch)
1173+ yield {anyFailed: (not success && not deferred) || rest.anyFailed, anySucceeded: success || rest.anySucceeded}
9801174
9811175-- Walk pending forwards grouped by destination and retry each peer's backlog (up
9821176-- to maxBatchSize per peer) via `/federation/forward`. One failure record per peer
983−-- per sweep: a sweep in which every attempt succeeded clears the peer's backoff, a
984−-- sweep with any failure takes exactly one backoff step (see `retryForwardsTo`).
1177+-- per sweep: a sweep with any genuine failure takes exactly one backoff step; a
1178+-- sweep with at least one genuine success clears the peer's backoff; an all-404
1179+-- sweep leaves the backoff untouched, neither charging nor clearing it (S1). See
1180+-- `retryForwardsTo`.
9851181retryPendingForwards : IO {rw *forwardFailures, rw *forwards, rw *messages, network, clock} {}
9861182retryPendingForwards = do
9871183 t <- now
@@ -996,50 +1192,71 @@ retryPendingForwards = do
9961192 cur <- *forwards
9971193 *forwards = filter (\x -> x.toServer != server) cur)
9981194 else when (shouldRetryServer server t failures) (do
999− -- Order the per-peer backlog deterministically before `take maxBatchSize`:
1000− -- `[a]` is an unordered set, so an unsorted `take` returns an
1001− -- implementation-defined subset that could keep retrying the same entries
1002− -- while starving others past the cap. A stable key drains a fixed prefix as
1003− -- entries succeed (removed) or hit `maxForwardRetries` (dropped). (Same class
1004− -- of fix as `forwardQueuedToServer`'s `sortBy receivedAt`; `ForwardEntry`
1005− -- carries no timestamp, so key on the unique blob.)
1195+ -- INVARIANT — `[a]` is an unordered set, so the backlog must be sorted before
1196+ -- `take maxBatchSize` or the batch is an implementation-defined subset that
1197+ -- could keep retrying the same entries while starving others past the cap. A
1198+ -- stable key drains a fixed prefix as entries succeed (removed) or hit
1199+ -- `maxForwardRetries` (dropped). `ForwardEntry` carries no timestamp, so key on
1200+ -- the unique blob.
10061201 let batch = take maxBatchSize (sortBy (\f -> f.encryptedBlob) (filter (\f -> f.toServer == server) fwds))
1007− anyFailed <- retryForwardsTo server batch
1008− -- `count batch > 0` guards the clear: `maxBatchSize` is startup-overridable,
1009− -- and at 0 every batch is empty — an empty sweep must not be read as a
1010− -- success and reset a failing peer's backoff.
1011− if anyFailed
1202+ result <- retryForwardsTo server batch
1203+ -- Clear the peer's backoff only on a sweep with at least one genuine success
1204+ -- (S1). An all-404 sweep (recipient not online at the peer) is neither a
1205+ -- failure nor a success: clearing backoff on it would reset the peer to
1206+ -- "fresh" every sweep, firing a retry every `backgroundPruneInterval` for the
1207+ -- full 30-day message TTL. `count batch > 0` also guards against reading an
1208+ -- empty sweep (possible with a startup-overridden `maxBatchSize` of 0) as
1209+ -- meaningful.
1210+ if result.anyFailed
10121211 then recordFailure server t
1013− else when (count batch > 0) (clearFailure server t)))
1212+ else when (count batch > 0 && result.anySucceeded) (clearFailure server t)))
10141213
10151214-- Forward queued messages to a server when a remote key comes online.
10161215-- Skips messages already delivered to `server` (tracked via Message.deliveredTo)
10171216-- so a presence re-announce after a TTL lapse doesn't duplicate delivery.
10181217--
1019−-- SECURITY: this function trusts `*presence`, and `*presence` is writable by any
1020−-- unauthenticated host via `/federation/gossip`. A forged `online` announcement
1021−-- therefore redirects a victim's queued ciphertext to the attacker's server —
1022−-- see the gossip-redirect note on `handleRecvGossip` for the full threat model
1023−-- and why it is an accepted v0.1 limitation. Do not add a caller that widens
1024−-- what this forwards (e.g. dropping the `deliveredTo` filter) without revisiting
1025−-- that note.
1218+-- SECURITY: this is the function the gossip-redirect attack in the section header
1219+-- above actually cashes out through — it routes on `*presence`, which any
1220+-- unauthenticated host can write. Do not add a caller that widens what this
1221+-- forwards (e.g. dropping the `deliveredTo` filter) without revisiting that note.
10261222forwardQueuedToServer : PubkeyHex -> ServerName -> IO {rw *forwards, r *messages} {}
10271223forwardQueuedToServer = \pubkey serverName -> atomic (do
1028− -- Widen the refined `ServerName` to its base `Text` once, up front. Server names
1029− -- are plain `Text` everywhere in state (`ForwardEntry.toServer`,
1030− -- `Message.deliveredTo`, `PresenceEntry.server` — see `collectPeers` for why),
1031− -- and Knot does not implicitly coerce between a refined type and its base inside
1032− -- a comparison: `f.toServer == server` would try to use the `Text` field where a
1033− -- `ServerName` is required and fail to typecheck. Widening is always sound (the
1034− -- predicate only ever adds constraints); narrowing is what needs `refine`.
10351224 let server = (serverName : Text)
10361225 msgs <- *messages
10371226 fwds <- *forwards
1038− let existing = count (filter (\f -> f.toServer == server) fwds)
1227+ let existing = countWhere (\f -> f.toServer == server) fwds
10391228 let budget = max 0 (maxForwardsPerServer - existing)
1040− let candidates = filter (\m -> m.toKey == pubkey && not any (forwardMatches m.encryptedBlob server) fwds && not any (\d -> d.server == server) m.deliveredTo) msgs
1229+ let notYetForwarded = \m -> not any (forwardMatches m.toKey m.encryptedBlob server) fwds
1230+ let notYetDelivered = \m -> not any (\d -> d.server == server) m.deliveredTo
1231+ let candidates = filter (\m -> m.toKey == pubkey && notYetForwarded m && notYetDelivered m) msgs
10411232 let newFwds = map (\m -> {toServer: server, m.toKey, m.encryptedBlob, retries: 0}) (take budget (sortBy (\m -> m.receivedAt) candidates))
1042− *forwards = union fwds newFwds)
1233+ *forwards = capForwards (union fwds newFwds))
1234+
1235+-- Batched version of `forwardQueuedToServer`: stage forwards for *all* newly-online
1236+-- keys in a single mailbox scan (S4). Calling `forwardQueuedToServer` per key scans
1237+-- `*messages` once per key, which is why `handleRecvGossip` previously capped the
1238+-- number of keys at `maxNewlyOnlineForwards` (N13) — but that cap silently deferred
1239+-- delivery past the 10th key, and a re-announce within the TTL never recovered it
1240+-- (the `deliveredTo`/presence state made the key look already-handled). A single
1241+-- pass bounds the cost to O(|messages|) regardless of how many keys came online.
1242+--
1243+-- SECURITY: shares `forwardQueuedToServer`'s exposure — it routes on gossip-written
1244+-- presence. The same `deliveredTo` / `notYetForwarded` / per-peer budget guards
1245+-- apply; do not widen them without revisiting the gossip-redirect note above.
1246+forwardQueuedToAll : [PubkeyHex] -> ServerName -> IO {rw *forwards, r *messages} {}
1247+forwardQueuedToAll = \pubkeys serverName -> atomic (do
1248+ let server = (serverName : Text)
1249+ msgs <- *messages
1250+ fwds <- *forwards
1251+ let existing = countWhere (\f -> f.toServer == server) fwds
1252+ let budget = max 0 (maxForwardsPerServer - existing)
1253+ let notYetForwarded = \m -> not any (forwardMatches m.toKey m.encryptedBlob server) fwds
1254+ let notYetDelivered = \m -> not any (\d -> d.server == server) m.deliveredTo
1255+ -- `elem m.toKey pubkeys` is O(|pubkeys|), but `pubkeys` is bounded by
1256+ -- `maxGossipEvents` (100), so the scan stays O(|messages|) overall.
1257+ let candidates = filter (\m -> elem m.toKey pubkeys && notYetForwarded m && notYetDelivered m) msgs
1258+ let newFwds = map (\m -> {toServer: server, m.toKey, m.encryptedBlob, retries: 0}) (take budget (sortBy (\m -> m.receivedAt) candidates))
1259+ *forwards = capForwards (union fwds newFwds))
10431260
10441261-- ============================================
10451262-- Handler: challenge / verify
@@ -1058,75 +1275,115 @@ forwardQueuedToServer = \pubkey serverName -> atomic (do
10581275-- Capped per-key (maxChallengesPerKey); per-client-IP rate limiting is enforced
10591276-- by the route's `rateLimit` clause. The IP is recorded so /auth/verify can
10601277-- require the same client.
1278+--
1279+-- A full pool LRU-evicts rather than rejecting, exactly as `handleVerifyAuth` does
1280+-- for `maxSessions`. Answering 503 once `maxChallenges` is reached would hand any
1281+-- attacker who can fill the pool a total login outage — nobody can start a
1282+-- handshake, including clients whose challenges are already in flight. Evicting the
1283+-- soonest-to-expire challenge instead degrades to "an abandoned challenge may be
1284+-- dropped before its 60 s window elapses", which costs the affected client one
1285+-- retry. The freshly-issued row always survives its own `capList`: it carries the
1286+-- latest `expiresAt` of any live challenge by construction.
10611287handleChallenge : PubkeyHex -> Text -> IO {rw *challenges, clock, random} (Result HttpError {challenge: Text, expiresAt: Timestamp})
10621288handleChallenge = \pubkey clientIp -> do
10631289 t <- now
1064− challenge <- genToken 48
1290+ challenge <- genToken 48 ""
10651291 let expiresAt = t + challengeExpiry
10661292 atomic (do
10671293 ch <- *challenges
10681294 let cappedActive = capPerKey (filter (\c -> c.expiresAt > t) ch) pubkey maxChallengesPerKey
1069− if count cappedActive >= maxChallenges
1070− then yield (Err {error: {status: 503, message: "capacity"}})
1071− else do
1072− *challenges = union cappedActive [{pubkey, challenge, expiresAt, ip: clientIp}]
1073− yield (Ok {value: {challenge, expiresAt}}))
1295+ *challenges = capList (union cappedActive [{pubkey, challenge, expiresAt, ip: clientIp}]) maxChallenges
1296+ yield (Ok {value: {challenge, expiresAt}}))
10741297
10751298-- POST /auth/verify: validate `signature` over `challenge` for `pubkey`.
10761299-- On success, mints a session token, records local presence (`pubkey` is now
10771300-- live on this server), and gossips an `online` event to known peers. If
10781301-- `revokeOthers` is set, all other sessions for the same pubkey are dropped.
1079−handleVerifyAuth : PubkeyHex -> Text -> Text -> Bool -> Text -> IO {rw *challenges, rw *forwardFailures, rw *presence, rw *sessions, network, clock, random} (Result HttpError {expiresAt: Timestamp, token: Text})
1302+handleVerifyAuth : PubkeyHex -> Text -> Text -> Bool -> Text -> IO {rw *challenges, rw *forwardFailures, rw *presence, rw *sessions, network, clock, random, console} (Result HttpError {expiresAt: Timestamp, token: Text})
10801303handleVerifyAuth = \pubkey challenge signature revokeOthers clientIp -> do
10811304 t <- now
10821305 let expiry = t + sessionExpiry
1083− token <- genToken 48
1306+ token <- genToken 48 ""
10841307 -- The client signs (target host, challenge) under a domain-separation tag so a
10851308 -- relay server cannot replay the signature to a different server. We verify
10861309 -- against our own configured hostname (port stripped), which a relay cannot forge.
1310+ --
1311+ -- Signature verification is split out of the session-install transaction (S7).
1312+ -- Phase 1 is a cheap read-only atomic that confirms a matching, unexpired,
1313+ -- IP-bound challenge exists — the original CPU-DoS guard, which still spends no
1314+ -- Ed25519 CPU on /auth/verify calls that have no matching challenge. Phase 2 runs
1315+ -- the expensive `verify` *outside* any atomic, so an STM retry on the phase-3
1316+ -- install transaction (triggered by concurrent writes to *challenges/*sessions)
1317+ -- never re-executes it — previously `verify` sat inside that transaction and every
1318+ -- retry re-ran the Ed25519 check. Phase 3 re-checks the challenge before consuming
1319+ -- it, closing the TOCTOU window opened between phases 1 and 3.
10871320 let signedText = "skrepka-auth-v1:" ++ authHost serverHost ++ ":" ++ challenge
1088− let sigValid = case bytesFromHex pubkey of
1089− Just {value: pk} -> case bytesFromHex signature of
1090− Just {value: sigBytes} -> verify pk (textToBytes signedText) sigBytes
1091− _ -> False {}
1092− _ -> False {}
1093− result <- atomic (do
1321+ challengeOk <- atomic (do
10941322 ch <- *challenges
10951323 let same = \c -> c.pubkey == pubkey && c.challenge == challenge
1096− let valid = any (\c -> same c && c.expiresAt > t && matchIp clientIp c.ip) ch && sigValid
1097− if not valid
1098− then yield (Nothing {})
1324+ case findFirst ch same of
1325+ Nothing {} -> yield (False {})
1326+ Just {value: c} -> yield (c.expiresAt > t && matchIp clientIp c.ip))
1327+ if not challengeOk
1328+ then yield (Err {error: {status: 401, message: "invalid"}})
1329+ else do
1330+ -- Phase 2: verify OUTSIDE any atomic. Expensive, and must not be re-executed on
1331+ -- an STM retry of the install transaction below (S7).
1332+ let sigValid = case bytesFromHex pubkey of
1333+ Just {value: pk} -> case bytesFromHex signature of
1334+ Just {value: sigBytes} -> verify pk (textToBytes signedText) sigBytes
1335+ _ -> False {}
1336+ _ -> False {}
1337+ if not sigValid
1338+ then yield (Err {error: {status: 401, message: "invalid"}})
10991339 else do
1100− *challenges = filter (\c -> not same c) ch
1101− ses <- *sessions
1102− let pruned = if revokeOthers
1103− then filter (\s -> s.pubkey != pubkey) ses
1104− else capPerKey ses pubkey maxSessionsPerKey
1105− let newSession = {token, pubkey, expiresAt: expiry, ip: clientIp}
1106− -- LIMITATION — global LRU eviction is Sybil-floodable. `capList` evicts the
1107− -- soonest-to-expire sessions once the global `maxSessions` pool is full, and
1108− -- it does not care whose they are: an attacker minting fresh keypairs (free)
1109− -- from enough IPs to stay under `authRateLimit` can push `maxSessions` worth
1110− -- of throwaway sessions through and evict *live* users' sessions, which
1111− -- shows up client-side as a 401 and a forced re-handshake.
1112− --
1113− -- `maxSessionsPerKey` bounds any single key's share, and the per-IP
1114− -- `authRateLimit` bounds the rate from any single source, so the flood needs
1115− -- real distributed resources. Deliberately not fixed with a per-IP session
1116− -- cap: `clientIp` is empty for every session whenever there is no trusted
1117− -- proxy (`clientIpOf`), so such a cap would collapse to a single global
1118− -- bucket in exactly the deployments that have no XFF — and even with a proxy
1119− -- it would punish carrier-NAT users, where thousands of legitimate clients
1120− -- genuinely do share one address. A real fix prices session creation (proof
1121− -- of work, or a per-key deposit) rather than counting IPs.
1122− *sessions = capList (union pruned [newSession]) maxSessions
1123− peers <- refreshLocalPresence pubkey expiry
1124− yield (Just {value: peers}))
1125− case result of
1126− Nothing {} -> yield (Err {error: {status: 401, message: "invalid"}})
1127− Just {value: peers} -> do
1128− when federationEnabled (fork (sendBatchedGossip peers [{eventType: "online", pubkey: Just {value: pubkey}}]))
1129− yield (Ok {value: {token, expiresAt: expiry}})
1340+ -- Phase 3: re-check the challenge (it may have expired or been consumed by a
1341+ -- concurrent verify since phase 1), consume it, and install the session. The
1342+ -- body is cheap, so an STM retry here costs almost nothing.
1343+ result <- atomic (do
1344+ ch <- *challenges
1345+ let same = \c -> c.pubkey == pubkey && c.challenge == challenge
1346+ let matchingChallenge = findFirst ch same
1347+ case matchingChallenge of
1348+ Nothing {} -> yield (Nothing {})
1349+ Just {value: c} -> do
1350+ if not (c.expiresAt > t && matchIp clientIp c.ip)
1351+ then yield (Nothing {})
1352+ else do
1353+ -- Consume the challenge and optionally revoke other sessions + challenges.
1354+ -- When `revokeOthers` is set, drop all other sessions AND outstanding
1355+ -- challenges for this pubkey, so a captured challenge cannot be
1356+ -- redeemed for a new session after revocation (Q35).
1357+ *challenges = if revokeOthers
1358+ then filter (\x -> not (x.pubkey == pubkey)) ch
1359+ else filter (\x -> not same x) ch
1360+ ses <- *sessions
1361+ let pruned = if revokeOthers
1362+ then filter (\s -> s.pubkey != pubkey) ses
1363+ else capPerKey ses pubkey maxSessionsPerKey
1364+ let newSession = {token, pubkey, expiresAt: expiry, ip: clientIp}
1365+ -- LRU-evicts the soonest-to-expire session when the pool is full; this global
1366+ -- eviction is Sybil-floodable, see the LIMITATION note on `maxSessions`.
1367+ let pooled = union pruned [newSession]
1368+ -- Count what `capList` is about to shed, so the handler can warn about it
1369+ -- below. That flood has no other observable signature: evicted users just
1370+ -- start seeing 401s and silently re-authenticate, which looks like normal
1371+ -- traffic in the access log. A sustained nonzero rate here is the alert.
1372+ let evicted = max 0 (count pooled - maxSessions)
1373+ *sessions = capList pooled maxSessions
1374+ peers <- refreshLocalPresence pubkey expiry
1375+ yield (Just {value: {peers, evicted}}))
1376+ case result of
1377+ Nothing {} -> yield (Err {error: {status: 401, message: "invalid"}})
1378+ Just {value: r} -> do
1379+ -- Warn outside the `atomic` block, never inside: an STM transaction can
1380+ -- retry, and a console write is not rolled back with it — logging inside
1381+ -- would emit one line per retry attempt rather than one per eviction.
1382+ -- Include the requesting pubkey and IP for audit (Q38): an operator
1383+ -- investigating a Sybil flood needs to know which identities are responsible.
1384+ when (r.evicted > 0) (logWarn ("session pool full: evicted " ++ show r.evicted ++ " session(s) to seat a new login (pubkey=" ++ pubkey ++ ", ip=" ++ clientIp ++ ", maxSessions=" ++ show maxSessions ++ ")"))
1385+ when federationEnabled (fork (sendBatchedGossip r.peers [{eventType: "online", pubkey: Just {value: pubkey}}]))
1386+ yield (Ok {value: {token, expiresAt: expiry}})
11301387
11311388-- ============================================
11321389-- Handler: poll
@@ -1141,7 +1398,7 @@ handleVerifyAuth = \pubkey challenge signature revokeOthers clientIp -> do
11411398-- don't time us out mid-session, then runs `doPoll` to collect events (or
11421399-- block until a matching message arrives or the timeout elapses) and
11431400-- assembles the response.
1144−handlePoll : Int -> Text -> Text -> IO {r *seqCounter, r *sessions, rw *forwardFailures, rw *forwards, rw *messages, rw *presence, network, clock} (Result HttpError {cursor: Timestamp, events: [PollEvent]})
1401+handlePoll : Timestamp -> Text -> Text -> IO {r *seqCounter, r *sessions, rw *forwardFailures, rw *forwards, rw *messages, rw *presence, network, clock} (Result HttpError {cursor: Timestamp, events: [PollEvent]})
11451402handlePoll = \cursor authorization clientIp -> do
11461403 t <- now
11471404 setup <- atomic (do
@@ -1161,13 +1418,20 @@ handlePoll = \cursor authorization clientIp -> do
11611418 let clampedCursor = max 0 (min (max t curSeq) cursor)
11621419 when (clampedCursor > 0) (ackPolledMessages pubkey clampedCursor)
11631420 pres <- *presence
1421+ -- Refresh local presence when less than half the session TTL remains,
1422+ -- so peers don't time us out mid-session.
11641423 let stale = not any (\p -> p.pubkey == pubkey && isLocalServer p.server && p.expiresAt - t >= sessionExpiry / 2) pres
11651424 refreshPeers <- if stale then refreshLocalPresence pubkey (t + sessionExpiry) else yield []
1166− yield (Just {value: {pubkey, clampedCursor, refreshPeers}}))
1425+ -- S3: Track whether we actually refreshed so the gossip line below
1426+ -- only fires on a refresh, not on every poll. Without this, every
1427+ -- poll gossips to all seed peers via gossipTargets [], creating
1428+ -- O(clients × seeds) federation traffic per poll cycle.
1429+ yield (Just {value: {pubkey, clampedCursor, refreshPeers, didRefresh: stale}}))
11671430 case setup of
11681431 Nothing {} -> yield (Err {error: {status: 401, message: "unauthorized"}})
11691432 Just {value: s} -> do
1170− when federationEnabled (fork (sendBatchedGossip s.refreshPeers [{eventType: "online", pubkey: Just {value: s.pubkey}}]))
1433+ -- S3: Only gossip when we actually refreshed presence — not on every poll.
1434+ when (federationEnabled && s.didRefresh) (fork (sendBatchedGossip s.refreshPeers [{eventType: "online", pubkey: Just {value: s.pubkey}}]))
11711435 pollResult <- doPoll s t
11721436 yield (Ok {value: pollResult})
11731437
@@ -1180,12 +1444,20 @@ handlePoll = \cursor authorization clientIp -> do
11801444-- the wait transaction reads `*messages` and `retry`s until a row matching
11811445-- this pubkey/cursor is committed; the timer wins on idle. Either way we
11821446-- re-collect at the new wall time, so a timeout returns an empty page.
1183−doPoll : {clampedCursor: Timestamp, pubkey: PubkeyHex | a} -> Timestamp -> IO {r *messages, clock} {cursor: Timestamp, events: [{encryptedBlob: BlobHex}]}
1447+
1448+-- Messages addressed to `pk`, unexpired at `tnow`, and newer than `cursor`. Shared
1449+-- by `doPoll`'s collect and STM-wait arms so the two predicates cannot drift: a
1450+-- wait that accepted a row the collect then filtered out (say, an expired row still
1451+-- above the cursor) would wake the poll, return an empty page with an unchanged
1452+-- cursor, and spin the client through an immediate re-poll into the same wakeup.
1453+freshFor : PubkeyHex -> Timestamp -> Timestamp -> [Message] -> [Message]
1454+freshFor = \pk cursor tnow msgs -> filter (\m -> m.toKey == pk && tnow - m.receivedAt < messageMaxAge && m.receivedAt > cursor) msgs
1455+
1456+doPoll : {clampedCursor: Timestamp, pubkey: PubkeyHex | a} -> Timestamp -> IO {r *messages, clock} {cursor: Timestamp, events: [PollEvent]}
11841457doPoll = \s t -> do
11851458 let collectAt = \tnow -> atomic (do
11861459 msgs <- *messages
1187− let fresh = filter (\m -> m.toKey == s.pubkey && tnow - m.receivedAt < messageMaxAge && m.receivedAt > s.clampedCursor) msgs
1188− let limited = take maxPollEvents (sortBy (\m -> m.receivedAt) fresh)
1460+ let limited = take maxPollEvents (sortBy (\m -> m.receivedAt) (freshFor s.pubkey s.clampedCursor tnow msgs))
11891461 yield {
11901462 events: map (\m -> {m.encryptedBlob}) limited,
11911463 cursor: fold (\acc m -> max acc m.receivedAt) s.clampedCursor limited
@@ -1197,19 +1469,12 @@ doPoll = \s t -> do
11971469 -- `race` requires both arms to share a single effect row, so each arm
11981470 -- carries the union {r *messages, clock} — the STM wait gets a `now`,
11991471 -- the timer gets a no-op `*messages` read.
1200− -- The wait predicate must match `collectAt`'s exactly, age guard included:
1201− -- an expired row that still sits above the cursor (not yet swept by
1202− -- `pruneExpired`) would otherwise satisfy the wait, wake the poll, then be
1203− -- filtered out by `collectAt` — returning an empty page whose cursor is
1204− -- unchanged, so the client immediately re-polls into the same wakeup. That
1205− -- is a tight spin for as long as the row survives.
12061472 race
12071473 (do
12081474 tw <- now
12091475 atomic (do
12101476 msgs <- *messages
1211− let fresh = filter (\m -> m.toKey == s.pubkey && tw - m.receivedAt < messageMaxAge && m.receivedAt > s.clampedCursor) msgs
1212− if count fresh > 0 then yield {} else retry))
1477+ if count (freshFor s.pubkey s.clampedCursor tw msgs) > 0 then yield {} else retry))
12131478 (do
12141479 atomic (do _ <- *messages; yield {})
12151480 sleep pollTimeoutMs)
@@ -1220,19 +1485,19 @@ doPoll = \s t -> do
12201485-- receivedAt <= cursor, plus their pending forwards.
12211486--
12221487-- The ack is destructive and keyed on `pubkey` alone — no session identity enters
1223−-- into it. Two concurrent sessions for the same keypair therefore share one
1224−-- mailbox and race: whichever polls first acks the rows out from under the other,
1225−-- which never sees them. That is an accepted limitation, not a bug to fix here —
1226−-- one keypair per device is the model. See `maxSessionsPerKey`.
1227−ackPolledMessages : PubkeyHex -> Int -> IO {rw *forwards, rw *messages} {}
1228−ackPolledMessages = \pubkey cursor -> do
1488+-- into it, so two sessions sharing one keypair race over one mailbox. Accepted
1489+-- limitation; see `maxSessionsPerKey`.
1490+-- Self-atomic: touches two refs (*messages and *forwards), so wraps its own
1491+-- transaction rather than relying on the caller's.
1492+ackPolledMessages : PubkeyHex -> Timestamp -> IO {rw *forwards, rw *messages} {}
1493+ackPolledMessages = \pubkey cursor -> atomic (do
12291494 msgs <- *messages
12301495 let matches = \m -> m.toKey == pubkey && m.receivedAt <= cursor
12311496 let toAck = filter matches msgs
12321497 let blobs = map (\m -> m.encryptedBlob) toAck
12331498 *messages = filter (\m -> not matches m) msgs
12341499 fwds <- *forwards
1235− *forwards = filter (\f -> not (f.toKey == pubkey && elem f.encryptedBlob blobs)) fwds
1500+ *forwards = filter (\f -> not (f.toKey == pubkey && elem f.encryptedBlob blobs)) fwds)
12361501
12371502-- ============================================
12381503-- Handler: send
@@ -1244,6 +1509,23 @@ ackPolledMessages = \pubkey cursor -> do
12441509-- Duplicates are silently treated as success so retries are idempotent.
12451510-- Per-client-IP send rate is enforced by the route's `rateLimit` clause.
12461511-- Federated forwards are kicked off in background forks after the atomic.
1512+-- The sender's UI treats every success the same and learns "they got it" only via
1513+-- the recipient's E2E ack.
1514+
1515+-- Batch validation: checks batch size, per-message field validity, and self-send.
1516+-- Refined-type validation at the route boundary only fires for top-level scalar
1517+-- body fields; `to`/`encryptedBlob` are nested inside the `messages` list, so the
1518+-- runtime does not check them. `isValidBlobHex` is the same predicate `BlobHex`
1519+-- refines on, so this check and the route boundary cannot drift apart.
1520+validateBatch : [{to: PubkeyHex, encryptedBlob: BlobHex | a}] -> PubkeyHex -> Maybe HttpError
1521+validateBatch = \messages senderKey ->
1522+ if count messages > maxBatchSize
1523+ then Just {value: {status: 413, message: "batch_too_large"}}
1524+ else if any (\m -> not (isValidExactHex 64 m.to && isValidBlobHex m.encryptedBlob)) messages
1525+ then Just {value: {status: 400, message: "invalid_message"}}
1526+ else if any (\m -> m.to == senderKey) messages
1527+ then Just {value: {status: 400, message: "self_send"}}
1528+ else Nothing {}
12471529
12481530-- POST /messages: send a list of ciphertexts atomically. Self-send is
12491531-- rejected up-front; the remaining batch is committed inside one atomic
@@ -1255,52 +1537,44 @@ handleSendMessages = \messages authorization clientIp -> do
12551537 auth <- authedPubkey authorization t clientIp
12561538 case auth of
12571539 Nothing {} -> yield (Err {error: {status: 401, message: "unauthorized"}})
1258− Just {value: senderKey} -> do
1259− if count messages > maxBatchSize
1260− then yield (Err {error: {status: 413, message: "batch_too_large"}})
1261− -- Refined-type validation at the route boundary only fires for top-level
1262− -- scalar body fields; `to`/`encryptedBlob` are nested inside the `messages`
1263− -- list, so the runtime does not check them. Enforce the `PubkeyHex` /
1264− -- `BlobHex` contracts here so a malformed key, or a non-hex / under-
1265− -- `minBlobLen` / over-`maxBlobLen` blob, is rejected instead of stored.
1266− -- `isValidBlobHex` is the same predicate `BlobHex` refines on, so this
1267− -- check and the route boundary cannot drift apart.
1268− else if any (\m -> not (isValidExactHex 64 m.to && isValidBlobHex m.encryptedBlob)) messages
1269− then yield (Err {error: {status: 400, message: "invalid_message"}})
1270− else if any (\m -> m.to == senderKey) messages
1271− then yield (Err {error: {status: 400, message: "self_send"}})
1272− else do
1540+ Just {value: senderKey} -> case validateBatch messages senderKey of
1541+ Just {value: err} -> yield (Err {error: err})
1542+ Nothing {} -> do
12731543 committed <- atomic (do
12741544 pres <- *presence
1545+ -- S2: cap the immediate fan-out at `maxForwardsPerServer` servers per
1546+ -- recipient. The post-commit `forkForwardsTo` fires against this list
1547+ -- directly (bypassing the `*forwards` queue and its per-peer cap), so
1548+ -- without a bound here a recipient gossiped as present on thousands of
1549+ -- servers would spawn one immediate HTTP forward per server per message.
12751550 let staged = map (\m -> {
12761551 m.to,
12771552 m.encryptedBlob,
1278− remoteServers: collectPeers (filter (\p -> p.pubkey == m.to && p.expiresAt > t) pres) (\p -> p.server)
1553+ remoteServers: take maxRemoteServersPerMessage (collectPeers (filter (\p -> p.pubkey == m.to && p.expiresAt > t) pres) (\p -> p.server))
12791554 }) messages
12801555 forEach staged (\c -> do
1281− -- Dedupe like the federation ingress path (`handleForwardMessage`):
1282− -- a client retry after a lost response carries the identical
1283− -- ciphertext, and `appendMessage`'s fresh `seqTs` would otherwise
1284− -- make `union` keep both rows and double-deliver. Re-reading
1285− -- `*messages` each iteration also collapses duplicate blobs that
1286− -- appear twice within one batch.
1556+ -- Read `*messages` *before* the append: `delivered` below must see the
1557+ -- pre-existing row, and re-reading each iteration is also what lets
1558+ -- `appendMessage`'s own dedupe collapse a blob repeated within one batch.
12871559 existingMsgs <- *messages
1288− when (not any (\m -> m.toKey == c.to && m.encryptedBlob == c.encryptedBlob) existingMsgs) (appendMessage c.to c.encryptedBlob t)
1560+ appendMessage c.to c.encryptedBlob t
12891561 -- Peers that already hold this blob — from an earlier send of the
12901562 -- identical ciphertext that was forwarded then pruned from
12911563 -- `*forwards`. A brand-new message has empty `deliveredTo`, so this
12921564 -- is `[]` on the normal path; on a client resend it carries the real
12931565 -- set. Mirrors `forwardQueuedToServer`'s guard so we don't re-stage a
12941566 -- forward to a peer that already accepted this blob.
1295− let delivered = fold (\acc m -> if m.toKey == c.to && m.encryptedBlob == c.encryptedBlob then union acc (map (\d -> d.server) m.deliveredTo) else acc) [] existingMsgs
1567+ let delivered = case findFirst existingMsgs (\m -> m.toKey == c.to && m.encryptedBlob == c.encryptedBlob) of
1568+ Just {value: m} -> map (\d -> d.server) m.deliveredTo
1569+ Nothing {} -> ([] : [Text])
12961570 -- Stage outbox rows for peers under their `maxForwardsPerServer`
12971571 -- ceiling. Peers at the cap still get the immediate post-commit
12981572 -- delivery attempt (`forkForwardsTo`) — only the retry-queue row
12991573 -- is skipped.
13001574 when federationEnabled (do
13011575 fwds <- *forwards
1302− let newFwds = map (\s -> {toServer: s, toKey: c.to, c.encryptedBlob, retries: 0}) (filter (\s -> not (any (forwardMatches c.encryptedBlob s) fwds) && not elem s delivered && countWhere (\f -> f.toServer == s) fwds < maxForwardsPerServer) c.remoteServers)
1303− *forwards = union fwds newFwds))
1576+ let newFwds = map (\s -> {toServer: s, toKey: c.to, c.encryptedBlob, retries: 0}) (filter (\s -> not (any (forwardMatches c.to c.encryptedBlob s) fwds) && not elem s delivered && countWhere (\f -> f.toServer == s) fwds < maxForwardsPerServer) c.remoteServers)
1577+ *forwards = capForwards (union fwds newFwds)))
13041578 yield staged)
13051579 when federationEnabled (forEach committed (\c -> fork (forkForwardsTo c.to c.encryptedBlob c.remoteServers)))
13061580 yield (Ok {value: {}})
@@ -1315,22 +1589,23 @@ handleSendMessages = \messages authorization clientIp -> do
13151589-- the message), and `deliveredTo` prevents re-forwards to peers that already
13161590-- have the message. On failure the forwards row stays so
13171591-- `retryPendingForwards` can re-attempt with backoff.
1592+--
1593+-- A 404 is not a peer failure — see `retryForwardsTo` for why `no_presence` must
1594+-- not reach `recordFailure`. Here the row is left queued for the retry sweep and
1595+-- the peer's backoff (shared with gossip) is not touched.
13181596forkForwardsTo : PubkeyHex -> BlobHex -> [Text] -> IO {rw *forwardFailures, rw *forwards, rw *messages, network, clock} {}
13191597forkForwardsTo = \to encryptedBlob servers -> forEach servers (\server -> when (not isBadServerName server) (do
13201598 t <- now
13211599 result <- fetch (federationUrl server) (ForwardMessage {toKey: to, encryptedBlob})
1322− let same = forwardMatches encryptedBlob server
1600+ let same = forwardMatches to encryptedBlob server
13231601 case result of
1324− Err _ -> recordFailure server t
1602+ Err {error: e} -> when (e.status != 404) (recordFailure server t)
13251603 Ok _ -> do
13261604 clearFailure server t
13271605 atomic (do
13281606 fwds <- *forwards
13291607 *forwards = filter (\x -> not same x) fwds
1330− msgs <- *messages
1331− *messages = map (\m -> if m.toKey == to && m.encryptedBlob == encryptedBlob && not any (\d -> d.server == server) m.deliveredTo
1332− then {m.toKey, m.encryptedBlob, m.receivedAt, deliveredTo: union m.deliveredTo [{server}]}
1333− else m) msgs)))
1608+ markDelivered to encryptedBlob server)))
13341609
13351610-- ============================================
13361611-- Handler: federation receive
@@ -1340,49 +1615,58 @@ forkForwardsTo = \to encryptedBlob servers -> forEach servers (\server -> when (
13401615-- currently-online local keys. Both handlers refuse with 403 when
13411616-- `federationEnabled` is off, matching the outbound paths — a single-node
13421617-- deployment accepts no peer writes to `*presence`/`*messages`.
1618+--
1619+-- SECURITY — THE OPEN-FEDERATION THREAT MODEL (accepted v0.1 limitations; the
1620+-- canonical statement, referenced by the handlers below and by
1621+-- `forwardQueuedToServer`). Neither endpoint authenticates its caller and nothing
1622+-- ties an event to the key it speaks for, so any host that can reach us may:
1623+--
1624+-- * announce an arbitrary victim pubkey as `online` at itself. We write that
1625+-- presence row, and the next `forwardQueuedToServer` hands the victim's queued
1626+-- ciphertext to the attacker's host — a *gossip redirect*.
1627+-- * append an arbitrary blob to any currently-online local key's mailbox, which
1628+-- the recipient then polls down — *unauthenticated mailbox injection*.
1629+--
1630+-- Neither breaks confidentiality or allows forgery. Payloads are sealed to the
1631+-- recipient's key and the sender's identity and signature live *inside* the AEAD
1632+-- (PROTOCOL.md §5), so a redirected blob cannot be read and an injected blob that
1633+-- does not open — or opens without a valid inner signature — is dropped by the
1634+-- client and can never impersonate a contact. What the attacker gets is metadata a
1635+-- relay is otherwise never supposed to concentrate (which keys receive traffic, how
1636+-- much, when), unsolicited storage and bandwidth, and — because our copy is pruned
1637+-- once marked `deliveredTo` — the ability to *withhold* delivery by steering a
1638+-- ciphertext at a host that will never serve it. Confidentiality-preserving;
1639+-- availability- and metadata-affecting.
1640+--
1641+-- Bounded, not prevented, by: the SSRF deny-list (`isBadServerName`), the
1642+-- `no_presence` gate, per-IP rate limits, the presence caps (`maxPresence` /
1643+-- `maxPresencePerServer`), the gossip TTL (`onlineGossipTtl`) capping how long one
1644+-- forged row survives, `maxBlobLen`, the `appendMessage` dedupe, and
1645+-- `messageMaxAge` pruning.
1646+--
1647+-- The fix for both is peer authentication: require a gossip event to carry a
1648+-- signature from the pubkey it announces, and/or authenticate the peer relay itself
1649+-- so an unknown host cannot write to `*presence` / `*messages` at all. Deferred past
1650+-- v0.1 because it needs a key-to-home-server binding the protocol does not yet
1651+-- define. PROTOCOL.md §10 enumerates what open federation does and does not protect.
13431652
13441653-- POST /federation/gossip: ingest peer presence events. The transport-level
13451654-- `fromServer` is the home server for every event. Drops every (pubkey,
13461655-- fromServer) row touched by this batch, then re-adds fresh-TTL rows for
13471656-- pubkeys with an `online` event (so Online wins on collision). For keys
13481657-- that transition offline → online, flushes any locally-buffered messages via
1349−-- `forwardQueuedToServer`. Events with an unrecognized `eventType` or no
1658+-- `forwardQueuedToAll`. Events with an unrecognized `eventType` or no
13501659-- `pubkey` are skipped (forward-compat) rather than rejecting the batch.
13511660--
1352−-- SECURITY (accepted v0.1 limitation — gossip redirect / ciphertext theft):
1353−-- this endpoint is unauthenticated, and nothing ties a gossip event to the key
1354−-- it claims to speak for. Any host that can reach us may announce an arbitrary
1355−-- victim pubkey as `online` at itself; we write that presence row, and the very
1356−-- next `forwardQueuedToServer` hands the victim's queued ciphertext to the
1357−-- attacker's host. The attacker cannot *read* those messages — the payload is
1358−-- sealed to the victim's key, and the sender's identity and signature live
1359−-- inside the AEAD (PROTOCOL.md §5) — but it does harvest metadata a relay is
1360−-- otherwise never supposed to concentrate: which keys are receiving traffic,
1361−-- how much, and when. Worse, because our copy is pruned once it is marked
1362−-- `deliveredTo` the attacker's host, a forged announcement can also *withhold*
1363−-- delivery: the ciphertext goes to a host that will never serve it to the
1364−-- victim's client. So this is a confidentiality-preserving but availability-
1365−-- and metadata-affecting attack.
1366−--
1367−-- Bounded, not prevented, by: the SSRF deny-list (`isBadServerName`), the
1368−-- `no_presence` gate on the inbound side, per-IP rate limits, and the gossip
1369−-- TTL (`onlineGossipTtl`) capping how long one forged row survives.
1370−--
1371−-- The fix is peer authentication: require a gossip event to carry a signature
1372−-- from the pubkey it announces (proving the key really did authenticate at
1373−-- `fromServer`), and/or authenticate the peer relay itself so an unknown host
1374−-- cannot inject presence at all. Deferred past v0.1 because it needs a
1375−-- key-to-home-server binding the protocol does not yet define.
1376−-- PROTOCOL.md §10 enumerates what open federation does and does not protect.
1661+-- SECURITY: this is the gossip-redirect ingress described in the section header
1662+-- above — a forged `online` row written here is what steals a victim's routing.
1663+-- The presence caps applied below are the only thing bounding how much of
1664+-- `*presence` an unauthenticated peer can own.
13771665handleRecvGossip : [GossipEvent] -> ServerName -> IO {r *messages, rw *forwards, rw *presence, clock} (Result HttpError {})
13781666handleRecvGossip = \events fromServer -> do
13791667 t <- now
1380− -- `fromServer` arrives refined from the route boundary — that is exactly where
1381− -- the `ServerName` predicate is worth enforcing, since the name is peer-supplied.
1382− -- Internally, though, every server name in state is plain `Text` (see
1383− -- `collectPeers`), so widen once here: a `PresenceEntry.server` field cannot be
1384− -- built from, or compared against, the refined type. `forwardQueuedToServer`
1385− -- below still takes the refined `fromServer` — it wants the checked name.
1668+ -- Widen the peer-supplied `ServerName` once (see `type ServerName`);
1669+ -- `forwardQueuedToAll` below still takes the refined name.
13861670 let from = (fromServer : Text)
13871671 if not federationEnabled
13881672 then yield (Err {error: {status: 403, message: "federation_disabled"}})
@@ -1405,16 +1689,46 @@ handleRecvGossip = \events fromServer -> do
14051689 Ok {value: pk} -> if e.eventType == "online"
14061690 then {
14071691 touched: union acc.touched [pk],
1408− added: union acc.added [{pubkey: pk, server: from, expiresAt: t + onlineGossipTtl}]
1692+ added: union acc.added [{pubkey: pk, server: from, expiresAt: t + onlineGossipTtl}],
1693+ offline: acc.offline
14091694 }
14101695 else if e.eventType == "offline"
1411− then {acc.added, touched: union acc.touched [pk]}
1696+ then {acc.added, touched: union acc.touched [pk], offline: union acc.offline [pk]}
14121697 else acc
1413− Nothing {} -> acc) {touched: ([] : [PubkeyHex]), added: ([] : [PresenceEntry])} events
1698+ Nothing {} -> acc) {touched: ([] : [PubkeyHex]), added: ([] : [PresenceEntry]), offline: ([] : [PubkeyHex])} events
14141699 let kept = filter (\p -> p.server != from || not elem p.pubkey collected.touched) pres
1415− *presence = union kept collected.added
1700+ let merged = union kept collected.added
1701+ -- Cap the gossip-learned rows: per-peer first, so one peer cannot crowd every
1702+ -- other peer's routing information out of the pool, then globally. Local rows
1703+ -- are held out of both caps and re-unioned afterwards — folding them into the
1704+ -- same LRU would let a gossip flood evict our own online users, because their
1705+ -- `sessionExpiry` (60 min) is *sooner* than a gossiped row's `onlineGossipTtl`
1706+ -- (90 min) and `capList` drops soonest-to-expire first. See `maxPresence`.
1707+ let localRows = filter (\p -> isLocalServer p.server) merged
1708+ let remoteRows = filter (\p -> not isLocalServer p.server) merged
1709+ *presence = union localRows (capList (capPerServer remoteRows from maxPresencePerServer) maxPresence)
1710+ -- S8: Make online+offline for the same key mutually exclusive within one
1711+ -- batch. If a batch carries both events for a key, online wins — the presence
1712+ -- merge above already added the online row — so that key must NOT also travel
1713+ -- the offline path and cancel its own freshly-staged forwards.
1714+ let onlineKeys = map (\p -> p.pubkey) collected.added
1715+ let offlineOnly = filter (\pk -> not elem pk onlineKeys) collected.offline
1716+ -- N14: Cancel pending forwards to `from` for offline keys. Without this,
1717+ -- forwards to a peer that just went offline retry for up to 80 minutes,
1718+ -- wasting maxForwardsPerServer slots and generating failed HTTP requests.
1719+ -- The message stays in *messages, so it's re-forwarded if the key
1720+ -- re-appears on another peer.
1721+ when (count offlineOnly > 0) (do
1722+ fwds <- *forwards
1723+ *forwards = filter (\f -> not (f.toServer == from && elem f.toKey offlineOnly)) fwds)
14161724 yield (filter (\pk -> not any (\p -> p.pubkey == pk && p.server == from && p.expiresAt > t) pres) (map (\p -> p.pubkey) collected.added)))
1417− fork (forEach newlyOnline (\pk -> forwardQueuedToServer pk fromServer))
1725+ -- S4: forward queued mail for ALL newly-online keys in one mailbox pass. The
1726+ -- old per-key cap (maxNewlyOnlineForwards, N13) bounded amplification but
1727+ -- silently deferred delivery past the 10th key, and a re-announce within the
1728+ -- TTL never recovered it (the deliveredTo/presence state made the key look
1729+ -- already-handled). `forwardQueuedToAll` bounds the cost to O(|messages|)
1730+ -- regardless of how many keys came online.
1731+ fork (forwardQueuedToAll newlyOnline fromServer)
14181732 yield (Ok {value: {}})
14191733
14201734-- POST /federation/forward: receive a single federated message destined for
@@ -1424,29 +1738,13 @@ handleRecvGossip = \events fromServer -> do
14241738-- actively-polling client and get stuck. If B refuses, A retries via
14251739-- `retryPendingForwards` against the next presence target.
14261740-- Re-delivery of an already-stored (toKey, blob) pair is treated as success
1427−-- without a second append, so a sender whose success response was lost can
1428−-- retry without duplicating the message in the recipient's mailbox.
1429−--
1430−-- SECURITY (accepted v0.1 limitation — unauthenticated mailbox injection):
1431−-- this endpoint authenticates nobody. Any host that can reach us may append an
1432−-- arbitrary blob to any currently-online local key's mailbox, and the recipient
1433−-- will poll it down like any other message. This is a spam/flood surface, not a
1434−-- forgery one: the sender's identity and signature live *inside* the AEAD
1435−-- (PROTOCOL.md §5), so an injected blob that the recipient's key cannot open —
1436−-- or that opens but carries no valid inner signature — is dropped by the client
1437−-- and can never impersonate a contact. What an attacker gets is unsolicited
1438−-- rows in the recipient's mailbox and in `*messages` (storage + bandwidth), not
1439−-- a message the recipient will attribute to someone else.
1440−--
1441−-- Bounded, not prevented, by: the `no_presence` gate (only currently-online
1442−-- local keys are injectable, so an attacker must first observe or force
1443−-- presence), per-IP rate limits on the route, `maxBlobLen`, the dedupe below
1444−-- (the same blob cannot be appended twice), and `messageMaxAge` pruning.
1741+-- without a second append (`appendMessage` is idempotent), so a sender whose
1742+-- success response was lost can retry without duplicating the message.
14451743--
1446−-- The fix is the same one the gossip-redirect note calls for: authenticate the
1447−-- peer relay, so an unknown host cannot write to `*messages` at all. Deferred
1448−-- past v0.1. PROTOCOL.md §10 enumerates what open federation does and does not
1449−-- protect.
1744+-- SECURITY: this is the unauthenticated-mailbox-injection ingress described in the
1745+-- section header above — an unsolicited row lands here. The `no_presence` gate is
1746+-- what keeps the surface to keys that are already online, so an attacker must first
1747+-- observe or force presence.
14501748handleForwardMessage : PubkeyHex -> BlobHex -> IO {rw *messages, r *presence, rw *seqCounter, clock} (Result HttpError {})
14511749handleForwardMessage = \toKey encryptedBlob -> do
14521750 t <- now
@@ -1457,8 +1755,7 @@ handleForwardMessage = \toKey encryptedBlob -> do
14571755 if not hasLocalPresence pres toKey t
14581756 then yield (Err {error: {status: 404, message: "no_presence"}})
14591757 else do
1460− msgs <- *messages
1461− when (not any (\m -> m.toKey == toKey && m.encryptedBlob == encryptedBlob) msgs) (appendMessage toKey encryptedBlob t)
1758+ appendMessage toKey encryptedBlob t
14621759 yield (Ok {value: {}}))
14631760
14641761-- ============================================
@@ -1489,7 +1786,7 @@ api = serve Api where
14891786-- Endless tick: prune expired state and gossip offline for locally-expired
14901787-- keys. First sweep happens immediately so stale rows persisted by the
14911788-- previous process clear before the next interval elapses.
1492−backgroundPrune : IO {rw *challenges, rw *forwardFailures, rw *messages, rw *presence, rw *sessions, network, clock} a
1789+backgroundPrune : IO {rw *challenges, rw *forwardFailures, rw *forwards, rw *messages, rw *presence, rw *sessions, network, clock} a
14931790backgroundPrune = do
14941791 t <- now
14951792 -- Snapshot the peer set *before* the sweep. `pruneExpired` drops every expired
@@ -1538,17 +1835,12 @@ main = do
15381835 case localServerName of
15391836 Nothing {} -> logWarn ("serverHost '" ++ serverHost ++ "' is not a valid ServerName (must be lowercase, no trailing dot, at most " ++ show maxServerNameLen ++ " chars); federation egress disabled")
15401837 _ -> yield {}
1541− -- serverHost is still the compiled-in default. The auth signature is bound to
1542− -- the hostname the client dialed (`skrepka-auth-v1:<host>:<challenge>`,
1543− -- PROTOCOL.md §6), and /auth/verify checks it against `beforeColon serverHost`
1544− -- — so any client that reaches this relay under a name other than "localhost"
1545− -- fails verification with 401, and no session is ever issued. That is exactly
1546− -- the install.sh deployment (Caddy fronts a public DOMAIN, clients dial it),
1547− -- which passes `--serverHost=<domain>` — but the current Knot runtime accepts
1548− -- and then IGNORES `--<name>=<value>` constant overrides at startup, so the
1549− -- flag is inert and serverHost stays "localhost". A public relay must bake the
1550− -- real name at build time (`knot build server.knot --serverHost=<host>`).
1551− -- Warn loudly rather than let every login fail silently.
1838+ -- /auth/verify checks the client's host-bound signature against
1839+ -- `authHost serverHost`, so a relay still on the compiled-in default 401s every
1840+ -- login the moment a client dials it under any other name — which is exactly the
1841+ -- install.sh deployment (Caddy fronts a public DOMAIN). `--serverHost=<domain>` is
1842+ -- accepted and then IGNORED by the current Knot runtime, so it must be baked in at
1843+ -- build time instead. Warn loudly rather than let every login fail silently.
15521844 when (serverHost == "localhost") (logWarn "serverHost is the default 'localhost': every client that dials this relay under any other hostname will fail /auth/verify (the auth signature is host-bound, PROTOCOL.md §6), so no session is ever issued. A public relay must set serverHost to its real hostname; note the Knot runtime currently ignores --serverHost at startup, so bake it at build time: knot build server.knot --serverHost=<host>")
15531845 when (federationEnabled && count seedPeerList > 0) (logInfo (" seed peers: " ++ show seedPeerList))
15541846 fork backgroundPrune
server.onew file

Binary file not shown.