From: Quentin Lefebvre <qlefebvre_pro@yahoo.com>
To: "U.Mutlu" <for-gmane@mutluit.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] plain: opening with a wrong password
Date: Wed, 04 Feb 2015 14:02:42 +0100 [thread overview]
Message-ID: <54D21872.2030406@yahoo.com> (raw)
In-Reply-To: <mat3ic$ql0$1@ger.gmane.org>
Hi,
Le 04/02/2015 13:33, U.Mutlu a écrit :
> 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
cryptsetup create/open command is indeed successful, but mounting your
partition will fail (because the filesystem is not detected).
So you have few chance to accidentally damage a filesystem, even in
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
next prev parent reply other threads:[~2015-02-04 13:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 12:33 [dm-crypt] plain: opening with a wrong password U.Mutlu
2015-02-04 13:02 ` Quentin Lefebvre [this message]
2015-02-04 13:30 ` U.Mutlu
2015-02-05 11:54 ` Arno Wagner
2015-02-05 13:53 ` U.Mutlu
2015-02-05 14:04 ` U.Mutlu
2015-02-05 23:51 ` Arno Wagner
2015-02-06 14:01 ` dennis
2015-02-06 14:19 ` Michael
2015-02-06 14:47 ` U.Mutlu
2015-02-06 18:27 ` Arno Wagner
2015-02-07 17:27 ` dennis
2015-02-07 18:03 ` Heinz Diehl
2015-02-07 23:16 ` Matthias Schniedermeyer
2015-02-08 8:19 ` Heinz Diehl
2015-02-08 9:23 ` Arno Wagner
2015-02-08 9:55 ` Milan Broz
2015-02-08 10:09 ` U.Mutlu
2015-02-08 10:33 ` Milan Broz
2015-02-09 3:13 ` Arno Wagner
2015-02-08 3:07 ` Arno Wagner
2015-02-08 2:59 ` Arno Wagner
2015-02-06 14:04 ` U.Mutlu
2015-02-06 18:20 ` Arno Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54D21872.2030406@yahoo.com \
--to=qlefebvre_pro@yahoo.com \
--cc=dm-crypt@saout.de \
--cc=for-gmane@mutluit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.