Amber

Amber's avatar
Amber
amber@greenart7c3.com
npub1am3e...xrv7
Amber is a nostr event signer for Android. It allows users to keep their nsec segregated in a single, dedicated app. The goal of Amber is to have your smartphone act as a NIP-46 signing device without any need for servers or additional hardware. "Private keys should be exposed to as few systems as possible as each system adds to the attack surface," as the rationale of said NIP states. In addition to native apps, Amber aims to support all current nostr web applications without requiring any extensions or web servers.
## Amber 4.0.5 - Implemented pagination in the application, logs and activities screen - Fix database size calculation inside the settings screen - Optimize `getSavedRelays` to query unique relay lists directly - Remove application name pre-loading in `IncomingRequestScreen` - Use direct `DELETE` queries for clearing old logs and history instead of iterative deletion Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](
GitHub
GitHub - ImranR98/Obtainium: Get Android app updates straight from the source.
Get Android app updates straight from the source. Contribute to ImranR98/Obtainium development by creating an account on GitHub.
), [f-droid](
Amber | F-Droid - Free and Open Source Android App Repository
Nostr event signer for Android
) or download it directly in the [releases page](
GitHub
Release Release v4.0.5 · greenart7c3/Amber
Amber 4.0.5 Implemented pagination in the application, logs and activities screen Fix database size calculation inside the settings screen Optimiz...
) If you like my work consider making a [donation](
greenart7c3
) ## 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-v4.0.5.txt` and `manifest-v4.0.5.txt.sig` are in the current directory) with: ``` bash gpg --verify manifest-v4.0.5.txt.sig manifest-v4.0.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-v4.0.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.