X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=FAQ;h=3e316ad7b85fb3227543e1c677da1f370139d142;hb=eb2b03699f3d50eea9d1a45a48f41e7417297719;hp=58626e75104e612d3db44fecd1a924e2c300be8d;hpb=3da3b415a7c04ba705105ccd8e352579f0aefae6;p=platform%2Fupstream%2Fcryptsetup.git

diff --git a/FAQ b/FAQ
index 58626e7..3e316ad 100644
--- a/FAQ
+++ b/FAQ
@@ -49,6 +49,15 @@ A. Contributors
   installers after a complete backup of all LUKS containers has been
   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
   used in deriving the master key. It is used in decrypting a master
   key that is randomly selected on header creation. This means that