The412Banner 6e5932cb68 Stores: seal the GOG, Epic and Amazon sign-in files with an Android Keystore key (#486) ...

The stores' sign-ins (files/stores/<store>/credentials.json: access and refresh
tokens, account id and name) were plain JSON. Other apps could not read them, but
every program in the Linux session runs as the app and could. They are now sealed
with AES-256-GCM under a non-exportable AndroidKeyStore key (StrongBox when the
device has one), so the session only ever sees ciphertext.

- Format: a versioned envelope {v, alg, iv, ct}, written atomically and readable
  only by the app. No new dependencies (javax.crypto and KeyStore).
- Migration: an existing plaintext file is sealed at the next start, checked by
  decrypting it, then the plaintext is removed; users stay signed in.
- No Keystore on the device: the file stays plain and the log says so once per
  start.
- A sealed file that can never be opened (tampered, key gone or invalidated,
  broken envelope) is removed and that store asks for sign-in again. A transient
  Keystore error keeps the file and retries.

2026-10-09 14:42:23 -04:00

..

development

Stores: seal the GOG, Epic and Amazon sign-in files with an Android Keystore key (#486)

2026-10-09 14:42:23 -04:00

releases

docs: point 0.3.2 full changelog at the 0.3.2 tag (#438)

2026-10-08 10:49:29 -04:00

testing

Add game file exports and sync for Android frontends (#179)

2026-10-03 21:29:01 -04:00

agent-control.md

feat: agent bridge wayland and gamescope coverage (#406)

2026-10-08 03:50:58 +00:00

progress-log.md

Stores: seal the GOG, Epic and Amazon sign-in files with an Android Keystore key (#486)

2026-10-09 14:42:23 -04:00