All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Size of LUKS header and how to overwrite
Date: Wed, 10 Feb 2016 20:13:50 +0000	[thread overview]
Message-ID: <20160210201350.GR12867@yeono.kjorling.se> (raw)
In-Reply-To: <56BB989F.5090805@whgl.uni-frankfurt.de>

On 10 Feb 2016 21:07 +0100, from sven@whgl.uni-frankfurt.de (Sven Eschenberg):
> Yes, it will overwrite the header and potential free space after the
> header up to the first sector of encrypted data.
> 
> Does this seem so weird?

No, but given the somewhat roundabout way this was described in the
FAQ at least last I looked, this seems like a much easier way to
describe it...

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
                 “People who think they know everything really annoy
                 those of us who know we don’t.” (Bjarne Stroustrup)

  reply	other threads:[~2016-02-10 20:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 22:02 [dm-crypt] Size of LUKS header and how to overwrite Rypervenche
2016-02-09  1:11 ` Arno Wagner
2016-02-09 21:28   ` Rypervenche
2016-02-09 23:28     ` Arno Wagner
2016-02-10 19:13       ` Subscriptions
2016-02-10 19:21         ` Arno Wagner
2016-02-10 19:41           ` Subscriptions
2016-02-10 20:02           ` Michael Kjörling
2016-02-10 20:07             ` Sven Eschenberg
2016-02-10 20:13               ` Michael Kjörling [this message]
2016-02-10 20:29                 ` Sven Eschenberg
2016-02-10 21:50                   ` Arno Wagner
2016-02-10 22:07                     ` 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=20160210201350.GR12867@yeono.kjorling.se \
    --to=michael@kjorling.se \
    --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 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.