From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from nm10-vm3.bullet.mail.ir2.yahoo.com (nm10-vm3.bullet.mail.ir2.yahoo.com [212.82.96.155]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Wed, 4 Feb 2015 14:02:39 +0100 (CET) Message-ID: <54D21872.2030406@yahoo.com> Date: Wed, 04 Feb 2015 14:02:42 +0100 From: Quentin Lefebvre MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format="flowed" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] plain: opening with a wrong password List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "U.Mutlu" , dm-crypt@saout.de Hi, Le 04/02/2015 13:33, U.Mutlu a =E9crit : > Hi, > what happens if an encrypted filesystem (plain, no LUKS) > next time is opened accidently with a wrong password, > and new data written to it? Will the filesystem then become > damaged/unusable? What typically happens when you use a wrong password is that the=20 cryptsetup create/open command is indeed successful, but mounting your=20 partition will fail (because the filesystem is not detected). So you have few chance to accidentally damage a filesystem, even in=20 plain mode. > I didn't try this out, but I know the create/open command accepts > any password for an already existing encrypted filesystem > since no metadata is stored with such a "plain" volume, right? Right, but this does not mean that data will look meaningful. Best, Quentin