Skip to content

v0.2.3-alpha
Compare
Choose a tag to compare
@carlaKC carlaKC released this 18 Jan 13:16
· 187 commits to master since this release
v0.2.3-alpha
This tag was signed with the committer’s verified signature.
guggero Oliver Gugger
GPG key ID: 8E4256593F177720
Learn about vigilant mode.
276b698
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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-v0.2.3-alpha.txt.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.2.3-alpha.txt'
gpg: Signature made Thu Mar 19 09:19:19 2020 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.3-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.3-alpha

Contributors (Alphabetical Order)

Carla Kirk-Cohen
Carsten Otto
Oliver Guggero

Release Notes

  • Fixed compile time compatibility with lnd v0.12.0-beta.
  • The output of the audit rpc is now sorted by ascending timestamp.
  • A pre-set custom category for Lightning Pool has been added to the audit cli, and can be used to separate all pool-related transactions into their own category called pool using audit --pool-category.

Bug Fixes

  • A bug in the audit custom categories functionality which switched on-chain and off-chain categories has been fixed.
Assets 26
Loading