aboutsummaryrefslogtreecommitdiff
path: root/system/signify
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 12:50:39 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:12 -0400
commit57f0f8f8a513d95c116bd866c6458a872d64ac58 (patch)
treed3773105d7cf233f9e54ed57c7db7e4d7194c613 /system/signify
parentafaa7cc21db7d03e2308861169a2bc00e4f1c225 (diff)
system/signify: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/signify')
-rw-r--r--system/signify/README14
1 files changed, 7 insertions, 7 deletions
diff --git a/system/signify/README b/system/signify/README
index 77a8b58724994..9ca66cf859c85 100644
--- a/system/signify/README
+++ b/system/signify/README
@@ -1,12 +1,12 @@
-OpenBSD tool to signs and verify signatures on files. Portable version.
+OpenBSD tool to sign and verify signatures on files. Portable version.
The signify utility creates and verifies cryptographic signatures.
A signature verifies the integrity of a message.
The key and signature files created by signify have the same format.
-The first line of the file is a free form text comment that may be edited,
-so long as it does not exceed a single line. Signature comments will be
-generated based on the name of the secret key used for signing.
-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.
+The first line of the file is a free form text comment that may
+be edited, so long as it does not exceed a single line. Signature
+comments will be generated based on the name of the secret key used
+for signing. 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.