tomb

commit 4b1afb4fab83984b8fb4b3c27c6b5ccabdce93d5
parent b9f555b5fedc33cc5a27d9806d935cf28736135c
Author: Jaromil <jaromil@dyne.org>
Date:   Thu, 22 Dec 2016 20:46:40 +0100

documentation on direct use of images as keys

as mentioned in #225 now the manual mentions using jpeg images
directly as arguments to -k on open commands.

Diffstat:
M
doc/tomb.1
 | 
13
+++++++------

1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/doc/tomb.1 b/doc/tomb.1
@@ -64,12 +64,13 @@ LUKS and Ext4), then set the key in its first LUKS slot.
 
 .B
 .IP "open"
-Opens an existing \fI.tomb\fR (first argument) using a key (\fI-k\fR),
-if a second argument is given it will indicate the \fImountpoint\fR
-where the tomb should be made accessible, else the tomb is mounted in
-a directory inside /media (if not available it uses /run/media/$USER).
-The option \fI-o\fR can be used to pass mount(8) options
-(default: rw,noatime,nodev).
+Opens an existing \fI.tomb\fR (first argument) using a key (\fI-k\fR)
+which can also be an \fIjpeg image\fR (see
+\fIbury\fR/\fIexhume\fR). If a second argument is given it will
+indicate the \fImountpoint\fR where the tomb should be made
+accessible, else the tomb is mounted in a directory inside /media (if
+not available it uses /run/media/$USER).  The option \fI-o\fR can be
+used to pass mount(8) options (default: rw,noatime,nodev).
 
 .B
 .IP "list"