Package: signify-openbsd / 13-1

rename-manual.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
Description: Change manual references from "signify" to "signify-openbsd"
 The information contained in the manpage needs to match the function
 of the binary, including the renaming.
Forwarded: not-needed
Author: Riley Baird <BM-2cVqnDuYbAU5do2DfJTrN7ZbAJ246S4Xix@bitmessage.ch>
Last-Update: 2016-01-09
Index: build/signify.1
===================================================================
--- build.orig/signify.1
+++ build/signify.1
@@ -15,31 +15,31 @@
 .\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .Dd $Mdocdate: July 14 2015 $
-.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
 .Fl p Ar pubkey
 .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 e
 .Op Fl x Ar sigfile
 .Fl s Ar seckey
 .Fl m Ar message
-.Nm signify
+.Nm signify-openbsd
 .Fl V
 .Op Fl eq
 .Op Fl x Ar sigfile
@@ -121,7 +121,7 @@ so long as it does not exceed a single l
 .\" 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
@@ -136,31 +136,36 @@ 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-56-base.pub \-x SHA256.sig
+$ signify-openbsd \-C \-p /etc/signify/openbsd-56-base.pub \-x SHA256.sig
 Note that for non-OpenBSD operating systems, you will have to get the
 signing key yourself.
 .Ed
 .Pp
 Verify a bsd.rd before an upgrade:
 .Bd -literal -offset indent -compact
-$ signify \-C \-p /etc/signify/openbsd-56-base.pub \-x SHA256.sig bsd.rd
+$ signify-openbsd \-C \-p /etc/signify/openbsd-56-base.pub \-x SHA256.sig bsd.rd
 .Ed
 .Sh HISTORY
 The
 .Nm
 command first appeared in
-.Ox 5.5 .
+.Ox 5.5 ,
+but was renamed to
+.Nm signify-openbsd
+for Debian because another binary named
+.Nm signify
+already existed in Debian's repositories.
 .Sh AUTHORS
 .An Ted Unangst Aq Mt tedu@openbsd.org