Package: signify-openbsd / 30-2

0002-replace-signify-with-signify-openbsd.patch Patch series | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
From: Tomasz Buchert <tomasz@debian.org>
Date: Wed, 6 Nov 2019 21:33:14 +0100
Subject: replace signify with signify-openbsd

---
 signify.1 | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/signify.1 b/signify.1
index a731b4a..7603258 100644
--- a/signify.1
+++ b/signify.1
@@ -1,4 +1,4 @@
-.\" $OpenBSD: signify.1,v 1.51 2020/08/31 16:08:28 deraadt Exp $
+.\" $OpenBSD: signify-openbsd.1,v 1.51 2020/08/31 16:08:28 deraadt Exp $
 .\"
 .\"Copyright (c) 2013 Marc Espie <espie@openbsd.org>
 .\"Copyright (c) 2013 Ted Unangst <tedu@openbsd.org>
@@ -15,32 +15,32 @@
 .\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .Dd $Mdocdate: August 31 2020 $
-.Dt SIGNIFY 1
+.Dt SIGNIFY-OPENBSD 1
 .Os
 .Sh NAME
-.Nm signify
+.Nm signify-openbsd
 .Nd cryptographically sign and verify files
 .Sh SYNOPSIS
-.Nm signify
+.Nm signify-openbsd
 .Fl C
 .Op Fl q
 .Op Fl p Ar pubkey
 .Op Fl t Ar keytype
 .Fl x Ar sigfile
 .Op Ar
-.Nm signify
+.Nm signify-openbsd
 .Fl G
 .Op Fl n
 .Op Fl c Ar comment
 .Fl p Ar pubkey
 .Fl s Ar seckey
-.Nm signify
+.Nm signify-openbsd
 .Fl S
 .Op Fl enz
 .Op Fl x Ar sigfile
 .Fl s Ar seckey
 .Fl m Ar message
-.Nm signify
+.Nm signify-openbsd
 .Fl V
 .Op Fl eqz
 .Op Fl p Ar pubkey
@@ -144,7 +144,7 @@ This comment can then be used as a hint for the name of the public key
 when verifying.
 The second line of the file is the actual key or signature base64 encoded.
 .Sh EXIT STATUS
-.Ex -std signify
+.Ex -std signify-openbsd
 It may fail because of one of the following reasons:
 .Pp
 .Bl -bullet -compact
@@ -159,34 +159,34 @@ 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-openbsd -G -p newkey.pub -s newkey.sec
 .Pp
 Sign a file, specifying a signature name:
-.Dl $ signify -S -s key.sec -m message.txt -x msg.sig
+.Dl $ signify-openbsd -S -s key.sec -m message.txt -x msg.sig
 .Pp
 Verify a signature, using the default signature name:
-.Dl $ signify -V -p key.pub -m generalsorders.txt
+.Dl $ signify-openbsd -V -p key.pub -m generalsorders.txt
 .Pp
 Verify a release directory containing
 .Pa SHA256.sig
 and a full set of release files:
 .Bd -literal -offset indent -compact
-$ signify -C -p /etc/signify/openbsd-69-base.pub -x SHA256.sig
+$ signify-openbsd -C -p /etc/signify/openbsd-69-base.pub -x SHA256.sig
 .Ed
 .Pp
 Verify a bsd.rd before an upgrade:
 .Bd -literal -offset indent -compact
-$ signify -C -p /etc/signify/openbsd-69-base.pub -x SHA256.sig bsd.rd
+$ signify-openbsd -C -p /etc/signify/openbsd-69-base.pub -x SHA256.sig bsd.rd
 .Ed
 .Pp
 Sign a gzip archive:
 .Bd -literal -offset indent -compact
-$ signify -Sz -s key-arc.sec -m in.tgz -x out.tgz
+$ signify-openbsd -Sz -s key-arc.sec -m in.tgz -x out.tgz
 .Ed
 .Pp
 Verify a gzip pipeline:
 .Bd -literal -offset indent -compact
-$ ftp url | signify -Vz -t arc | tar ztf -
+$ ftp url | signify-openbsd -Vz -t arc | tar ztf -
 .Ed
 .Sh SEE ALSO
 .Xr fw_update 1 ,