Repository navigation
v4.2.4 — Security fixes: verified node RPC endpoint, handover hardening
What's new
- The security fix release for the external audit of v4.2.3. That audit found no critical or high issues (one medium, eleven low, twelve informational); every item is fixed here, or accepted with the reason recorded in SECURITY.md. An audit of these changes found no critical or high findings either (one medium, three low), and every verified finding was fixed in this release. No feature changes, no new permissions, and the bundled node and miner binaries are unchanged from v4.2.3.
- The app now verifies it is talking to its own node. The node does not fail when its RPC port (9944) is taken — it silently rebinds to a random port — so polling a fixed address could have meant polling another app's listener. The app now adopts the RPC address and peer identity from the node's own startup output and checks the identity on every poll. The activity recording and the identity transfer read through a record of the same facts that stays valid only while that node process lives.
- Log-derived figures count only the node's own lines. Statistics, the miner's start gate and the diagnostics' WARN/ERROR counts act only on lines in the node's own header format; control and bidi control characters are stripped before a line is stored, shown or shared; and shared diagnostics now mask every non-loopback address, not only the device's own.
- Less of the node is visible by default. Your display name is passed to the node only while telemetry is on (peers otherwise see the default name); mDNS no longer advertises the node on the local network; the Prometheus metrics endpoint and offchain workers are off.
- Handover hardening. The confirmation number is now derived from the handover's own secret instead of the transfer code; packages are capped at 16 MiB (about 19,900 checkpoints) and imports stream into place instead of buffering the whole file in memory; the transfer-code entry and dialogs gain the same input and screen protections as the inner-hash editor. Both devices need v4.2.4 for a handover — an older version cannot read the new package (a v4.2.4 device still reads packages from older versions).
Install
Download quantus-node-v4.2.4.apk (63,566,527 bytes) and install it over your current version — settings and records are kept.
SHA-256: 845f5f7375ffb776d3d0959608c6d56a5bcac031d43a440f798aad99a26e3b3d
Note
Published ahead of on-device verification; the on-device checks (above all, the node reaching sync through the adopted endpoint, and a mining start with the new launch arguments) follow. A further external review of this release is scheduled; any findings will be addressed in a later release.
Full details: CHANGELOG.md