X-Git-Url: https://git.distorted.org.uk/~mdw/udpkey/blobdiff_plain/8d34ef00d95f1a74acc20616aa77c664dba62ba3..5c7e9df83788dcb1f8f57d88ce0a945fe44b4ca0:/udpkey.1

diff --git a/udpkey.1 b/udpkey.1
index 272905f..1371567 100644
--- a/udpkey.1
+++ b/udpkey.1
@@ -1,3 +1,4 @@
+'\" e
 .\" -*-nroff-*-
 .EQ
 delim $$
@@ -124,9 +125,9 @@ For each
 of the form
 .IP
 .IB address : port \c
-.IB [ = \c
+.RB [ = \c
 .IR tag ] \c
-.IB [ # \c
+.RB [ # \c
 .IR hash ] \c
 .BR ; ...
 .PP
@@ -207,7 +208,7 @@ The
 program uses the Catacomb keyring format to store its cryptographic
 keys: see
 .BR keyring (5)
-for the technical details.  Keys maybe generated and managed using the
+for the technical details.  Keys may be generated and managed using the
 .BR key (1)
 utility.
 .PP
@@ -262,8 +263,8 @@ The default is
 .B mac
 The message authentication code used to ensure the integrity of the
 ciphertext, in the form
-.IB name / tagbits \fR.
-The default is to use HMAC with the chosen hash function, and truncate
+.IB name\fR[ / tagbits \fR].
+The defaults are to use HMAC with the chosen hash function, and truncate
 the tag to half of its original length.
 .PP
 Key fragments must contain only plain binary data: you can generate one
@@ -364,13 +365,7 @@ captured response.  Periodically rekeying the random number generator
 when high-quality entropy is available \(en serves to limit the exposure
 to responses captured since the last rekeying.
 .SH BUGS
-For some mysterious reason,
-.BR cryptsetup (8)
-initially rejects a key from
-.BR udpkey ;
-but when the relevant
-.B initramfs
-script retries, everything works.  I'm not sure what's going on here.
+None known.
 .SH SEE ALSO
 .BR key (1),
 .BR crypttab (5),