greenart7c3/Amber v7.0.0-pre4

Release 7.0.0-pre4

on GitHub

Amber 7.0.0-pre4

• New: an amber command line client that asks a running Amber for NIP-46 signatures, so scripts and AI agents can sign events without speaking the protocol, shipped for Linux, macOS and Windows
• New: send desktop request notifications through the system on Windows and macOS too, with Approve / Reject buttons
• Show on the onboarding page where your accounts are when an offline Amber is installed under the other application id, with a button to open it
• Keep the offline app on the online application id so installs from the releases page and Obtainium update in place, and publish the "Amber Offline" Zapstore listing under its own id
• Check the update relays that are still reliable: relay.zapstore.dev, relay.primal.net, relay.snort.social, offchain.pub and purplerelay.com
• Fix desktop request notifications staying on screen after the request is answered in Amber
• Fix accounts of installs from 3.3.0 or older not being restored
• Fix crashes when the Android keystore prunes a cipher operation, by retrying it

Download it with Zapstore, Obtainium, f-droid or download it directly in the releases page

If you like my work consider making a donation

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 the keys that have signed this release if you haven't done so already:

gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

Once you have his PGP key you can verify the release (assuming manifest-v7.0.0-pre4.txt and manifest-v7.0.0-pre4.txt.sig are in the current directory) with:

gpg --verify manifest-v7.0.0-pre4.txt.sig manifest-v7.0.0-pre4.txt

You should see the following if the verification was successful:

gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg:                using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"

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-v7.0.0-pre4.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.

Older versions

Release notes for previous versions live in docs/changelogs.