mirror of
https://github.com/greenart7c3/Amber.git
synced 2026-10-05 10:58:23 +00:00
Claude
d48491cf7a
Add one file per GitHub release from 0.0.1 through 6.1.0-pre3, including pre-releases (185 files), with release bodies kept verbatim. Releases published without notes get a placeholder line. Regenerate the README index to list all 190 versions newest first. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JnvVcrZbefZviFqfG8bgPU
39 lines
2.0 KiB
Markdown
39 lines
2.0 KiB
Markdown
# Amber 2.0.5
|
|
|
|
- If you are coming from version 1.3.7 or lower you will need to first backup your accounts, uninstall the old version and install the new version
|
|
- Fix nip 04 decryption for web applications
|
|
|
|
Download 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.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-v2.0.5.txt` and `manifest-v2.0.5.txt.sig` are in the current directory) with:
|
|
|
|
``` bash
|
|
gpg --verify manifest-v2.0.5.txt.sig manifest-v2.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-v2.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.
|