## Amber 7.0.0-pre1 - New: Amber for desktop (Windows, macOS and Linux) — a NIP-46 signer that mirrors the Android permission model, with a mandatory passphrase lock, keys kept in the OS credential store and each account's data encrypted at rest - New: approve or reject desktop requests from the notification, plus a tray icon, start-on-boot, Tor support, nostrconnect:// links and per-app relay management - New: a NIP-5F local socket signer on desktop so CLI tools sign through the same permission and approval pipeline as bunker apps - New: a pure-black AMOLED theme and an appearance setting to pick the theme, and a fix for unreadable light-on-amber elements in the dark theme - New: search saved accounts by name or npub in the account switcher and the approval account picker, and keep favorite accounts at the top - New: list the backed-up applications before a restore and pick which ones to restore, refusing encrypt-to-self permission backups - Show the request description in redacted bunker notifications - Show which account each batched request signs as, never show a connect request on the batch screens, and apply the auth whitelist to relay auth there - Keep each calling app's NIP-55 requests on its own screen, and sign intents with the account that authorizes them - Show decoded outputs, change and fee on desktop sign_psbt approvals - Keep logs and activity longer with a size budget - Copy decrypt results to the clipboard as sensitive and clear them - Add keyboard selection and remember-cycling for pending requests on desktop - Fix '+' in app names that clients form-encode in bunker URIs, and sanitize client-chosen app names on both apps so they stay out of notification bodies - Return the real result for NIP-46 and NIP-55 seal encrypt/decrypt requests - Never let an older kind-0 overwrite a newer profile, and only accept profile events the fetch actually asked for - Keep the NIP-46 subscription 'since' from following future-dated events - Handle revoked and expired NIP-46 connections: never resurrect a revoked one from its queued requests, treat an expired one as absent, and replace a saved connection when a nostrconnect reuses its key - Answer a rejected or malformed NIP-46 request with an error instead of crashing or staying silent - Verify the NIP-46 sender's key before using the account key with it, require a lowercase hex client key in nostrconnect URIs, and rate-limit NIP-46 events from unknown senders - Handle a locked device: answer each locked request once even when several relays deliver it, keep requests the lock interrupted queued for redelivery, check the lock before opening NIP-46 requests, and explain the software-only unlock gate on Android 8 - Keep desktop crash reports unreadable on disk while a passphrase is set, and keep the keyring second factor across passphrase changes - Redeliver NIP-46 requests interrupted by the passphrase lock, enforce connection expiry at request time, and drop requests a stored app sends to another connection's key (desktop) - Refuse to sign PSBTs whose sighash does not commit to all outputs, and label PSBT change by the output script instead of requester metadata - Only accept Zapstore release events signed by the developer key, refuse an update without a download hash, and never treat an unparsable release version as newer - Refuse WebDAV redirects that leave HTTPS, and connect directly when Tor is not used - Require per-listener credentials on the built-in Tor SOCKS port, and fail closed to a proxy when built-in Tor releases its port - Decide Tor bypass on the parsed host instead of a URL substring, and resolve .localhost and .local relay names without the system resolver - Serve only share/ and updates/ from the FileProvider, load client icons only over https and native icons only from Amber's store, and accept notification routes only from Amber's own intents - Record encrypt/decrypt intents under the account that handled them, make the generic permission lookup exact and deterministic, and treat blank-relay auth grants as all relays on the approval screens - Scope the provider's v3 decrypt pre-check to the requested kind, and only let accepting grants past it - Delete an account's databases at logout - Make all PendingIntents immutable - Load settings before anything can read them on a cold start, and start the connectivity functions after every startup - Refresh relay subscriptions when the device is unlocked, and don't report a locked Keystore as a broken key - Show failed backup imports in a dialog instead of a toast, and translate the failed key export and account import messages - Add event kind labels used by ngit, divine, Staircase and White Noise - Update Quartz to 2.3.0, OkHttp and the rest of the dependency stack, and port Quartz's relay socket fixes to both apps - Make the release APKs and the desktop installers reproducible, and verify the checksum of every dependency and plugin Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v7.0.0-pre1) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash 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-pre1.txt` and `manifest-v7.0.0-pre1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v7.0.0-pre1.txt.sig manifest-v7.0.0-pre1.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v7.0.0-pre1.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](docs/changelogs/README.md).

## Amber 6.6.9 - Fix nostrconnect:// connections approved from the multi-request screen never getting a reply, and reply on the relays from the nostrconnect:// URI - Group the multi-request screen by app, showing each app's name, icon and request count, and keep "remember my choice" per app - Fix revoked permissions that could keep working until the cache was cleared, and respect reject rules for fully trusted apps (GHSA-8f7m-9g64-vrjw) - Clear a copied nsec, ncryptsec or seed words after 60 seconds even when Amber is in the background or was closed (GHSA-g62f-m6pm-jv9p) - Fix possible loss of the nsec and seed words when changing the "require unlocked device" setting (GHSA-wv7c-hq2j-ppc5) Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.9) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.9.txt` and `manifest-v6.6.9.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.9.txt.sig manifest-v6.6.9.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.9.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](docs/changelogs/README.md).

## Amber 6.6.8 - Fix a crash on some devices when opening Amber from another app or after rejecting a request, caused by the system failing to read the referring app Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.8) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.8.txt` and `manifest-v6.6.8.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.8.txt.sig manifest-v6.6.8.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.8.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](docs/changelogs/README.md).

## Amber 6.6.7 - Fix relays staying disconnected until the app was force closed: relays marked dead after a stretch of bad connectivity now get another chance after a 15 minute cooldown, and failed connection attempts are no longer counted twice - Reset relay connections when a VPN comes up or goes down, or when the device regains internet access, the same way switching between Wi-Fi and mobile data does; network changes now drop stale sockets and clear the reconnect backoff so relays come back immediately - Detect web requests from browsers other than Chrome (such as DuckDuckGo), which previously failed with "Unknown signer type" - Fix a crash when a permission was saved for an application that had just been deleted or reset Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.7) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.7.txt` and `manifest-v6.6.7.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.7.txt.sig manifest-v6.6.7.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.7.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](docs/changelogs/README.md).

# Changelog ## Amber 6.6.6 - Fix the nostrconnect parser corrupting connect-param values that contain `=` (such as base64-padded secrets): the connect response returned mangled values instead of the original secret, so NDK-based clients failed their secret check - Fix white text and icons on light-amber surfaces in dark theme (Edit Relays floating action button, add-relay icon buttons, selected filter chips on the feedback screen) - Fix the Tor/proxy status icon in the top app bar being nearly invisible in light theme — status icons now use theme-aware colors in both themes, and the relay reconnect icon matches the adjacent relay count - Feedback issues are now published to the relays advertised on Amber's repository announcement instead of a hardcoded relay, falling back to the previous behavior when the announcement can't be fetched; longer timeouts on Tor so slow relays still confirm the publish Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.6) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.6.txt` and `manifest-v6.6.6.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.6.txt.sig manifest-v6.6.6.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.6.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](docs/changelogs/README.md).

## Amber 6.6.5 - Harden application backups: backup events published to relays are now encrypted with a dedicated key derived from your account key (via HKDF, outside the NIP-44 derive-key namespace) instead of your main identity key, so apps holding a remembered `nip44_decrypt` permission can no longer fetch the kind 30078 backup and read its payload, including per-app NIP-46 secrets and local keys; existing identity-encrypted backups still restore through a fallback until the next publish overwrites them - Fix the backup restore prompt never appearing after logging out and back in when backup publishing is disabled — the exact case restore exists for Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.5) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.5.txt` and `manifest-v6.6.5.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.5.txt.sig manifest-v6.6.5.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.5.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](docs/changelogs/README.md).

# Changelog ## Amber 6.6.3 - Fix the "start service on boot" setting not being respected after an app update - Fix a crash on the offline flavor caused by a `SecurityException` from WorkManager network tracking left over from an upgrade - Fix the Russian translation of the "Amber is a free and open source project" string - Fix a release build failure caused by an AGP 9.4.0 regression Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.3) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.3.txt` and `manifest-v6.6.3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.3.txt.sig manifest-v6.6.3.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.3.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](docs/changelogs/README.md).

# Changelog ## Amber 6.6.1 - Fix parsing of incoming permission lists when a permission has no `kind` field in its JSON, so the whole list no longer fails to load - Fix rejected signer requests not returning the request id in the result, leaving calling apps unable to match the rejection to their request - Update the default signer relays to `auth.nostr1.com`, `bucket.coracle.social`, `nrs.primal.net` and `relay.nip46.com`, and add `indexer.coracle.social` to the default indexer relays (#518) - Add missing translations for Marmot protocol event kinds Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.1) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.1.txt` and `manifest-v6.6.1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.1.txt.sig manifest-v6.6.1.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.1.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](docs/changelogs/README.md).

## Amber 6.6.0 - New: pre-approve individual permissions when connecting an app under the "Manually approve each permission" policy — an "Add permission" button lets you pick from the full permission catalog (searchable, including custom sign-event kinds) so those requests are approved automatically while everything else still asks - New: when a NIP-46 connect request arrives while the kill switch is enabled, Amber now asks whether to disable it so the request can be answered, and the kill switch gained a toggle in the Settings network section - Toggling the "Enable biometrics" setting now requires biometric authentication first, so the setting cannot be deactivated without authorization and broken sensors are caught before activation - Toggling "require unlocked device" now shows a progress indicator with a do-not-close warning while every stored secret is re-encrypted, instead of silently freezing - Fix the account picker not scrolling and its title not being visible - Fix a crash in profile feed subscriptions when an account is removed while its events are being processed - Trim the image and trust-score caches when the system reports memory pressure, so the 32 MB bitmap cache no longer stays fully resident while the app is in the background - Performance: cache decrypted application lists so periodic relay refreshes stop re-decrypting every application row through the Keystore (the dominant native memory user on populated accounts), and warm up timezone data off the main thread to remove a ~170 ms disk read during the Applications screen's first composition - Update Kotlin to 2.4.10, Gradle to 9.7.1, Quartz to 1.14.0 and the rest of the dependency stack Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.0) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.6.0.txt` and `manifest-v6.6.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.6.0.txt.sig manifest-v6.6.0.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.6.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](docs/changelogs/README.md).

# Changelog ## Amber 6.5.2 - Fix the Applications screen taking several seconds to load on populated accounts: the list no longer decrypts the encrypted `secret`/`localKey` columns it doesn't render, and the Keystore key handle is cached instead of re-fetched for every decryption - Warm the account cache at app start so the switch-accounts button lists all accounts again instead of only the current one - Fix a crash when scrolling the activity history screens caused by the same row appearing in two loaded pages at once - Debounce relay status-counter notification updates so the status notification no longer freezes on stale text during bursts of relay traffic Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.5.2) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.5.2.txt` and `manifest-v6.5.2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.5.2.txt.sig manifest-v6.5.2.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.5.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. ## Older versions Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.5.1 - Re-encrypt NIP-46 connection secrets stored in the per-account database during Keystore key rotation, so toggling "require unlocked device for key access" no longer leaves connections undecryptable - Fix crash in EditPermission due to an invalid localKey Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.5.1) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.5.1.txt` and `manifest-v6.5.1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.5.1.txt.sig manifest-v6.5.1.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.5.1.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](docs/changelogs/README.md).

# 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](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.5.0) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash 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: ``` bash gpg --verify manifest-v6.5.0.txt.sig manifest-v6.5.0.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash 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](docs/changelogs/README.md).

## Amber 6.4.0 - Redesign the multi-request approval screen with explicit Approve/Deny toggles per request and per group, replacing the select-and-confirm flow, with proper error responses for denied bunker requests - Add support for 113 more event kinds with localized labels across all shipped locales, including the Concord kinds, NIP-51 git repository bookmarks and NIP-53 room presence - Add light/dark Compose previews for the multi-event approval screens - Ignore platform finalizer-watchdog TimeoutExceptions in crash reports - Fix a NegativeArraySizeException crash in relay subscriptions by guarding shared maps for concurrent access - Translate the new approval strings (approve, confirm, remember my choice for) in all supported locales - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.4.0) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.4.0.txt` and `manifest-v6.4.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.4.0.txt.sig manifest-v6.4.0.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.4.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](docs/changelogs/README.md).

# Changelog ## Amber 6.3.0 - Group multi-request approval lists by type and kind, with collapsible groups and per-group remember and scope options - Only use the fullscreen layout when there is a single bunker request - Add support for Expert List (kind 12022) and Expert Pack (kind 32022) events - Add a privacy mode setting to disable logs and activity stats - Add a setting to disable relay trust scores - Add a restart action and live status to the built-in Tor notification - Fetch the user's NIP-65 relay list before fetching profile metadata - Remove relay.damus.io from the default relay lists - Fix the event date shown as Jan 1970 in the Show Details modals - Fix all Android Lint warnings and enforce lint in the git hooks - Upgrade Gradle to 9.6.1 and AGP to 9.3.0 - Move older release notes to per-version files under docs/changelogs - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.3.0) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.3.0.txt` and `manifest-v6.3.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.3.0.txt.sig manifest-v6.3.0.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.3.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](docs/changelogs/README.md).

## Amber 6.2.3 - Add a configurable profile fetch interval setting with never/always options - Show a profile picture in the account switch bottom sheet - Scope profile subscriptions by the current account, driven by composables - Add error handling to bunker permission parsing - Trim the shipped languages to the curated set of locales - Set the benchmark build app name to "Amber Benchmark" - Fix a StrictMode DiskReadViolation in Coil onSuccess logging - Load the account off the main thread to fix a StrictMode keystore violation - Read account name and picture off the main thread in the account switch sheet - Avoid eager KeyPair() on the main thread in the login/signup screens - Fix the settings section header contrast in the light theme - Fix an unescaped apostrophe in the Turkish profile fetch interval string - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.3) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.2.3.txt` and `manifest-v6.2.3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.2.3.txt.sig manifest-v6.2.3.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.2.3.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.

## Amber 6.2.1 - Reduce battery drain from relay reconnects and websocket pings - Drop dead relays from the subscription pool instead of only backing off reconnects - Do not wake the device when updating the relay notification - Modernize the settings screen with grouped Material 3 cards and distinct icons - Fix navigation crash when opening application permissions - Fix a crash when writing the Bunker connect screen state off the main thread - Reply with an error for invalid bunker request methods - Add NIP-46 logout method support - Add support for event kind 39701 (Public web bookmark) - Fix a per-account database connection leak by building databases atomically - Refresh app bar titles when the language changes - Update Kotlin to 2.4.0 and Gradle to 9.5.1 - Update translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.1) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.2.1.txt` and `manifest-v6.2.1.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.2.1.txt.sig manifest-v6.2.1.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.2.1.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.

## Amber 6.2.0 - Add NIP-44 v3 encryption support, including a dedicated approval screen, intent preview, bunker preview, history logging and auto-reject for invalid requests - Register NIP-44 v3 ContentProvider authorities - Auto-accept NIP-46 ping requests on connect - Ignore empty `` intents so the app can be opened directly - Simplify the invalid intent screen to only close the app - Use a segmented toggle for option pickers, with a scrollbar and shrinking segments when they get too narrow to fit the screen - Remove the `sign_message` signer method - Remove the 1 minute option from the sign-automatically pickers - Disable resource shrinking in release builds - New Crowdin translations Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.0) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.2.0.txt` and `manifest-v6.2.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.2.0.txt.sig manifest-v6.2.0.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.2.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.

## Amber 6.1.0 - Better layout when connecting a new app - Fix some reported crashes - Fix signer dialog not closing after accepting a bunker request - Show name and npub when showing your account - Add a select/deselect all option in the permissions screen when connecting a new app - Show a invalid request screen when receiving a invalid request - Preview missing translation report before sending it - Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) - Some optimizations when accepting/rejecting intent requests - Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications - Added a option to disable the service start on boot - Only start the profile subscription for the current account - Always return hex key when logging in to an app to comply with nip 55 - Added a close button in the empty requests screen - Added loading state to the report screens - Support for beta releases for the auto updater - Add a reset button for bunkers - Fix a connection issue when connecting to a new bunker by @Alex Gleason - Fix app starting on boot when not enabled - Support for sign psbt method - Fix relay auth whitelist when the relay contains port number - Change selectable options to be a bottom sheet - Added more options to the automatically sign this for - Add an encrypted applications backup that can be restored on a new device Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0.txt` and `manifest-v6.1.0.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.1.0.txt.sig manifest-v6.1.0.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.1.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.

## Amber 6.1.0-pre3 - Better layout when connecting a new app - Fix some reported crashes - Fix signer dialog not closing after accepting a bunker request - Show name and npub when showing your account - Add a select/deselect all option in the permissions screen when connecting a new app - Show a invalid request screen when receiving a invalid request - Preview missing translation report before sending it - Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) - Some optimizations when accepting/rejecting intent requests - Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications - Added a option to disable the service start on boot - Only start the profile subscription for the current account - Always return hex key when logging in to an app to comply with nip 55 - Added a close button in the empty requests screen - Added loading state to the report screens - Support for beta releases for the auto updater - Add a reset button for bunkers - Fix a connection issue when connecting to a new bunker by @Alex Gleason - Fix app starting on boot when not enabled - Support for sign psbt method - Fix relay auth whitelist when the relay contains port number - Change selectable options to be a bottom sheet - Added more options to the automatically sign this for Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0-pre3) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0-pre3.txt` and `manifest-v6.1.0-pre3.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.1.0-pre3.txt.sig manifest-v6.1.0-pre3.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.1.0-pre3.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.

## Amber 6.1.0-pre2 - Better layout when connecting a new app - Fix some reported crashes - Fix signer dialog not closing after accepting a bunker request - Show name and npub when showing your account - Add a select/deselect all option in the permissions screen when connecting a new app - Show a invalid request screen when receiving a invalid request - Preview missing translation report before sending it - Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once) - Some optimizations when accepting/rejecting intent requests - Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications - Added a option to disable the service start on boot - Only start the profile subscription for the current account - Always return hex key when logging in to an app to comply with nip 55 - Added a close button in the empty requests screen - Added loading state to the report screens - Support for beta releases for the auto updater - Add a reset button for bunkers - Fix a connection issue when connecting to a new bunker by @Alex Gleason - Fix app starting on boot when not enabled Download it with [Zapstore](

Zapstore

App Details — Zapstore

The open app store where users meet builders. Curated by communities. Android apps.

[Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0-pre2) If you like my work consider making a [donation](https://greenart7c3.com) ## 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: ``` bash gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D ``` Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0-pre2.txt` and `manifest-v6.1.0-pre2.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v6.1.0-pre2.txt.sig manifest-v6.1.0-pre2.txt ``` You should see the following if the verification was successful: ``` bash 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: ``` bash cat manifest-v6.1.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.