Skip to content

v0.10.1

Choose a tag to compare

@fr34aky fr34aky released this 14 Nov 19:04
· 8 commits to main since this release
6015a50

Fixes only: ten faults found in a review of the app's native code. None of them was on the normal path, so most users will notice no difference. No new settings or permissions.

DNS

  • DNS over TCP is answered. An app that asked the tunnel's resolver over TCP (resolvers do this when an answer is too large for UDP) got no reply. These queries are now answered like the UDP ones, .fips names included. A truncated upstream answer is fetched again over TCP.
  • Only the server that was asked can answer. A reply to an upstream DNS query was accepted from any address that reached the socket. It is now accepted only from the upstream the query went to.
  • A flood of queries no longer starts a thread each. At most 128 queries are in progress at once; further ones get SERVFAIL until some finish.

Tunnel

  • One failed write no longer stops traffic to apps. Any error writing a packet to the tunnel ended the writer, and apps received nothing until a reconnect. Now only that packet is dropped; the writer stops only when the tunnel itself is gone.
  • A failed start cleans up. If the forwarder or the packet pump could not start, the node was left running in the background and could get in the way of the next connect. It is now stopped first.
  • Tunnel changes are applied in order. A tunnel change that arrived while another was being applied was dropped. The app never sent two at once, so this did not happen in practice.

Other

  • Worker threads apply on the next connect. A changed Worker threads setting took effect only after the app process was restarted.
  • Mesh relays for public names. A local app without the relay's access token could occupy all four connection slots of a relay and keep the app's own connection out. Slots are now given only after the token is checked, and waiting connections are limited and timed out. The relay also receives its own name in the Host header instead of 127.0.0.1.
  • An internal error in six native calls returns an error instead of ending the app process.
  • rustls 0.23.46.

Installing over 0.10.0 keeps identity and settings.

Checked on an x86_64 emulator, installed over an older release: connect, a tunnel replacement after selecting a mesh app, DNS and a web page through the tunnel, disconnect. Not run on a phone, and DNS over TCP was checked by the host tests only; the other two ABIs were built and checked in CI. If something misbehaves, 0.10.0 remains on the releases page; going back needs an uninstall, so use Overview → Back up first.

Which APK

Most phones: fips-android-v0.10.1-arm64-v8a.apk. If you are unsure, -universal.apk carries all three ABIs for a first install; the in-app updater picks the per-ABI APK.

Signing

Release certificate SHA-256: aa905e32bd0058874d252990abba26c78ddd8fca018195ebd1cd232a99a7a8e1