github breez/breezmobile 0.17.bugfixes.4
0.17 Bug fixes

pre-release16 days ago

Changes

  • Bug fixes

Verifying the release

In order to verify the release, you'll need gpg or gpg2 installed on your system. Breez puts hashes of the release files in a SHA256SUM file. The SHA256SUM file is then signed with the Breez GPG key. In order to verify the signatures, complete the following steps:

Download 1733260939-1.apk, SHA256SUMS and SHA256SUMS.asc from the release assets:

curl \
-LO https://github.com/breez/breezmobile/releases/download/0.17.bugfixes.4/1733260939-1.apk \
-LO https://github.com/breez/breezmobile/releases/download/0.17.bugfixes.4/SHA256SUMS \
-LO https://github.com/breez/breezmobile/releases/download/0.17.bugfixes.4/SHA256SUMS.asc

Download Breez's GPG key:

curl -O https://breez.technology/breez.technology.gpg

Verify that the fingerprint is 02B5 268A 5D94 F50C D8B2 1734 C9B2 A8A6 46E9 4858

gpg --show-keys --fingerprint < breez.technology.gpg

Check the signature of the SHA256SUM file:

gpgv --keyring ./breez.technology.gpg SHA256SUMS.asc SHA256SUMS

This should give the following output:

gpgv: Signature made Thu 05 Dec 2024 15:13:49 UTC
gpgv:                using EDDSA key C4193B7F45B972375DFFDBACF5C584019396C59D
gpgv: Good signature from "Breez Technology <contact@breez.technology>"

Finally check the apk file hash:

sha256sum -c SHA256SUMS

This should give the following output:

1733260939-1.apk: OK

Don't miss a new breezmobile release

NewReleases is sending notifications on new releases.