Some checks failed
Android CI / build (push) Has been cancelled
Owner 2026-11-19: Russia cuts the whole zone zapret.moe by SNI, and zapret-links hands out mirrors under other pool domains (fuckingspeedtest.com, osjcpjzipyb.click). ForgejoHosts only took one label under zapret.moe, so every name of the entry pages was dropped and the updater fell back to GitHub or nothing. Now a name is one label under a domain from the entry page's own `domains` (or TRUSTED_DOMAINS), prefixed git*/wiki* names under zapret.moe keep the family rule, and the seed starts with four pool mirrors of the release day (verified: API, assets on the same name, ranges). With the VPN up, the app's own requests to all these domains (updater, report ingest names) go through it, like zapret.moe before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
32 lines
2.8 KiB
Markdown
32 lines
2.8 KiB
Markdown
# app-updater
|
|
|
|
An isolated module for APK updates. It does not depend on the UI, profiles, libbox or the VPN
|
|
implementation in `app`.
|
|
|
|
- `ForgejoUpdateSource.kt` — an HTTPS client for a single route (Range, a neutral User-Agent, a redirect cache) and the parsing of Forgejo Releases.
|
|
- `UpdateModels.kt` — release metadata, the states (`Checking`, `Downloading` with the savings, `Ready`/`Installing`, `Failure`) and a strict JSON parser.
|
|
- `ZipDirectory.kt`, `DeltaPlan.kt` — pure parsing of ZIP/APK (EOCD, the central directory, the APK Signing Block), the plan for reusing entries and range merging; no network and no Android.
|
|
- `ApkDownloader.kt` — a delta download over HTTP Range against the installed APK, a full download that resumes `.part`, SHA-256 verification.
|
|
- `UpdateRouter.kt` — route selection (direct / through a temporary VPN) without intermediate messages; a race when the VPN is on; the remembered route in `updater_prefs` (`UpdatePrefs.kt`).
|
|
- `ApkUpdateVerifier.kt` — the package/version/minSdk/signing policy.
|
|
- `UpdateController.kt` — the check, the automatic download (Stable), the mobile network policy (`UpdateAutoDownloadPolicy`), the hand-over to the installer, the cache cleanup; the state for the banner and the settings page.
|
|
- `UpdateContracts.kt`, `UpdateVpnFallback.kt` — narrow callback contracts: the installer, notifications, the environment (VPN/network/screen), the VPN lease.
|
|
|
|
The contracts are implemented in `app/src/main/java/io/github/zapretkvn/android/updates/`
|
|
(`AppUpdateVpnFallback`, `PackageInstallerUpdateInstaller`, `UpdateInstallReceiver`, `UpdateCheckJob`,
|
|
`AndroidUpdateNotifier`), because only the product module owns `VpnService`, `PackageInstaller`,
|
|
notifications and `JobScheduler`.
|
|
|
|
## Site names (owner 2026-11-19)
|
|
|
|
Russia cuts the whole zone `zapret.moe` by name (SNI), so zapret-links serves the Forgejo mirrors under
|
|
random names of other pool domains too (`fuckingspeedtest.com`, `osjcpjzipyb.click`, more later).
|
|
`ForgejoHosts` keeps a fixed seed: four pool mirrors of the release day first (zapret-links never removes a
|
|
name), then the old `git*.zapret.moe` names, which still work outside Russia and through the VPN. When
|
|
every known name is silent it reads the zapret-links entry pages (script.google.com, the GitHub gist) and
|
|
learns `families.git.hosts`, trusting one label under a domain from the page's own `domains` list (without
|
|
it, under `TRUSTED_DOMAINS`); a prefixed `git*`/`wiki*` name under zapret.moe must be of the git family.
|
|
Only learnt or seed names pass `ForgejoHttpsClient.validatedUrl`, so a redirect cannot leave the project's
|
|
names. With the VPN up, the app's own requests to all these domains go through it (the updater route rule
|
|
of `RuntimeConfigBuilder`). The same rules live in the shared update core `zapret_update/mirrors.py` on
|
|
Windows.
|