diff options
| author | saturneric <[email protected]> | 2026-08-14 23:48:12 +0200 |
|---|---|---|
| committer | saturneric <[email protected]> | 2026-08-14 23:48:12 +0200 |
| commit | 1da013869c0dffe7666d8d5cd18620cc82965d56 (patch) | |
| tree | 52dbff5e83351332b2ddf492d7eadc3308445da4 /src/content/docs/appendix/code-binary-verify.md | |
| parent | feat(site): add redirect from setup-dev-env to contribute (diff) | |
| download | manual-1da013869c0dffe7666d8d5cd18620cc82965d56.tar.gz manual-1da013869c0dffe7666d8d5cd18620cc82965d56.zip | |
docs(manual): convert inline URLs to reference style
- convert inline image URLs to reference-style [img-*] and add refs
- convert inline external links to reference labels and add refs
- normalize link names across many docs for consistency
- reword translate-interface guide for clarity and brevity
- fix algorithms table formatting and add wiki/rfc references
Diffstat (limited to 'src/content/docs/appendix/code-binary-verify.md')
| -rw-r--r-- | src/content/docs/appendix/code-binary-verify.md | 21 |
1 files changed, 14 insertions, 7 deletions
diff --git a/src/content/docs/appendix/code-binary-verify.md b/src/content/docs/appendix/code-binary-verify.md index e83fd9d..3e5ef1c 100644 --- a/src/content/docs/appendix/code-binary-verify.md +++ b/src/content/docs/appendix/code-binary-verify.md @@ -34,11 +34,11 @@ Each system also adds its own check on top: ### Windows All programs and installers are signed with a -[Certum](https://www.certum.eu/en/certum-by-asseco/) code signing certificate. +[Certum][certum] code signing certificate. Windows checks this itself. You can also look at it yourself: right-click the file, open Properties, and look at Digital Signatures. - +![][img-1] ### macOS @@ -46,7 +46,7 @@ The app is signed with an Apple developer certificate and passes Apple's notarization check. macOS verifies both automatically the first time you open the app. If the app had been changed, macOS would refuse to start it. - +![][img-2] ### Linux @@ -54,7 +54,7 @@ The AppImage comes with a `.sig` file, like the other packages. Check it with GPG before you run the app. Flatpak and other formats bring their own signature and sandbox systems on top. - +![][img-3] ## Check Inside the App @@ -63,13 +63,13 @@ and the exact branch and commit hash of the source code this copy was built from. That lets you match your running app to a specific point in the public code history. - +![][img-4] ## The Signing Key All commits and release packages are signed with the maintainer's OpenPGP key. The key and its fingerprint are published at -[bktus.com/openpgp](https://bktus.com/openpgp/). Get the key there, check the +[bktus.com/openpgp][bktus-openpgp]. Get the key there, check the fingerprint, and use it to verify the `.sig` file that comes with each release. ## When the Stakes Are Very High @@ -86,7 +86,7 @@ If you are in that situation, this is the path: 1. **Get the source, not a binary.** Clone the repository and check out an official release tag. Verify the tag's GPG signature with the maintainer's - key from [bktus.com/openpgp](https://bktus.com/openpgp/). + key from [bktus.com/openpgp][bktus-openpgp]. 2. **Read before you build.** Review the code yourself, or have someone you trust review it. Pay attention to the build scripts too, not only the app code. @@ -102,3 +102,10 @@ Build instructions are in the costs real time and skill. That is the honest price of not having to trust anyone else's build. + +[certum]: https://www.certum.eu/en/certum-by-asseco/ +[img-1]: https://image.cdn.bktus.com/i/2025/06/25/2eb0e5a1ff970b6d97ed38f18b45476c9aad6ee7.webp +[img-2]: https://image.cdn.bktus.com/i/2025/06/24/cbc3a2ec86515bf5882d1249179e5e06053ada5f.webp +[img-3]: https://image.cdn.bktus.com/i/2025/06/24/690c6b534ab54130dfa100f85a8cc299a0223ff5.webp +[img-4]: https://image.cdn.bktus.com/i/2025/06/24/fe75a2c041c9e5a7823d0c4d8820bf35501117cd.webp +[bktus-openpgp]: https://bktus.com/openpgp/ |