Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265178AbUAZVFH (ORCPT ); Mon, 26 Jan 2004 16:05:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265193AbUAZVFG (ORCPT ); Mon, 26 Jan 2004 16:05:06 -0500 Received: from 153.Red-213-4-13.pooles.rima-tde.net ([213.4.13.153]:13832 "EHLO kerberos.felipe-alfaro.com") by vger.kernel.org with ESMTP id S265178AbUAZVFD (ORCPT ); Mon, 26 Jan 2004 16:05:03 -0500 Subject: Re: Encrypted Filesystem From: Felipe Alfaro Solana To: Mark Borgerding Cc: Michael A Halcrow , Linux Kernel Mailinglist In-Reply-To: <40156546.1050809@borgerding.net> References: <40156546.1050809@borgerding.net> Content-Type: text/plain Message-Id: <1075151094.809.11.camel@teapot.felipe-alfaro.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-8) Date: Mon, 26 Jan 2004 22:04:55 +0100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 678 Lines: 16 On Mon, 2004-01-26 at 20:06, Mark Borgerding wrote: > 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? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/