aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorNikolaus Rath <Nikolaus@rath.org>2023-07-05 18:58:05 +0100
committerNikolaus Rath <Nikolaus@rath.org>2023-08-08 11:11:55 +0100
commit0d830af6b8441b9fc52cf5e2c6f815b2cf178d8f (patch)
tree524a43076166f22daf57e64337916989818388ef /README.md
parent7b9e7eeec6c43a62ab1e02dfb6542e6bfb7f72dc (diff)
downloadlibfuse-0d830af6b8441b9fc52cf5e2c6f815b2cf178d8f.tar.gz
Don't attempt to put signify signature into gz header
This is currently buggy, cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042837
Diffstat (limited to 'README.md')
-rw-r--r--README.md11
1 files changed, 5 insertions, 6 deletions
diff --git a/README.md b/README.md
index cf76978..6855cef 100644
--- a/README.md
+++ b/README.md
@@ -49,13 +49,12 @@ Supported Platforms
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 downloading the tarball, verify
-it using [signify])(https://www.openbsd.org/papers/bsdcan-signify.html):
+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 downloading the tarball and `.sig` file, 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
+ signify -V -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