v0.2.4-alpha
Verifying the Release
In order to verify the release, you'll need to have gpg
or gpg2
installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import carlakirkcohen
's key from keybase:
curl https://keybase.io/carlakirkcohen/pgp_keys.asc | gpg --import
Once you have his PGP key you can verify the release (assumingmanifest-v0.2.1-alpha.txt
and manifest-v0.2.3-alpha.txt.sig
are in the current directory) with:
gpg --verify manifest-carlakirkcohen-v0.2.4-alpha.sig manifest-v0.2.4-alpha.txt
You should see the following if the verification was successful:
gpg: Signature made Wed May 19 09:10:39 2021 SAST
gpg: using RSA key 15E7ECF257098A4EF91655EB4CA7FE54A6213C91
gpg: Good signature from "Carla Kirk-Cohen <[email protected]>" [ultimate]
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256
sum of the binary, and compare that with the following hashes:
cat manifest-v0.2.4-alpha.txt
One can use the shasum -a 256 <file name here>
tool in order to re-compute the sha256
hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.
Finally, you can also verify the tag itself with the following command:
git verify-tag v0.2.4-alpha
Contributors (Alphabetical Order)
Carla Kirk-Cohen
Justin O'Brien
Oliver Guggero
Release Notes
Breaking Changes
- Bumped the minimum required version of
lnd
tov0.11.1-beta
.
Bug Fixes
- Fixes a bug in how TLS connections were initialized which lead to the
missing selected ALPN property
error in node.js and #c clients. - A bug where the rpc server would panic on rpc calls to the outlier and
threshold recommendation api has been fixed.