Install it · 9 of 9
Verifying a download
Checking a downloaded inbuxa tool before you run it: the checksums prove the files arrived whole, and a minisign signature proves the checksums came from us.
Who needs this: Anyone installing the installer, inbuxa-migrate or inbuxa-cli from a release, who wants to confirm a download is genuine before running it.
Every release of the inbuxa installer, inbuxa-migrate and inbuxa-cli carries two small files beside the program:
SHA256SUMS— the checksum of each file in the release. Checking a download against it proves the file arrived whole and wasn't corrupted.SHA256SUMS.minisig— a signature overSHA256SUMS, made with our private key. Checking it proves the checksums themselves came from us, and not from someone who swapped the download and itsSHA256SUMStogether.
The checksum alone tells you the file matches its own SHA256SUMS; the
signature is what ties that SHA256SUMS to inbuxa. Verify the signature
first, then trust the checksums.
Install minisign
minisign is a small, single-purpose signing tool. It is packaged almost everywhere:
apt install minisign # Debian, Ubuntu
dnf install minisign # Fedora
pacman -S minisign # Arch
brew install minisign # macOS
A static binary is also on minisign's own releases if your system has no package for it.
The public key
One key signs every inbuxa tool — the installer, inbuxa-migrate and inbuxa-cli:
RWS1yFYwVuJ7MGJTZXLbhv9+hrEsjrC8Zg+7WmPlM86Sjy0qF/xkoCKq
It is published in each tool's README and here, so a tampered copy of one
can't quietly carry a different key. Its minisign key id is
307BE2563056C8B5.
Verify a download
Download the program and its SHA256SUMS as each tool's page shows, then also
fetch the signature and check it. Taking inbuxa-cli as the example:
base=https://git.coffeylabs.org/inbuxa/inbuxa-cli/releases/latest/download
curl -fLO "$base/SHA256SUMS.minisig"
# 1. The signature proves SHA256SUMS came from us.
minisign -Vm SHA256SUMS -P RWS1yFYwVuJ7MGJTZXLbhv9+hrEsjrC8Zg+7WmPlM86Sjy0qF/xkoCKq
# 2. Now the checksums can be trusted: check the download against them.
sha256sum --check --ignore-missing SHA256SUMS
The first command prints Signature and comment signature verified when the
SHA256SUMS is genuine. The second prints inbuxa-cli-linux-amd64.tar.gz: OK
for the file you downloaded. Both lines have to appear. If either command
fails — minisign says the signature is invalid, or sha256sum prints
FAILED — don't run the program. Fetch it again, and if it still fails, ask
on the forum before trusting it.
The other tools work the same way, with their own release address:
| Tool | Release address |
|---|---|
| The installer | git.coffeylabs.org/inbuxa/inbuxa-installer/releases |
| inbuxa-migrate | git.coffeylabs.org/inbuxa/inbuxa-migrate/releases |
| inbuxa-cli | git.coffeylabs.org/inbuxa/inbuxa-cli/releases |
Release candidates
A release candidate (v27.1-rc.1) is published as a pre-release, so
releases/latest stays on the last final release. Use the candidate's own
tag in the address, in place of latest/download, when you are trying one.
The server, the console and the webmail
Those three are distributed mainly as container images, pulled without a login
from registry.coffeylabs.org — the registry already authenticates what it
serves over TLS. Each image also records the exact source commit it was built
from. Their binary releases carry a SHA256SUMS to check a download against.
For where all of this code comes from, and how each import is checked against the public repositories, see Where the code comes from.