mirror of
https://gitlab.com/cryptsetup/cryptsetup.git
synced 2025-12-13 20:00:08 +01:00
updated ASCII version also
git-svn-id: https://cryptsetup.googlecode.com/svn/trunk@701 36d66b0a-2a48-0410-832c-cd162a569da5
This commit is contained in:
9
FAQ
9
FAQ
@@ -49,6 +49,15 @@ A. Contributors
|
|||||||
installers after a complete backup of all LUKS containers has been
|
installers after a complete backup of all LUKS containers has been
|
||||||
made.
|
made.
|
||||||
|
|
||||||
|
NO WARNING ON NON-INERACTIVE FORMAT: If you feed cryptsetup from
|
||||||
|
STDIN (e.g. via GPG) on LUKS format, it does not give you the
|
||||||
|
warning that you are about to format (and e.g. will lose any
|
||||||
|
pre-existing LUKS container on the target), as it assumes it is
|
||||||
|
used form a script. In this scenario, the responsibility for
|
||||||
|
warning the user and possibly checking for an existing LUKS header
|
||||||
|
goes over to the script. This is a more general form of the
|
||||||
|
previous item.
|
||||||
|
|
||||||
LUKS PASSPHRASE IS NOT THE MASTER KEY: The LUKS passphrase is not
|
LUKS PASSPHRASE IS NOT THE MASTER KEY: The LUKS passphrase is not
|
||||||
used in deriving the master key. It is used in decrypting a master
|
used in deriving the master key. It is used in decrypting a master
|
||||||
key that is randomly selected on header creation. This means that
|
key that is randomly selected on header creation. This means that
|
||||||
|
|||||||
Reference in New Issue
Block a user