public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: docs: add warning for btrfs checksum features
Date: Fri, 21 Nov 2025 15:54:26 +1030	[thread overview]
Message-ID: <bc5249ba-9c39-42b1-903d-e50375a433d2@suse.com> (raw)
In-Reply-To: <9523838F-B99E-4CC5-8434-B34B105FD08B@scientia.org>



在 2025/11/21 15:47, Christoph Anton Mitterer 写道:
> 
> 
> On November 21, 2025 6:03:05 AM GMT+01:00, Qu Wenruo <wqu@suse.com> wrote:
>> The checksum of btrfs, no matter the algorithm utilized, can not provide
>> any guarantee that the metadata/data is not modified by a malicious
>> attacker.
> 
> Is that even the case when the wohle btrfs itself is encrypted, like in dm-crypt (without AEAD or verity, but only a normal cipher like aes-xts-plain64)?
> Wouldn't an attacker then neet to know how he can forge the right encrypted checksum?

In that case the attacker won't even know it's a btrfs or not.

Thanks,
Qu

> 
> Cheers,
> Chris


  reply	other threads:[~2025-11-21  5:24 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 [this message]
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
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=bc5249ba-9c39-42b1-903d-e50375a433d2@suse.com \
    --to=wqu@suse.com \
    --cc=calestyo@scientia.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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