All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Hualing Yu <hualing.yu@jci.com>, "dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] 10 M Luks2 header size?
Date: Tue, 29 Oct 2019 14:07:43 +0100	[thread overview]
Message-ID: <4fd9084a-e78d-6c16-edb7-2dec936023dc@gmail.com> (raw)
In-Reply-To: <CH2P132MB0187418DB7BD6C9DF85EC5C587660@CH2P132MB0187.NAMP132.PROD.OUTLOOK.COM>

On 28/10/2019 14:50, Hualing Yu wrote:
> I am sorry that I cannot resist asking more questions as your answer
> indicate more opportunities 8-)  If they are very simple to you to
> answer, thank you for just drop a few lines; if not, you can simply
> ignore.
> 
> 1.      You said “…if you have no extra user JSON data stored there”.
> Can we use that area to store additional user data?  How?

You can create custom token type and import directly JSON through cryptsetup
token import command. There is just mandatory type object, otherwise it can be
arbitrary valid JSON.

(I plan to write some article about it but I promised this months ago ... :-)
 
> 2.      To check if a LUKS is in good condition, can we just use
> isLuks command?  Does this cmd trigger some internal sanitary
> checking?

Hm, in theory yes (it calls functions that will do autorecovery),
so side effect is that it validates JSON areas.

But note that any LUKS load will recover invalid JSON area if there
is one area valid (it requires access to cryptsetup locks directory and
of course write access rights to the image/device).

IOW it should "autorepair". If not possible, commands starts to fail
as there is no LUKS2 header.

Milan

  reply	other threads:[~2019-10-29 13:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18 19:24 [dm-crypt] 10 M Luks2 header size? Hualing Yu
2019-10-19  7:07 ` Milan Broz
2019-10-19 18:47   ` Hualing Yu
2019-10-19 19:59     ` Hualing Yu
2019-10-20 10:07       ` Milan Broz
2019-10-21 16:13         ` Hualing Yu
2019-10-27 13:15           ` Hualing Yu
2019-10-27 18:33             ` Arno Wagner
2019-10-28 10:36             ` Milan Broz
2019-10-28 13:50               ` Hualing Yu
2019-10-29 13:07                 ` Milan Broz [this message]
2019-10-29 15:03                   ` Hualing Yu
2019-11-03  3:33                     ` Hualing Yu
2019-11-04 10:33                       ` Ondrej Kozina
2019-11-04 14:59                         ` Hualing Yu
  -- strict thread matches above, loose matches on Subject: below --
2019-10-18 19:04 Hualing Yu

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=4fd9084a-e78d-6c16-edb7-2dec936023dc@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=hualing.yu@jci.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.