From: Pavel Machek <pavel@ucw.cz>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Mark Borgerding <mark@borgerding.net>,
Michael A Halcrow <mahalcro@us.ibm.com>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Encrypted Filesystem
Date: Fri, 30 Jan 2004 18:01:08 +0100 [thread overview]
Message-ID: <20040130170108.GA625@elf.ucw.cz> (raw)
In-Reply-To: <1075151094.809.11.camel@teapot.felipe-alfaro.com>
Hi!
> > Have you given any thought to journalling? fscking? Can directory
> > contents be encrypted? If so, what does the dir look like to others
> > (e.g. backup utils)
> >
> > Per-file signatures will severely affect random access performance.
> > Changing 1 byte in a 1 GB file would require the whole thing to be reread.
>
> What about calculating signatures on a per-block basis instead?
Hmm, having md5's in indirect blocks would be very nice for detecting
cable problems ;-). That's usefull even without encryption.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-01-30 17:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 17:46 Encrypted Filesystem Michael A Halcrow
2004-01-26 19:06 ` Mark Borgerding
2004-01-26 21:04 ` Felipe Alfaro Solana
2004-01-30 17:01 ` Pavel Machek [this message]
2004-01-27 0:06 ` jw schultz
2004-01-27 0:43 ` Adam Sampson
2004-01-27 1:42 ` Andy Isaacson
2004-01-27 22:01 ` Jan Harkes
2004-01-27 22:16 ` Jean-Luc Cooke
2004-01-28 13:50 ` Userspace filesystems (WAS: Encrypted Filesystem) Miklos Szeredi
2004-01-30 17:06 ` Pavel Machek
2004-02-02 9:42 ` Miklos Szeredi
2004-02-02 15:19 ` Pavel Machek
2004-02-02 15:36 ` Nikita Danilov
[not found] <16405.24299.945548.174085@laputa.namesys.com>
2004-01-26 19:02 ` Encrypted Filesystem Hans Reiser
2004-01-27 18:56 ` Edward Shishkin
2004-01-27 21:25 ` Michael Halcrow
2004-01-27 21:51 ` Hans Reiser
[not found] <OFA97B290B.67DE842E-ON87256E27.0061728C-86256E27.0061BB0E@us.ibm.com.suse.lists.linux.kernel>
2004-01-27 16:13 ` Andi Kleen
2004-01-27 18:17 ` Jari Ruusu
2004-01-27 18:44 ` Andi Kleen
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=20040130170108.GA625@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahalcro@us.ibm.com \
--cc=mark@borgerding.net \
/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.