From: Florian Weimer <fweimer@bfk.de>
To: "Gregory Maxwell" <gmaxwell@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Checksum and transform layering
Date: Thu, 06 Nov 2008 17:31:53 +0100 [thread overview]
Message-ID: <82ej1oiznq.fsf@mid.bfk.de> (raw)
In-Reply-To: <e692861c0811052234h704c938es20b562123aa4fe9b@mail.gmail.com> (Gregory Maxwell's message of "Thu, 6 Nov 2008 01:34:55 -0500")
* Gregory Maxwell:
> I noticed in the compression support that the checksum is over the
> uncompressed data.
>
> While this has the advantages that the checksum does not have to be
> changed as transformations are changed and the system might catch
> errors in the compression layer, this design decision will be
> problematic if/when encryption is supported: Plaintext checksums
> would leak substantial amounts of information about the content of
> files.
Would this be an issue if metadata (including file names) were
encrypted as well?
--=20
=46lorian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstra=DFe 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-06 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 6:34 Checksum and transform layering Gregory Maxwell
2008-11-06 12:15 ` Claudio Martins
2008-11-06 17:49 ` Tracy Reed
2008-11-06 16:31 ` Florian Weimer [this message]
2008-11-06 16:42 ` Gregory Maxwell
[not found] ` <1225982445.15281.15.camel@think.oraclecorp.com>
2008-11-06 14:58 ` Gregory Maxwell
2008-11-06 15:27 ` Xavier Nicollet
2008-11-06 15:43 ` Gregory Maxwell
2008-12-09 0:23 ` Chris Mason
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=82ej1oiznq.fsf@mid.bfk.de \
--to=fweimer@bfk.de \
--cc=gmaxwell@gmail.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