public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Christoph Anton Mitterer <calestyo@scientia.org>
Cc: Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: docs: add warning for btrfs checksum features
Date: Sat, 22 Nov 2025 00:52:00 +0000	[thread overview]
Message-ID: <20251122005200.GC3300186@google.com> (raw)
In-Reply-To: <5493c0684cc1014614ae156e9b8888d52857d2bf.camel@scientia.org>

On Sat, Nov 22, 2025 at 12:55:18AM +0100, Christoph Anton Mitterer wrote:
> On Fri, 2025-11-21 at 17:14 +1030, Qu Wenruo wrote:
> > 
> > Adding linux-crypto list for more feedback.
> 
> It would be good if any of them could confirm or reject:
> 
> - Whether a filesystem that uses full checksumming (data + meta-data)
> and that is encrypted with dm-crypt,... is effectively integrity
> protected like it would be with an AEAD.

No, encrypting checksummed data using an unauthenticated encryption mode
isn't equivalent to an AEAD.

- Eric

  reply	other threads:[~2025-11-22  0:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21  5:03 [PATCH] btrfs-progs: docs: add warning for btrfs checksum features Qu Wenruo
2025-11-21  5:17 ` Christoph Anton Mitterer
2025-11-21  5:24   ` Qu Wenruo
2025-11-21  6:02     ` Christoph Anton Mitterer
2025-11-21  6:44       ` Qu Wenruo
2025-11-21 23:55         ` Christoph Anton Mitterer
2025-11-22  0:52           ` Eric Biggers [this message]
2025-11-22 14:36         ` Neal Gompa

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=20251122005200.GC3300186@google.com \
    --to=ebiggers@kernel.org \
    --cc=calestyo@scientia.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox