From 6e814f4fb29db0cba9c0a6620a0f38ca7fdcecfb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Th=C3=A9o=20FIDRY?= <5175937+theofidry@users.noreply.github.com> Date: Mon, 30 Oct 2023 22:16:28 +0100 Subject: [PATCH] doc: Fix various links (#1133) --- doc/installation.md | 2 +- doc/phar-signing.md | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/installation.md b/doc/installation.md index 290301d40..f850d9994 100644 --- a/doc/installation.md +++ b/doc/installation.md @@ -69,7 +69,7 @@ $ brew upgrade box ## GitHub -You may download the Box PHAR directly from the [GitHub release][github-release] directly. +You may download the Box PHAR directly from the [GitHub release][releases] directly. You should however beware that it is not as secure as downloading it from the other mediums. Hence, it is recommended to check the signature when doing so: diff --git a/doc/phar-signing.md b/doc/phar-signing.md index c5d6b9ab8..616684a7f 100644 --- a/doc/phar-signing.md +++ b/doc/phar-signing.md @@ -372,11 +372,12 @@ A more complete real-life example can be found in the [Box release workflow][box
Credits: + - [Andreas Heigl, January 19, 2017, _Encrypt a build-result – automaticaly_](https://andreas.heigl.org/2017/01/19/encrypt-a-build-result-automaticaly/) - [Arne Blankerts](https://github.com/theseer) - [Jeff Channell, July 13, 2017, _Code Injection in Signed PHP Archives (Phar)_](https://blog.sucuri.net/2017/07/code-injection-in-phar-signed-php-archives.html) -[box-release-workflow]: https://github.com/box-project/box/blob/main/.github/workflows/release.yaml +[box-release-workflow]: ./../.github/workflows/release.yaml [keys.openpgp.org]: https://keys.openpgp.org/about [github-environment-secrets]: https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions [phive]: https://phar.io/