NAME
----
-grml-crypt - Wrapper arround cryptsetup/losetup/mkfs/mount
+grml-crypt - Wrapper around cryptsetup/losetup/mkfs/mount
SYNOPSIS
--------
-*grml-vpn* [OPTIONS] 'action' <device/file> '[mountpoint]'
+*grml-crypt* [OPTIONS] 'action' <device/file> '[mountpoint]'
DESCRIPTION
-----------
*grml-crypt* is a program that
-provides an easy wrapper arround cryptsetup, mkfs, losetup and mount. You
-could create a loopback mountet crypted filesystem with only one command, but
+provides an easy wrapper around cryptsetup, mkfs, losetup and mount. You
+could create a loopback mounted crypted filesystem with only one command, but
grml-crypt works for normal devices also.
-------
*format <device/file> [mountpoint]*::
This command "formats" a device/file. If the second parameter is not a
- blockdevice grml-crupt assumes that it should operate in file modus. If the
- file does not allready exist it will be created with the given size. The
+ blockdevice grml-crypt 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
- /dev/urandom except where the file allready 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]
*start <device/file> <mountpoint>*::
- This command starts a encrypted device/file and mounts it to the given
+ This command starts an encrypted device/file and mounts it to the given
mountpoint. Commands: [losetup], cryptsetup luksOpen, mount
*stop <mountpoint>*::
- This command stops a encrypted filesystem mountet at mountpoint. Even the
+ This command stops an encrypted filesystem mounted at mountpoint. Even the
loopdevice gets destroyed with this command. Commands: mount, dmsetup info,
cryptsetup status, umount, cryptsetup luksClose, [losetup -d]
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
*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 allready 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)*::