greenart7c3/Amber v7.0.0-pre2

Release 7.0.0-pre2

on GitHub

Amber 7.0.0-pre2

• New: a local WebSocket relay on desktop (ws://127.0.0.1:7777, port editable or opt out under Settings → Desktop) so NIP-46 clients on the same machine reach the bunker without public relays
• New: an A to Z toggle on the Applications screen, on Android and desktop, to sort apps alphabetically instead of by most recent use
• Offer newer pre-releases to beta users and check both update relays, so the updater no longer misses a pre-release
• Ask for the camera permission before scanning a QR code, and point to the system settings when it is denied
• Send NIP-46 responses, feedback, application backups and desktop crash reports as soon as the first relay accepts them instead of waiting for every relay
• Fix relays removed in the desktop New bunker dialog coming back in the bunker:// URI and the saved app
• Update rustls to 0.23.46 in the built-in Tor engine, fixing four security advisories

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-pre2.txt and manifest-v7.0.0-pre2.txt.sig are in the current directory) with:

gpg --verify manifest-v7.0.0-pre2.txt.sig manifest-v7.0.0-pre2.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-pre2.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.