v0.5.0 — Waze police source via key-protected proxy
Re-adds the WAZE detection source (removed in v0.1.5 when Waze reCAPTCHA-gated its live-map endpoint). Data comes from OpenWeb Ninja's hosted Waze feed, but the paid API key never ships in the app: a Caddy reverse proxy at api.blackflagintel.com injects the key server-side, and the app authenticates with a scoped X-App-Token entered in Settings and stored encrypted via the Android Keystore (SecureStore). No credential is baked into the APK. - scan/WazeClient.kt, scan/WazeScanner.kt: proxy client + 4-min poller, 200-alert page + client-side POLICE filter, 45-min freshness window. - data/settings/SecureStore.kt: Keystore AES/GCM at-rest store (no dependency). - Settings: encrypted wazeProxyToken + "Waze police feed" token field. - ConfidenceEngine.scoreWaze, SourceHealth/DetectionSource WAZE, service wiring. - Removes the BuildConfig/local.properties key baking entirely. versionCode 15 -> 16, versionName 0.4.0 -> 0.5.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015jgJnzMr2bdNuWcDX2xRUR
This commit is contained in:
@@ -12,8 +12,8 @@ android {
|
||||
applicationId = "org.soulstone.overwatch"
|
||||
minSdk = 26
|
||||
targetSdk = 35
|
||||
versionCode = 14
|
||||
versionName = "0.3.2"
|
||||
versionCode = 16
|
||||
versionName = "0.5.0"
|
||||
}
|
||||
|
||||
buildTypes {
|
||||
|
||||
Reference in New Issue
Block a user