Verifying downloads
Every release lists SHA256SUMS and SHA512SUMS of its archives, each with a detached GPG signature
(SHA256SUMS.asc, SHA512SUMS.asc). The signing key is
dayzmake release signing key (https://github.com/bzed/dayzmake)
ed25519, expires 2029-11-15
6624 41B3 6A57 85AD 18FB 8667 DF75 3D99 D064 EB7E
The public key is a release asset (dayzmake-release-key.asc) and is published at
https://bzed.github.io/dayzmake/release-key.asc. Get it from the site or from a release, and compare the
fingerprint with the one above (and with the one in the repository’s AGENTS.md) before you trust it.
Download the archive you want together with the checksum files and the key, from the release page or with the GitHub CLI (without a tag it downloads the latest release):
gh release download -R bzed/dayzmake -p '*debian-trixie*' -p 'SHA*' -p 'dayzmake-release-key.asc'
On Linux or macOS, in the folder with the downloaded files (the Linux archive is named like dayzmake-v3.2.0-debian-trixie-x86_64.tar.gz):
gpg --import dayzmake-release-key.asc
gpg --fingerprint 662441B36A5785AD18FB8667DF753D99D064EB7E
s=$(gpg --status-fd 1 --verify SHA256SUMS.asc SHA256SUMS 2>/dev/null)
[ "$(grep -c '^\[GNUPG:\] NEWSIG' <<<"$s")" = 1 ] &&
grep -q '^\[GNUPG:\] GOODSIG DF753D99D064EB7E ' <<<"$s" &&
grep -q '^\[GNUPG:\] VALIDSIG 662441B36A5785AD18FB8667DF753D99D064EB7E ' <<<"$s" &&
! grep -Eq '^\[GNUPG:\] (EXPSIG|EXPKEYSIG|REVKEYSIG|BADSIG|ERRSIG) ' <<<"$s" &&
echo 'signature OK'
sha256sum -c --ignore-missing SHA256SUMS
The check must print signature OK. Do not rely on the Good signature text or the exit status of a plain
gpg --verify: gpg prints that text, and exits with 0, for a signature of a key that has expired since. Only the
GOODSIG status line means that the signature is good and its key is neither expired nor revoked, and VALIDSIG
names the key that made it. The check also demands that the file holds exactly one signature and that no
EXPSIG, EXPKEYSIG, REVKEYSIG, BADSIG or ERRSIG line appears, so a second, bad signature cannot hide behind a good one. The warning that the key is not certified with a trusted signature is expected as long
as you have not signed it yourself, so the check ignores it; the fingerprint is what counts. sha256sum -c --ignore-missing checks
the archives you downloaded and ignores the ones you did not (on macOS use shasum -a 256 -c --ignore-missing).
SHA512SUMS works the same way with sha512sum.
On Windows, in PowerShell with Gpg4win installed, check the signature and compare the
hash of your download with its line in SHA256SUMS:
gpg --import dayzmake-release-key.asc
$s = @(gpg --status-fd 1 --verify SHA256SUMS.asc SHA256SUMS 2>$null)
(@($s | Select-String -Pattern '^\[GNUPG:\] NEWSIG').Count -eq 1) -and
[bool]($s | Select-String -Quiet -Pattern '^\[GNUPG:\] GOODSIG DF753D99D064EB7E ') -and
[bool]($s | Select-String -Quiet -Pattern '^\[GNUPG:\] VALIDSIG 662441B36A5785AD18FB8667DF753D99D064EB7E ') -and
-not ($s | Select-String -Quiet -Pattern '^\[GNUPG:\] (EXPSIG|EXPKEYSIG|REVKEYSIG|BADSIG|ERRSIG) ')
$file = 'dayzmake-v3.2.0-windows-x86_64.zip'
$expected = ((Select-String -SimpleMatch $file SHA256SUMS).Line -split '\s+')[0]
(Get-FileHash -Algorithm SHA256 $file).Hash -eq $expected.ToUpper()
The signature check and the last line must each print True.