Download RedundaNet 3.0.0

Builds

Release agent/v3.0.0 on GitHub carries five archives and a sha256sums.txt. Each archive holds one folder with the redundanet binary (redundanet.exe on Windows).

sha256sums.txt · Release page on GitHub · All releases

Downloaded? The install page takes it from here: put the binary on your PATH, create your identity, join the network, install the service.

Verify a download

Every release's sha256 and size are in the signed release index, releases/index.yaml on the main branch, with the maintainer's signature in releases/index.sig. The index is signed offline with the maintainer's release key. The agent verifies that signature itself, with the key embedded in every build, and installs only what the index names.

To check a download by hand, compute the archive's sha256 and compare it with the index entry for your version and platform:

# Linux
sha256sum redundanet-3.0.0-linux-amd64.tar.gz

# macOS
shasum -a 256 redundanet-3.0.0-darwin-arm64.tar.gz

# Windows (PowerShell)
Get-FileHash redundanet-3.0.0-windows-amd64.zip -Algorithm SHA256

# the signed index, entry "version: 3.0.0", key "linux/amd64" and so on
curl -fsSL https://raw.githubusercontent.com/adefilippo83/redundanet/main/releases/index.yaml

• releases/index.yaml and releases/index.sig on GitHub.
• releases/README.md: how the index is written, signed and withdrawn.
• The sha256sums.txt beside the archives is written by the release workflow; the index is the signed word.

Channels

Each release in the index belongs to a channel. The agent follows the channel it was installed with.

# a laptop, on the early channel
redundanet service install --network redundanet --channel early

# a Linux storage node: CHANNEL in /etc/redundanet3/agent.env, then
sudo systemctl restart redundanet-agent

Code signing

Windows signing through SignPath and macOS notarization are set up in the release workflow but not yet active (accounts pending); until then every binary is unsigned and the signed release index is the way to verify a download on every platform. Linux binaries are never code-signed; the index covers them.

The policy, the team and what a signature would say are in the code signing policy of the README. Each release page states whether its binaries are signed.

The agent updates itself afterwards

You download once. From then on the agent checks the signed index hourly, downloads a newer release of its channel, verifies the hash, runs the new version in probation for up to two minutes, keeps the old binary as redundanet.old, and rolls back by itself if the new one does not reconnect. redundanet update check, update apply and update status drive it by hand.