minstrel

The session cookie is a bearer credential, and it sat in plain text in the
Room auth_session row. It now lives in a SessionVault: AES-256-GCM under a
key held in the Android Keystore, with only the ciphertext in a private
prefs file. A copy of the app's files no longer yields a usable session.
Platform APIs only, no new dependency (androidx.security-crypto is
deprecated).

Nobody is signed out by the upgrade. On first launch AuthStore moves a
cookie still in the row into the vault and clears the column. If the
Keystore can't be used on a device, the cookie stays in the row as before
rather than being lost. A sign-in or 401 that lands during the move wins
over the value it read, and the move never throws. The auth gate now
waits for this before choosing Login or Home, with a 10s deadline so a
wedged Keystore can't leave the start screen spinning.

Tests: AuthStoreSessionVaultTest (upgrade move, vault-only load, Keystore
fallback, sign-in/out, hydration race) and SealedBoxTest (round trip,
fresh IV, tamper and wrong-key rejection). The real Keystore path needs
a device; the first launch after updating is that check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-06 10:29:32 -04:00

.idea

refactor(android): unify offline detection into NetworkStatusController

2026-06-05 12:06:22 -04:00

app

feat(android): keep the session cookie in Keystore-encrypted storage (M462 #4985 )

2026-10-06 10:29:32 -04:00

config

chore(android): extend detekt TooManyFunctions exception to @Database

2026-05-22 16:45:47 -04:00

gradle

fix(android): bundle the typefaces instead of fetching them at runtime