greenart7c3 on Nostr: ## Amber 2.0.0 - New sign keys, to use this version you will need to first backup ...
#
- New sign keys, to use this version you will need to first backup your accounts, uninstall the old version and install the new version
- When you not configured a notification type Amber will ask you to configure and default to direct connection to relays
- Check if is a valid relay before adding it when changing the default relays or adding a relay to a application
Download it with zap.store, 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-v2.0.0.txt and manifest-v2.0.0.txt.sig are in the current directory) with:
gpg --verify manifest-v2.0.0.txt.sig manifest-v2.0.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-v2.0.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.
Published at
2024-09-13 12:00:20Event JSON
{
"id": "bf5cce72e6fbb65dfc958df99a92ed00c825101ebfff10745e78018521ee7c68",
"pubkey": "7579076d9aff0a4cfdefa7e2045f2486c7e5d8bc63bfc6b45397233e1bbfcb19",
"created_at": 1726228820,
"kind": 30023,
"tags": [
[
"client",
"Yakihonne",
"31990:20986fb83e775d96d188ca5c9df10ce6d613e0eb7e5768a0f0b12b37cdac21b3:1700732875747"
],
[
"published_at",
"1726228820"
],
[
"d",
"fYjK0FKQ7YU4r5Lt6frP3"
],
[
"image",
""
],
[
"title",
"Amber 2.0.0"
],
[
"summary",
""
],
[
"zap",
"7579076d9aff0a4cfdefa7e2045f2486c7e5d8bc63bfc6b45397233e1bbfcb19",
"",
"100"
]
],
"content": "## Amber 2.0.0\n\n- New sign keys, to use this version you will need to first backup your accounts, uninstall the old version and install the new version\n- When you not configured a notification type Amber will ask you to configure and default to direct connection to relays\n- Check if is a valid relay before adding it when changing the default relays or adding a relay to a application\n\nDownload it with [zap.store](https://zap.store/download), [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/v2.0.0)\n\nIf you like my work consider making a [donation](https://greenart7c3.com)\n\n## Verifying the release\n\nIn 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:\n\n``` bash\ngpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D\n```\n\nOnce you have his PGP key you can verify the release (assuming `manifest-v2.0.0.txt` and `manifest-v2.0.0.txt.sig` are in the current directory) with:\n\n``` bash\ngpg --verify manifest-v2.0.0.txt.sig manifest-v2.0.0.txt\n```\n\nYou should see the following if the verification was successful:\n\n``` bash\ngpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03\ngpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D\ngpg: Good signature from \"greenart7c3 \u003cgreenart7c3@proton.me\u003e\"\n```\n\nThat 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:\n\n``` bash\ncat manifest-v2.0.0.txt\n```\n\nOne can use the `shasum -a 256 \u003cfile name here\u003e` 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.",
"sig": "202386a075d5ee742dc1a2f0b0722a940ce6875097891be4a499b86c90bf2f628075600af194ea6638515d06bbc7bbf7a372ee58ebcc253348d3e3298bc9932c"
}
