Llewellyn/Tomb
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/Tomb.git synced 2024-11-05 21:07:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

documentation on direct use of images as keys

Browse Source 
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
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
doc/tomb.1
View File

@ -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"