I think it would be a mistake to change 'message.txt' etc (which are
obviously filenames) to just 'message' which could be misinterpreted.
I'm neutral on the other changes.
--
Sent from a phone, apologies for poor formatting.
On 24 February 2019 21:10:08 Matthias Schmidt <open...@xosc.org> wrote:
Hi,
while looking at signify's man page I noticed that the names of the
arguments in the EXAMPLES section change (newkey.sec vs key.sec, etc).
The diff harmonizes the examples. It makes it easier to follow the examples.
Cheers
Matthias
diff --git signify.1 signify.1
index de3b433e3b0..9f7335352a2 100644
--- signify.1
+++ signify.1
@@ -153,13 +153,13 @@ The message file is too large.
.El
.Sh EXAMPLES
Create a new key pair:
-.Dl $ signify -G -p newkey.pub -s newkey.sec
+.Dl $ signify -G -p key.pub -s key.sec
.Pp
Sign a file, specifying a signature name:
-.Dl $ signify -S -s key.sec -m message.txt -x msg.sig
+.Dl $ signify -S -s key.sec -m message -x message.sig
.Pp
Verify a signature, using the default signature name:
-.Dl $ signify -V -p key.pub -m generalsorders.txt
+.Dl $ signify -V -p key.pub -m message
.Pp
Verify a release directory containing
.Pa SHA256.sig
@@ -175,7 +175,7 @@ $ signify -C -p /etc/signify/openbsd-65-base.pub -x
SHA256.sig bsd.rd
.Pp
Sign a gzip archive:
.Bd -literal -offset indent -compact
-$ signify -Sz -s key-arc.sec -m in.tgz -x out.tgz
+$ signify -Sz -s key.sec -m in.tgz -x out.tgz
.Ed
.Pp
Verify a gzip pipeline:
