blog: update v6.3 release post (#5733)

* blog: update v6.3 release post

* update post, server page

* update

* headers
This commit is contained in:
Evgeny 2025-03-08 23:28:33 +00:00 committed by GitHub
parent 3188d9f087
commit 9dfa68bf57
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
3 changed files with 163 additions and 12 deletions

View file

@ -15,6 +15,7 @@ revision: 12.10.2024
- [systemd service](#systemd-service) with [installation script](#installation-script) or [manually](#manual-deployment)
- [docker container](#docker-container)
- [Linode marketplace](#linode-marketplace)
- [Verifying server binaries]
- [Configuration](#configuration)
- [Interactively](#interactively)
- [Via command line options](#via-command-line-options)
@ -32,6 +33,7 @@ revision: 12.10.2024
- [Systemd commands](#systemd-commands)
- [Control port](#control-port)
- [Daily statistics](#daily-statistics)
- [Reproduce builds](#reproduce-builds)
- [Updating your SMP server](#updating-your-smp-server)
- [Configuring the app to use the server](#configuring-the-app-to-use-the-server)
@ -515,6 +517,28 @@ This configuration allows you to retain the ability to manage 80 and 443 ports y
You can deploy smp-server upon creating new Linode VM. Please refer to: [Linode Marketplace](https://www.linode.com/marketplace/apps/simplex-chat/simplex-chat/)
## Verifying server binaries
Starting from v6.3 server builds are [reproducible](#reproduce-builds).
That also allows us to sign server releases, confirming the integrity of GitHub builds.
To verify server binaries after you downloaded them:
1. Download `_sha256sums` (hashes of all server binaries) and `_sha256sums.asc` (signature).
2. Download our key FB44AF81A45BDE327319797C85107E357D4A17FC from [openpgp.org](https://keys.openpgp.org/search?q=chat%40simplex.chat)
3. Import the key with `gpg --import FB44AF81A45BDE327319797C85107E357D4A17FC`. Key filename should be the same as its fingerprint, but please change it if necessary.
4. Run `gpg --verify --trusted-key _sha256sums.asc _sha256sums`. It should print:
> Good signature from "SimpleX Chat <chat@simplex.chat>"
5. Compute the hashes of the binaries you plan to use with `shu256sum <file>` or with `openssl sha256 <file>` and compare them with the hashes in the file `_sha256sums` - they must be the same.
That is it - you now verified authenticity of our GitHub server binaries.
## Configuration
To see which options are available, execute `smp-server` without flags: