Skip to content

Garrison 0.1.1

Choose a tag to compare

@relative23 relative23 released this 13 Nov 01:22
· 440 commits to main since this release

Host care gets three fixes that the first weeks on a real server asked for.
It works with Stalwart 1.1.0, like 0.1.0.

What changed

  • Firewall units of the host's own. A host whose own unit loads its
    nftables rules got a firewall warning it could only silence by leaving the
    check out. Name such units in firewall_units of the host-care provider;
    the check then asks whether one of them runs.
  • The update check says what keeps it out. Where only root may read a
    folder in /var/cache/dnf, as a dnf run under umask 077 leaves it, the
    check names the repositories and that chmod 755 on their folders lets it
    read them.
  • The update check follows the host. It asks the package manager again
    within five minutes after packages are installed or removed or new metadata
    is fetched, so a warning goes away soon after the update is installed.

The changelog
has the details.

Upgrading

From 0.1.0, garrison upgrade with the archive for your architecture and its
.minisig. Nothing in the configuration has to change; firewall_units is
optional. garrison install --rollback returns to 0.1.0; take
firewall_units out of the configuration first, as 0.1.0 does not know it.

Checking a download

Both archives were built twice by the release workflow and once on the
maintainer's machine, with byte-identical results, and GitHub's build
attestation names the commit they come from. Check the signature before you
unpack an archive:

minisign -Vm garrison-0.1.1-x86_64.tar.gz -P RWSKAjJdo0lsYJJA64rSgwP6KeVtTEbgqB12xkoAVxzQd+l9U0OplCP6

It must end with Trusted comment: garrison 0.1.1 x86_64 (or aarch64).

Archive SHA-256
garrison-0.1.1-x86_64.tar.gz 60e82f8a0239af9898072961d83f31a404dc3e5505a33a1da0e31ab661ece657
garrison-0.1.1-aarch64.tar.gz 87665ee48d547ad060bd8637bf1ff152c5c81054e9efdce38741bcd631da43c7