dm-crypt.saout.de archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Milan Broz <gmazyland@gmail.com>
Cc: Nikolay Kichukov <hijacker@oldum.net>,
	Chris Murphy <lists@colorremedies.com>,
	dm-crypt@saout.de
Subject: Re: [dm-crypt] luks2 and discard/trim not working
Date: Sat, 9 May 2020 19:41:09 -0600	[thread overview]
Message-ID: <CAJCQCtQ8_+o57bqv0z89biTG6OHMyqwQc2EXffm11JrH3utHkw@mail.gmail.com> (raw)
In-Reply-To: <69e220d1-d9b3-3e96-1b7a-8d400d6aed5a@gmail.com>

On Sat, May 9, 2020 at 2:11 PM Milan Broz <gmazyland@gmail.com> wrote:
>
> On 09/05/2020 21:41, Nikolay Kichukov wrote:
> >
> > Does mine use an internal hash?
>
> No, internal hash is used for non-cryptographic integrity
> protection (IOW when you use only integritysetup).

Ahh OK, nice, I had it exactly 180 degrees wrong.

> Authenticated encryption for LUKS2 is an experimental feature,
> I hope one day we will have something better on filesystem layer.

Authenticated Btrfs using hmac:sha256 checksumming is expected to be
merged pending review (in-progress). And keyed blake2 also looks
possible. No native encryption yet though, but it works fine on top of
dm-crypt.
https://lwn.net/Articles/818842/

One of many technical explanations of what is covered.
https://lore.kernel.org/linux-btrfs/SN4PR0401MB3598198E5FB728B68B39A1589BA60@SN4PR0401MB3598.namprd04.prod.outlook.com/


-- 
Chris Murphy

  reply	other threads:[~2020-05-10  1:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 14:25 [dm-crypt] luks2 and discard/trim not working Nikolay Kichukov
2020-05-09 15:45 ` Chris Murphy
2020-05-09 19:41   ` Nikolay Kichukov
2020-05-09 20:11     ` Milan Broz
2020-05-10  1:41       ` Chris Murphy [this message]
2020-05-09 20:23     ` Chris Murphy
2020-05-09 21:35       ` Nikolay Kichukov
2020-05-09 22:01         ` Milan Broz
  -- strict thread matches above, loose matches on Subject: below --
2020-05-08 21:41 Nikolay Kichukov

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=CAJCQCtQ8_+o57bqv0z89biTG6OHMyqwQc2EXffm11JrH3utHkw@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@gmail.com \
    --cc=hijacker@oldum.net \
    /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;
as well as URLs for NNTP newsgroup(s).