|
| 1 | +### 2026-05-29: RNS 1.3.4 |
| 2 | + |
| 3 | +This release fixes a regression that could cause sub-optimal path selection under conditions where the same announce was received within a very short timespan on different interfaces, as well as a few other bugs and inefficiencies. |
| 4 | + |
| 5 | +**Changes** |
| 6 | +- Fixed regression in inbound announce de-duplication |
| 7 | +- Fixed missing check for shared instance type configuration conflict |
| 8 | +- Fixed superfluous path state configuration on new announce from new destinations |
| 9 | +- Improved cleanup of stale known destinations |
| 10 | +- Improved shared instance RPC handling |
| 11 | + |
| 12 | +**Verified Retrieval** |
| 13 | +You can retrieve and verify this release over Reticulum using the built-in `rngit release` utility. To retrieve only the installation `.whl` package, and the release manifest for future updates, you can use: |
| 14 | + |
| 15 | +```sh |
| 16 | +rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch "latest:rns-*.whl" --signer bc7291552be7a58f361522990465165c |
| 17 | +``` |
| 18 | + |
| 19 | +To download all artifacts, including the documentation and source archive, you can use the following command: |
| 20 | + |
| 21 | +```sh |
| 22 | +rngit release rns://7649a50d84610232d1416b41d2896aff/reticulum/reticulum fetch latest:all --signer bc7291552be7a58f361522990465165c |
| 23 | +``` |
| 24 | + |
| 25 | +**Release Signatures** |
| 26 | +Release artifacts include a signed `rsm` release manifest and `rsg` signature files that can be validated against the RNS release signing identity `<bc7291552be7a58f361522990465165c>` using `rngit` or `rnid`. To perform an offline verification of all release artifacts using a manifest: |
| 27 | + |
| 28 | +```sh |
| 29 | +rngit release rns_*.rsm verify --signer bc7291552be7a58f361522990465165c |
| 30 | +``` |
| 31 | + |
| 32 | +To verify release artifacts using individual `rsg` files, while also verifying the manifest itself, download the `rsm` and `rsg` signatures, make sure they are in the same folder as the release artifact, and run `rnid` signature verification with the release identity as the required signer: |
| 33 | + |
| 34 | +```sh |
| 35 | +rnid -i bc7291552be7a58f361522990465165c -V rns_*.rsm *.rsg |
| 36 | +``` |
| 37 | + |
| 38 | +The `rnid` utility will then verify the signatures, and display whether they are valid. If the signature cannot be verified, the release has been tampered with and should be discarded. |
| 39 | + |
| 40 | + |
1 | 41 | ### 2026-05-28: RNS 1.3.3 |
2 | 42 |
|
3 | 43 | This release fixes a regression in persistence of known destination on Windows. |
|
0 commit comments