5 Commits

Include renames

Author	SHA1	Message	Date
ARIA	a61b47a947	docs: replace stale 'android' name mentions with 'iris' ... The plugin is named 'iris' (IrisAdapter, IRIS_HOME_CHANNEL, label Iris), but several docs still referred to it as the android platform/plugin and to the product as 'the Android app'. Rename name-mentions to iris/IRIS and product-mentions to 'Iris app'; keep legitimate OS references (androidApp, Android SDK, Android 10, androidx, test_android.py, ...). Also includes pi-lens markdown-lint autofixes (table spacing, trailing newlines) in the touched files.	2026-08-24 21:44:02 +02:00
ARIA	597a28050f	TLS: fingerprint-confirm flow for self-signed gateway certs (issue #14) ... docs/09 §9.4 promised a SSH-host-key-style fingerprint confirm on first pair, but the app built a default OkHttpClient with no certificate handling — self-signed gateway certs were simply rejected. Build the flow: - TlsPinning.kt: PinningTrustManager wraps the platform default trust manager; a rejected cert is accepted only when its SHA-256 fingerprint matches the user-confirmed pin, anything else fails with TlsFingerprintRequired (hostname verification still applies). - SecureStore.pinnedCertFingerprint (Android EncryptedSharedPreferences + desktop settings.json), cleared on forget(). - GatewayClient: pinning socket factory on the shared client (all legs inherit it), new terminal State.TlsConfirmRequired, unwrap the nested TlsFingerprintRequired in connect loop / watchdog / SSE / poll / testHello. - ConnectScreen: confirm dialog showing the fingerprint ("Confirm & pin" re-runs the connect); IrisApp routes TlsConfirmRequired there; ChatScreen + desktop tray handle the new state. - Docs: §9.4 now describes the real flow (incl. SAN requirement), gap table item 6 → implemented, setup.md limitation note updated. - Tests: TlsPinningTest (fingerprint vs openssl, pin accept/reject, live pin read, unwrap) + TlsPinningIntegrationTest (real TLS handshake: unpinned → confirm data, pinned → 200). Live E2E verified on the phone: first pair against a self-signed IRIS_HTTP_CERT gateway shows the dialog, confirm pins, chat works, auto-reconnect after gateway restart uses the pin.	2026-08-24 21:30:42 +02:00
ARIA	746d809d48	Default push backend to ntfy; FCM opt-in with privacy warning (issue #10) ... - IRIS_PUSH_BACKEND now defaults to ntfy (keeps push metadata on your own infrastructure); FCM is opt-in via IRIS_PUSH_BACKEND=fcm - build_push_backend(): ntfy for empty/unknown names, FCM only on explicit 'fcm' - gateway setup: warn when FCM is chosen (metadata routed via Google's servers) - README: privacy note + dedicated push section; new docs/playstore-listing.md with the FCM/ntfy privacy note for the Play Store listing - docs: 00/02/03/08/12/16 + setup.md updated to ntfy-default wording - tests: default-backend assertion updated (86/86 pass)	2026-08-24 19:04:40 +02:00
ARIA	7a6d922d12	Add QR pairing (terminal QR, in-app scanner, iris://pair deep link)	2026-08-22 22:43:13 +02:00
ARIA	bf6bf7e8bd	M7: polish + E2E + docs (layout pass, theming, states, e2e driver, schema, setup.md, security)	2026-08-20 12:00:13 +02:00