Skip to content

Release v6.5.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Aug 11:37
v6.5.0
0f313eb
This commit was signed with the committer’s verified signature. The key has expired.
greenart7c3 greenart7c3
GPG key ID: 885822EED3A26A6D
Expired
Verified
Learn about vigilant mode.

Changelog

Amber 6.5.0

  • Fix relay-auth whitelist authorizing any requester (GHSA-vx4h-56qj-wcp7)
  • Fix NIP-46 freshness and replay protection (GHSA-h9fv-9247-3582)
  • Envelope-encrypt NIP-46 connection secrets at rest (GHSA-5fjp-ghh8-wch8)
  • Add opt-in unlocked-device requirement for Keystore key (GHSA-8844)
  • Authorize before decrypt in SignerProviderQuery (GHSA-8844)
  • Redact key material from logs and crash reports (GHSA-8844)
  • Set FLAG_SECURE on sensitive QR surfaces (GHSA-8844)
  • Warn on insecure ws:// connections to non-onion relays (GHSA-8844)
  • Parse unknown permission remember types as NEVER to fail closed (GHSA-8844)
  • Lazy-load account keys on cache miss and properly zeroize them on logout (GHSA-8844)
  • Update translations for new string resources
  • Fix CI test failures and linter violations

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

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

Assets 15
Loading