laantungir/Amber
1
0
Fork 0
mirror of https://github.com/greenart7c3/Amber.git synced 2026-10-05 10:58:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Bump version to 6.6.5

Browse Source
This commit is contained in:
greenart7c3
2026-09-21 11:09:01 -03:00
parent 1e494a21a3
commit b4c9e26e22
6 changed files with 131 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+7 -10
View File
@@ -1,14 +1,11 @@
# Changelog
## Amber 6.6.4
## Amber 6.6.5
- Fix a clearnet leak for Tor users during the startup settings race: profile fetches and boot-time network callbacks could dial relays directly before the Tor setting finished loading
- Reduce background battery drain: the connectivity safety-net tick now runs every 5 minutes instead of every 30 seconds, and the built-in Tor daemon gives up after a bounded bootstrap window instead of restarting forever (a notification lets you retry)
- Relay connections now recover automatically when the built-in Tor daemon comes back, including after a manual Tor restart
- Sync the relay WebSocket layer with upstream quartz: relay-initiated CLOSE frames are answered so sockets close promptly instead of lingering half-open until the ping timeout
- Add sign-event labels for the Armada event kinds (presence and typing indicators, NIP-29 group management, Buzz forum kinds, webxdc app data, and more)
- 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](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.6.4)
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.6.5)
If you like my work consider making a [donation](https://greenart7c3.com)
@@ -20,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
```
Once you have his PGP key you can verify the release (assuming `manifest-v6.6.4.txt` and `manifest-v6.6.4.txt.sig` are in the current directory) with:
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.4.txt.sig manifest-v6.6.4.txt
gpg --verify manifest-v6.6.5.txt.sig manifest-v6.6.5.txt
```
You should see the following if the verification was successful:
@@ -37,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:
``` bash
cat manifest-v6.6.4.txt
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.
app/build.gradle.kts
+2 -2
View File
@@ -15,8 +15,8 @@ android {
defaultConfig {
applicationId = "com.greenart7c3.nostrsigner"
minSdk = 26
versionCode = 206
versionName = "6.6.4"
versionCode = 207
versionName = "6.6.5"
buildConfigField("boolean", "IS_FDROID_BUILD", "false")
docs/changelogs/6.6.3.md
+40
View File
@@ -0,0 +1,40 @@
# 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](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.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.
docs/changelogs/6.6.4.md
+41
View File
@@ -0,0 +1,41 @@
# Amber 6.6.4
- Fix a clearnet leak for Tor users during the startup settings race: profile fetches and boot-time network callbacks could dial relays directly before the Tor setting finished loading
- Reduce background battery drain: the connectivity safety-net tick now runs every 5 minutes instead of every 30 seconds, and the built-in Tor daemon gives up after a bounded bootstrap window instead of restarting forever (a notification lets you retry)
- Relay connections now recover automatically when the built-in Tor daemon comes back, including after a manual Tor restart
- Sync the relay WebSocket layer with upstream quartz: relay-initiated CLOSE frames are answered so sockets close promptly instead of lingering half-open until the ping timeout
- Add sign-event labels for the Armada event kinds (presence and typing indicators, NIP-29 group management, Buzz forum kinds, webxdc app data, and more)
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.6.4)
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.4.txt` and `manifest-v6.6.4.txt.sig` are in the current directory) with:
``` bash
gpg --verify manifest-v6.6.4.txt.sig manifest-v6.6.4.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.4.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.
docs/changelogs/6.6.5.md
+38
View File
@@ -0,0 +1,38 @@
# 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](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.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.
docs/changelogs/README.md
+3
View File
@@ -4,6 +4,9 @@ Release notes for Amber, one file per version (pre-releases included). The most
| Version | Changelog |
|---------|-----------|
| 6.6.5 | [6.6.5.md](6.6.5.md) |
| 6.6.4 | [6.6.4.md](6.6.4.md) |
| 6.6.3 | [6.6.3.md](6.6.3.md) |
| 6.6.2 | [6.6.2.md](6.6.2.md) |
| 6.6.1 | [6.6.1.md](6.6.1.md) |
| 6.6.0 | [6.6.0.md](6.6.0.md) |