From: John Gilmore <jgilmore@glycou.com>
To: reiserfs-list@namesys.com
Subject: Encryption/Compression and meta data (like file names)
Date: Mon, 13 Mar 2006 13:41:11 -0700 [thread overview]
Message-ID: <200603131341.11327.jgilmore@glycou.com> (raw)
I seem to recall several people saying that the compression/encryption plugins
will only encrypt items, and not the filesystems metadata. And then saying
that this might be useless for their purposes, because being able to see the
filename might be enough for the attacker.
However, I don't think that is correct. The only thing visible to an attacker
would be the tree structure, not the item, which contains the directory
information including the filenames.
So at most an attacker would be able to browse the tree structure, and see the
keys used and the size of the item pointed to. If this is true, selection of
a good hash should entirely prevent the giving information away problem,
leaving only useless key->size->location data for an attacker.
Is my understanding correct?
next reply other threads:[~2006-03-13 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 20:41 John Gilmore [this message]
2006-03-14 6:29 ` Encryption/Compression and meta data (like file names) Hans Reiser
2006-03-14 13:56 ` Edward Shishkin
2006-03-15 7:22 ` Hans Reiser
2006-03-16 12:21 ` Edward Shishkin
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=200603131341.11327.jgilmore@glycou.com \
--to=jgilmore@glycou.com \
--cc=reiserfs-list@namesys.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 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.