Skip to content

Wildbloom Node 0.3.3 preview 1

Pre-release
Pre-release

Choose a tag to compare

@TheCryptoDonkey TheCryptoDonkey released this 06 Oct 12:38

Wildbloom Node 0.3.3 preview.1 includes Windows privacy protections for owner receipts and repair work, alongside the existing desktop health checks, threshold recovery, automatic owner repair and explicit interrupted-file cleanup.

  • New Windows private directories grant access to the current account, SYSTEM and Administrators. Desktop and daemon share the checks and refuse broad/null ACLs and reparse points.
  • Windows CI tests actual read/write denial from a second unprivileged account. Native desktop acceptance checks persisted receipt, report and lock permissions.
  • Future signed releases now verify installer/updater bytes and expected signers/timestamps. These preview downloads do not have trusted Windows signing or macOS Developer ID/notarisation, and are not trusted automatic updates.

If existing Windows state is refused, stop repair and follow the desktop guide. Preserve receipt backups; permissions are not silently rewritten. The protections do not isolate data from administrators or malware running as the owner.

The six installers cover Linux x64 (deb/rpm), Windows x64 (MSI/NSIS), and Apple Silicon/Intel macOS (DMG). SHA256SUMS and build-provenance.json identify the exact artifacts and source. Source: 39e46f4d5802d8660ce1617956cf5ae9b6200e11.

Validation includes native lifecycle CI on Linux/macOS/Windows, browser threshold recovery and automatic repair against this exact daemon revision, installed-package checks for deb/NSIS on hosted Linux and Windows (rpm/MSI are built and checksummed), and real-Tor node loss/repair/source shutdown/identity restart on one Mac. Both macOS architectures have bundled daemon checks; downloaded DMGs receive local version/signature inspection. Evidence and its precise scope are retained in build-provenance.json.

Independent physical-device recovery, retail-machine installer/update acceptance, trusted signing and independent security review remain open. Erasure coding protects availability within the selected threshold; it does not replace encryption, recovery-key backups or independent storage placement.