R-TrustTunnel 0.6.1

R-TrustTunnel 0.6.1

Android 0.6.1-preview.1 / versionCode 60101. Signed with the release key introduced in v0.6.0 (certificate SHA-256 4aa431cd89387e969da006b0a76288ac725fa17e952a83641df80d4b977306af).

Changes since v0.6.0

• Connection status on all clients (#67): only checks that produced a result are shown. Route, DNS, guard and connectivity have no runtime source yet, so they are no longer listed as "unchecked". A running transport reads "Transport: running". The amber colour still means nothing has been verified.
• Android release signing (#66): scripts/sign-android.py uses the new release key from keystore.properties and rejects any other certificate.
• Version 0.6.1, desktop update sequence 11 (#68).

Updating Android

• From 0.6.0 (preview.1 / preview.2): install the APK over the current version. Profiles are kept.
• From 0.5.x and earlier: the app is signed with a new key, so the old version has to be uninstalled. Uninstalling deletes your profiles. Export local profiles first; reconnect portal profiles with an invitation.

Verification

Check	Result
Unit tests, CI on #66/#67/#68 (macOS, Linux, Windows)	PASS
Device: Honor DEL-LX9, Android 12, update 60002→60101 over the installed app, production profile	PASS: profiles kept, VPN works, T-Bank works through the VPN, header without "unchecked" rows
Windows: unit, clippy, build, smoke, installer, service E2E, full E2E (Jenkins rtrust-release-060-native #7, source db8796a)	PASS
macOS: unit, clippy, build, smoke, AmneziaWG/Hysteria/H2, dmg/pkg (same build)	PASS
Linux (flatpak, Arch host)	not published: the build node had no DNS; will follow later
Desktop auto-update channel (latest, sequence 11)	not promoted

The Android native library was built from the same Rust sources as in 0.6.0-preview.2 (the Android crates did not change in 0.6.1).

Details: docs/releases/v0.6.1.md