From: Claudio Martins <ctpm@ist.utl.pt>
To: linux-btrfs@vger.kernel.org
Subject: Re: Checksum and transform layering
Date: Thu, 6 Nov 2008 12:15:12 +0000 [thread overview]
Message-ID: <200811061215.12486.ctpm@ist.utl.pt> (raw)
In-Reply-To: <e692861c0811052234h704c938es20b562123aa4fe9b@mail.gmail.com>
On Thursday 06 November 2008, Gregory Maxwell wrote:
>
> 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. The system could be switched to a keyed cryptographic hash,
Indeed. The most obvious (and quite trivial) attack one can do is buil=
d a=20
huge database of checksums for known files or chunks of files.
AFAIK this has already been done by law enforcement/security agencies =
to=20
detect "illegal" files, so it's definitely an issue that would affect a=
ny=20
future encryption code implemented in btrfs.
Regards
Cl=C3=A1udio
--
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 12:15 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 [this message]
2008-11-06 17:49 ` Tracy Reed
2008-11-06 16:31 ` Florian Weimer
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=200811061215.12486.ctpm@ist.utl.pt \
--to=ctpm@ist.utl.pt \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.