From: Johannes Thumshirn <jthumshirn@suse.de>
To: Leonid Bloch <lbloch@janustech.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"bo.li.liu@oracle.com" <bo.li.liu@oracle.com>
Subject: Re: Cryptographically verifying a btrfs subvolume
Date: Mon, 8 Apr 2019 15:10:11 +0200 [thread overview]
Message-ID: <20190408131010.GA19386@linux-x5ow.site> (raw)
In-Reply-To: <adac7db8-aed6-9573-ec09-4acd5059801e@janustech.com>
On Mon, Apr 08, 2019 at 11:27:51AM +0000, Leonid Bloch wrote:
> Hi List,
>
> Can you suggest a way of cryptographically verifying the content of a
> btrfs subvolume, besides the naïve approach, of running a cryptographic
> hash function on the output of btrfs send?
>
> Back in 2014, an RFC patch was sent to allow using sha256 instead of
> crc32c for checksumming.
> (https://patchwork.kernel.org/patch/5363311)
> It was not merged. Had it been merged, one could just check the return
> value of btrfs scrub, instead of checksumming the whole btrfs send
> output, correct?
Hi Leonid,
I'm working on this feature currently but unfortunately get distracted with
other things all too often.
Thanks for your patience.
Byte,
Johannes
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-04-08 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 11:27 Cryptographically verifying a btrfs subvolume Leonid Bloch
2019-04-08 12:44 ` Austin S. Hemmelgarn
2019-04-08 13:30 ` Leonid Bloch
2019-04-08 14:22 ` Austin S. Hemmelgarn
2019-04-08 13:10 ` Johannes Thumshirn [this message]
2019-04-08 13:49 ` Leonid Bloch
2019-04-08 13:55 ` Johannes Thumshirn
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=20190408131010.GA19386@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=bo.li.liu@oracle.com \
--cc=lbloch@janustech.com \
--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;
as well as URLs for NNTP newsgroup(s).