DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "U.Mutlu" <for-gmane@mutluit.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] plain: opening with a wrong password
Date: Wed, 04 Feb 2015 13:33:15 +0100	[thread overview]
Message-ID: <mat3ic$ql0$1@ger.gmane.org> (raw)

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?

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?

             reply	other threads:[~2015-02-04 12:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 12:33 U.Mutlu [this message]
2015-02-04 13:02 ` [dm-crypt] plain: opening with a wrong password Quentin Lefebvre
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='mat3ic$ql0$1@ger.gmane.org' \
    --to=for-gmane@mutluit.com \
    --cc=dm-crypt@saout.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox