projects
/
grml-crypt.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
Added tag 0.14 for changeset ac073acb1f10720f7fae334c424c8dacfcc577dd
[grml-crypt.git]
/
grml-crypt.8.txt
diff --git
a/grml-crypt.8.txt
b/grml-crypt.8.txt
index
b4c61b3
..
6cf20fd
100644
(file)
--- a/
grml-crypt.8.txt
+++ b/
grml-crypt.8.txt
@@
-5,18
+5,18
@@
Michael Gebetsroither <michael.geb@gmx.at>
NAME
----
NAME
----
-grml-crypt - Wrapper ar
r
ound cryptsetup/losetup/mkfs/mount
+grml-crypt - Wrapper around cryptsetup/losetup/mkfs/mount
SYNOPSIS
--------
SYNOPSIS
--------
-*grml-
vpn
* [OPTIONS] 'action' <device/file> '[mountpoint]'
+*grml-
crypt
* [OPTIONS] 'action' <device/file> '[mountpoint]'
DESCRIPTION
-----------
*grml-crypt* is a program that
DESCRIPTION
-----------
*grml-crypt* is a program that
-provides an easy wrapper ar
r
ound cryptsetup, mkfs, losetup and mount. You
+provides an easy wrapper around cryptsetup, mkfs, losetup and mount. You
could create a loopback mountet crypted filesystem with only one command, but
grml-crypt works for normal devices also.
could create a loopback mountet crypted filesystem with only one command, but
grml-crypt works for normal devices also.
@@
-25,12
+25,12
@@
ACTIONS
-------
*format <device/file> [mountpoint]*::
This command "formats" a device/file. If the second parameter is not a
-------
*format <device/file> [mountpoint]*::
This command "formats" a device/file. If the second parameter is not a
- blockdevice grml-cr
u
pt assumes that it should operate in file modus. If the
- file does not al
l
ready exist it will be created with the given size. The
+ blockdevice grml-cr
y
pt assumes that it should operate in file modus. If the
+ file does not already exist it will be created with the given size. The
first 2MB of a device (luks header) are initialised with /dev/urandom, the
other space is initialised with the given initialisation. If grml-crypt is
in file modus the first 2MB of the loop file are also initialised with
first 2MB of a device (luks header) are initialised with /dev/urandom, the
other space is initialised with the given initialisation. If grml-crypt is
in file modus the first 2MB of the loop file are also initialised with
- /dev/urandom except where the file al
l
ready exist (with -f vor
+ /dev/urandom except where the file already exist (with -f vor
overwriting). Commands: [losetup], dd, cryptsetup luksFormat, cryptsetup
luksOpen, [dd], mkfs, [mount]
overwriting). Commands: [losetup], dd, cryptsetup luksFormat, cryptsetup
luksOpen, [dd], mkfs, [mount]
@@
-83,7
+83,7
@@
Show what is going on (more v => more out).
itself (eg. xfs needs a minimum of 4096 blocks).
*-m*::
itself (eg. xfs needs a minimum of 4096 blocks).
*-m*::
- Additional arguments passed through to mount. Could be like
'-o noatime'
.
+ Additional arguments passed through to mount. Could be like
"'-o noatime'"
.
CRYPTSETUP FORMAT OPTIONS
CRYPTSETUP FORMAT OPTIONS
@@
-110,7
+110,7
@@
INITIALISATION MODES
*Default/Secure mode (no -o or -z given)*::
This mode is the default. It should be quite secure. The device/file gets
*Default/Secure mode (no -o or -z given)*::
This mode is the default. It should be quite secure. The device/file gets
- initialised with /dev/urandom. Except with an al
l
ready existing file and
+ initialised with /dev/urandom. Except with an already existing file and
-f, where NO initialisation will be done (all other modes behave as usual).
*Optimized secure mode (-o)*::
-f, where NO initialisation will be done (all other modes behave as usual).
*Optimized secure mode (-o)*::