aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorNikolaus Rath <Nikolaus@rath.org>2023-07-05 11:03:07 +0100
committerNikolaus Rath <Nikolaus@rath.org>2023-07-05 11:25:27 +0100
commitd888c305970d73e9ca75e90b7705183299b36b04 (patch)
treeb42a4ad816c0986d2046301bf64022aa34e2c418 /README.md
parenta98add6e49cbee59a377362b5e2b952904f9294e (diff)
downloadlibfuse-d888c305970d73e9ca75e90b7705183299b36b04.tar.gz
Use signify to sign releases.
Diffstat (limited to 'README.md')
-rw-r--r--README.md15
1 files changed, 13 insertions, 2 deletions
diff --git a/README.md b/README.md
index 1b02149..cf76978 100644
--- a/README.md
+++ b/README.md
@@ -52,9 +52,20 @@ Installation
You can download libfuse from
https://github.com/libfuse/libfuse/releases. To build and install, you
must use [Meson](http://mesonbuild.com/) and
-[Ninja](https://ninja-build.org). After extracting the libfuse
-tarball, create a (temporary) build directory and run Meson:
+[Ninja](https://ninja-build.org). After downloading the tarball, verify
+it using [signify])(https://www.openbsd.org/papers/bsdcan-signify.html):
+ signify -V -z -m fuse-X.Y.Z.tar.gz -p fuse-X.Y.pub
+
+The `fuse-X.Y.pub` file contains the signing key and needs to be obtained from a
+trustworthy source. Each libfuse release contains the signing key for the release after it
+in the `signify` directory, so you only need to manually acquire this file once when you
+install libfuse for the first time.
+
+After you have validated the tarball, extract it, create a (temporary) build directory and
+run Meson:
+
+ $ tar xzf fuse-X.Y.Z.tar.gz; cd fuse-X.Y.Z
$ mkdir build; cd build
$ meson setup ..