Skip to content

Release v6.2.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Jun 11:55
v6.2.2
4703e5f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Amber 6.2.2

  • Show native app icons and NIP-46 client metadata on the request screens and app list
  • Persist client metadata on every connect and capture the native app icon and name at connect/accept time
  • Add support for event kind 30618
  • Add an export/share button to the Logs screen
  • Separate default and connection relays in the Active relays screen, and use default relays for new relay-delivered bunker connections
  • Stop logging decrypted NIP-46 request/response bodies and store encrypt/decrypt payloads as ciphertext, decrypting on demand
  • Gate all logcat output behind BuildConfig.DEBUG
  • Force always-ask for null-package (browser) callers
  • Flag nsec, ncryptsec and seed words clipboard copies as sensitive and clear them after a delay
  • Add explicit backup/data-extraction excludes as defense-in-depth
  • Fix a crash from nested scrolling in the Active relays screen
  • Fix a LazyColumn duplicate key crash from racy bunker request dedup
  • Fix the release update check missing a file subscription on an EOSE race
  • Fix the overlapping feedback type selector with long labels
  • Warm up the Coil ImageLoader off the main thread
  • Update translations

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

gpg --verify manifest-v6.2.2.txt.sig manifest-v6.2.2.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-v6.2.2.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.

Assets 15
Loading