DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] valid passphrase not accepted
Date: Wed, 27 Oct 2010 18:23:01 +0200	[thread overview]
Message-ID: <20101027162301.GA11949@fancy-poultry.org> (raw)
In-Reply-To: <AANLkTimFXw1C1mt0vO2Me_qWS8dd+mPe2Y6dmN2S8-uw@mail.gmail.com>

On 27.10.2010, Rick Moritz wrote: 

> Considering the amount of traffic on the list regarding issues like this,
> maybe future versions of dm-crypt should issue an annoying warning when
> creating LUKS-format mapped devices, about how a backup of the header is
> STRONGLY recommended

No, it's not. Read the FAQ, especially item nr.2 and the answer
from Clemens:

http://www.saout.de/tikiwiki/tiki-index.php?page=LUKSFaq

  parent reply	other threads:[~2010-10-27 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 12:15 [dm-crypt] valid passphrase not accepted ts0
2010-10-27 14:01 ` Arno Wagner
2010-10-27 14:39 ` Heinz Diehl
2010-10-27 15:56   ` Arno Wagner
2010-10-27 16:07     ` Rick Moritz
2010-10-27 16:16       ` Arno Wagner
2010-10-27 16:23       ` Heinz Diehl [this message]
2010-10-27 18:57         ` 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=20101027162301.GA11949@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --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