Repository navigation
An APK name filter from an imported list can no longer slow down the checks, and imported certificate pins get a stricter rule.
Requires Android 15 or later. The APK has no native code, so it runs on all ABIs. Update from 0.1.6 in place: the signing key is the same. If an app finds no APK after the update, its name filter is now used as plain text: make the filter shorter, with 6 or fewer repeats, "?" and "|" together.
Changed
- The APK name filter check is stricter. A filter with more than 6 repeats, "?" and "|" together, or a repeated group with a "?" in it, is now used as plain text, not as a regex. Usual filters such as
(arm64-v8a|armeabi-v7a|x86_64|x86|universal|noarch)and(?i)^app-?(?:foss)?-?release\.apk$stay regexes.
Fixed
- No change.
Privacy and security
- Filters with text that the check cannot read correctly (
\Q,\c,(?#, thexflag, a[in a class, a]at the start of a class) are now plain text. Before, such a filter could hide a slow regex from the check and stop the checks of all apps. - Fonte ignores release files with a name longer than 200 characters.
- An imported list can pin a certificate only for an entry that names the package. Without a package name, Fonte pins the certificate at the first install, as for a new app.
| File | Use |
|---|---|
Fonte-0.1.7.apk |
Release build, signed. |
SHA-256:
Fonte-0.1.7.apk:2385bd25f4106dc9fab48033c9538401d48f3417b679f491f567250563632048
Signing certificate SHA-256: cc:15:4a:2b:16:d1:b2:02:1f:23:37:24:05:49:34:16:2b:f2:98:0e:16:16:72:64:0a:6e:0f:38:8c:36:ff:a4
Check the certificate with apksigner verify --print-certs Fonte-0.1.7.apk or with AppVerifier. Do not install an APK with a different certificate.