Repository navigation
FreeNet Hub 4.3.7 Final
FreeNet Hub 4.3.7 Final
Current desktop install authority:
Windows:
- FreeNetHub_4.3.7_R51_Setup.exe
- SHA-256: 8283803146E1625A31F0223487A63C05D7B7D9C3D8B59D1A7432D14AB9D4FF11
- Revision: 4.3.7-r51-protocol-expansion-2
- Final asset rebuilt from exact main after Linux R18 metadata alignment; installer manifest preflight PASS_RAW_BYTES_MATCH_APP_MANIFEST.
Linux:
- FreeNetHub_4.2.0_Linux_R18.zip
- SHA-256: 3C9254840C85B6D7305B0986209FF96EBEE578193D193538E8E8D45924ECBCD7
- Revision: 4.2.0-linux.18-r45
Linux R18 browser/node hotfix:
- Fixes NODE browser routing so Firefox uses the selected sing-box SOCKS5 listener on 127.0.0.1:19460 with remote DNS.
- Adds NODE pre-launch readiness verification and records the selected proxy port in session state.
- Uses bounded verification retry to tolerate a transient first trace failure without blind reruns.
- Standard Ubuntu Snap Firefox 157 was revalidated after the required Ubuntu 26.04 reboot; no alternate Firefox runtime is required.
- Fresh public node refresh: 8/8 sources, 2,876 parsed inputs, 2,000 merged nodes.
- Owner-host live NODE acceptance: VMess via AURX_HTTP_VERIFIED, exit 31.76.11.83 / DE, Browser scope.
- Exact R18 ZIP rebuild is reproducible; 23/23 SHA256SUMS PASS and 7/7 extracted package tests PASS.
Hosted validation:
- Exact final SHA: 06d3459
- Candidate CI run #223 / 37492728341: 10/10 SUCCESS.
- Main CI run #224 / 37494197358: 10/10 SUCCESS on the same SHA.
- windows-unit: SUCCESS
- windows-installer-fresh: SUCCESS
- linux-static + exact R18 package: SUCCESS
- console-virtual-e2e: SUCCESS
- windows-virtual-signing: SUCCESS
- android-build: SUCCESS
- android-emulator-runtime: SUCCESS
- ios-static: SUCCESS
- ios-simulator-runtime: SUCCESS
- virtual-acceptance: SUCCESS
Public tree/security:
- Public manifest verification: PASS
- Public security scan: PASS
- Public manifest: 516 files
- PUBLIC_MANIFEST SHA-256: 0E5A866F0D1D300D54C314613127BE6EA496B52AAA97EE05AB5E82CA9EE053C9
Remaining external boundaries:
- Public-trust Windows Authenticode requires an external trusted signing identity.
- Physical console/game/country field validation requires target hardware/network.
- Production mobile forwarding/signing/real-device validation remains separate from the passing virtual fail-closed runtime gates.
For new desktop installs, use only the two assets above.