Skip to content

Display and control your Android device

Document release signature verification

Romain Vimont19c4d0b4e9d2
diff --git a/README.md b/README.md
index 3eef0951..d784e746 100644
--- a/README.md
+++ b/README.md
@@ -165,6 +165,7 @@ documented in the following pages:
- [Translations][wiki] (not necessarily up to date)
- [Build instructions](doc/build.md)
- [Developers](doc/develop.md)
+ - [Verify release signatures](doc/verify-release.md)
[wiki]: https://github.com/Genymobile/scrcpy/wiki
diff --git a/doc/verify-release.md b/doc/verify-release.md
new file mode 100644
index 00000000..a7f2a4d3
--- /dev/null
+++ b/doc/verify-release.md
@@ -0,0 +1,76 @@
+# Verify release signatures
+
+All releases are signed using Romain Vimont's [GPG key] ([raw]):
+
+[GPG key]: https://blog.rom1v.com/about/#gpg-key
+[raw]: https://blog.rom1v.com/keys/rom1v.asc
+
+```console
+$ curl -s https://blog.rom1v.com/keys/rom1v.asc | gpg --show-keys --with-fingerprint --with-subkey-fingerprints
+pub rsa4096 2021-03-15 [C]
+ 4569 58E8 5A18 5DD5 C2D1 E4E8 0C82 2B29 8461 FA03
+uid Romain Vimont <[email protected]>
+sub rsa4096 2021-03-15 [S] [expires: 2030-05-14]
+ E39E 2DE6 A55F 5AA6 D8EF B79A CA01 F46F 1868 3B3D
+sub rsa4096 2021-03-15 [E] [expires: 2030-05-14]
+ 2C86 255E 6D65 241D 8248 F1B3 F212 10AE 292B 63D1
+sub rsa4096 2021-03-15 [A] [expires: 2030-05-14]
+ 1782 0F23 CB1D 1921 5572 6FAD 0F0B 58E1 3784 09AA
+```
+
+## Import the key
+
+```bash
+# import the key
+curl -s https://blog.rom1v.com/keys/rom1v.asc | gpg --import
+
+# alternatively, the key can be retrieved from a key server
+gpg --keyserver hkps://keys.openpgp.org --recv-keys 456958E85A185DD5C2D1E4E80C822B298461FA03
+
+# verify the key fingerprint
+gpg --fingerprint 456958E85A185DD5C2D1E4E80C822B298461FA03
+```
+
+## Verify releases
+
+For each release, two additional files are published:
+ - `SHA256SUMS.txt`: the SHA-256 checksums
+ - `SHA256SUMS.txt.asc`: the signature of the checksums
+
+To verify a release, two steps are required.
+
+First, verify the signature of the checksums:
+
+```bash
+# SHA256SUMS.txt must be in the same directory
+gpg --verify SHA256SUMS.txt.asc
+```
+
+For example:
+
+```console
+$ gpg --verify SHA256SUMS.txt.asc
+gpg: assuming signed data in 'SHA256SUMS.txt'
+gpg: Signature made Wed Dec 17 20:16:30 2025 CET
+gpg: using RSA key E39E2DE6A55F5AA6D8EFB79ACA01F46F18683B3D
+gpg: Good signature from "Romain Vimont <[email protected]>" [ultimate]
+```
+
+Then verify the release checksums:
+
+```bash
+# the release files must be in the same directory
+shasum -a 256 -c SHA256SUMS.txt
+```
+
+For example:
+
+```console
+$ shasum -a 256 -c SHA256SUMS.txt
+scrcpy-server-v3.3.4: OK
+scrcpy-linux-x86_64-v3.3.4.tar.gz: OK
+scrcpy-win32-v3.3.4.zip: OK
+scrcpy-win64-v3.3.4.zip: OK
+scrcpy-macos-aarch64-v3.3.4.tar.gz: OK
+scrcpy-macos-x86_64-v3.3.4.tar.gz: OK
+```