v0.9.4

Public domain names: a server that is not reachable yet

Right after connecting, the first lookup of a public domain served over fips could come back with the ordinary Internet address and keep it: the mesh session to the domain's server was not up when the lookup asked it, the server was then set aside for five minutes, and without a published zone record the app's resolver kept the legacy address for as long as the record allowed.

• A name whose server does not answer now gets the legacy answer only until the resolver's next attempt — 20 seconds after a first failure, growing to three hours for a server that stays down — so the app asks again when the server is retried, and does not ask every few seconds about a server that is down for good.
• The resolver moves to fips-pub-domains 0.2.5, which carries that change.
• rustls 0.23.45 and rustls-webpki 0.103.15.

No new settings. Installing over 0.9.3 keeps identity and settings.

Checked on a Pixel 9 Pro with a release-signed build of the resolver change (before the rustls bump and the final pin): a domain bound to a mesh node answered over fips right after connecting and again 35 seconds later. The unreachable-server case itself did not occur in that run; it is covered by tests.

Which APK

Most phones: fips-android-v0.9.4-arm64-v8a.apk. The -universal.apk carries all three ABIs for a first install when unsure; the in-app updater picks the per-ABI one.

Signing

Release certificate SHA-256: aa905e32bd0058874d252990abba26c78ddd8fca018195ebd1cd232a99a7a8e1