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.
This commit is contained in:
Jaromil 2016-12-22 20:46:40 +01:00
parent b9f555b5fe
commit 4b1afb4fab

View File

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