of the form
.IP
.IB address : port \c
-.IB [ = \c
+.RB [ = \c
.IR tag ] \c
-.IB [ # \c
+.RB [ # \c
.IR hash ] \c
.BR ; ...
.PP
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
.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
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),