All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Why is it necessary to "wipe" an authenticated luks2 device when creating it?
Date: Thu, 26 Sep 2019 11:36:24 +0200	[thread overview]
Message-ID: <cd6b3fc3d6b50fd004ad46c1e9d1ae3b3f11f433.camel@scientia.net> (raw)
In-Reply-To: <83ff6ae8-0ac3-a2d3-a982-750862018d7c@gmail.com>

On Thu, 2019-09-26 at 09:41 +0200, Milan Broz wrote:
> Initial wipe recalculates integrity tags - so you can read the device
> afterward.

Maybe it shouldn't be called "wipe" (which people often relate to
secure deletion methods) but "initialise"? :-)

Cheers,
Chris

  reply	other threads:[~2019-09-26  9:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 19:40 [dm-crypt] Why is it necessary to "wipe" an authenticated luks2 device when creating it? .. ink ..
2019-09-26  7:41 ` Milan Broz
2019-09-26  9:36   ` Christoph Anton Mitterer [this message]
2019-09-26 13:38   ` Robert Nichols
2019-09-26 14:29     ` Ondrej Kozina
2019-09-26 21:27       ` Robert Nichols
2019-09-26 22:20         ` Arno Wagner
2019-09-27  8:52         ` Milan Broz
2019-09-26 14:23   ` 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=cd6b3fc3d6b50fd004ad46c1e9d1ae3b3f11f433.camel@scientia.net \
    --to=calestyo@scientia.net \
    --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.