Bump version to 6.5.1

This commit is contained in:
greenart7c3
2026-08-14 13:49:04 -03:00
parent 41a37aacdc
commit 16559c8e8e
4 changed files with 49 additions and 19 deletions
+7 -17
View File
@@ -1,21 +1,11 @@
# Changelog # Changelog
## Amber 6.5.0 ## Amber 6.5.1
- Fix relay-auth whitelist authorizing any requester (GHSA-vx4h-56qj-wcp7) - 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 NIP-46 freshness and replay protection (GHSA-h9fv-9247-3582) - Fix crash in EditPermission due to an invalid localKey
- 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](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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) Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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) If you like my work consider making a [donation](https://greenart7c3.com)
@@ -27,10 +17,10 @@ In order to verify the release, you'll need to have `gpg` or `gpg2` installed on
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D 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: 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 ``` bash
gpg --verify manifest-v6.5.0.txt.sig manifest-v6.5.0.txt gpg --verify manifest-v6.5.1.txt.sig manifest-v6.5.1.txt
``` ```
You should see the following if the verification was successful: You should see the following if the verification was successful:
@@ -44,7 +34,7 @@ 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: 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 ``` bash
cat manifest-v6.5.0.txt 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. 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.
+2 -2
View File
@@ -15,8 +15,8 @@ android {
defaultConfig { defaultConfig {
applicationId = "com.greenart7c3.nostrsigner" applicationId = "com.greenart7c3.nostrsigner"
minSdk = 26 minSdk = 26
versionCode = 199 versionCode = 200
versionName = "6.5.0" versionName = "6.5.1"
buildConfigField("boolean", "IS_FDROID_BUILD", "false") buildConfigField("boolean", "IS_FDROID_BUILD", "false")
+39
View File
@@ -0,0 +1,39 @@
# 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](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [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.
+1
View File
@@ -4,6 +4,7 @@ Release notes for Amber, one file per version (pre-releases included). The most
| Version | Changelog | | Version | Changelog |
|---------|-----------| |---------|-----------|
| 6.5.1 | [6.5.1.md](6.5.1.md) |
| 6.5.0 | [6.5.0.md](6.5.0.md) | | 6.5.0 | [6.5.0.md](6.5.0.md) |
| 6.4.0 | [6.4.0.md](6.4.0.md) | | 6.4.0 | [6.4.0.md](6.4.0.md) |
| 6.3.0 | [6.3.0.md](6.3.0.md) | | 6.3.0 | [6.3.0.md](6.3.0.md) |