Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262848AbUA3RVr (ORCPT ); Fri, 30 Jan 2004 12:21:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262888AbUA3RVr (ORCPT ); Fri, 30 Jan 2004 12:21:47 -0500 Received: from gprs116-76.eurotel.cz ([160.218.116.76]:27265 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S262848AbUA3RVo (ORCPT ); Fri, 30 Jan 2004 12:21:44 -0500 Date: Fri, 30 Jan 2004 18:01:08 +0100 From: Pavel Machek To: Felipe Alfaro Solana Cc: Mark Borgerding , Michael A Halcrow , Linux Kernel Mailinglist Subject: Re: Encrypted Filesystem Message-ID: <20040130170108.GA625@elf.ucw.cz> References: <40156546.1050809@borgerding.net> <1075151094.809.11.camel@teapot.felipe-alfaro.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1075151094.809.11.camel@teapot.felipe-alfaro.com> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 879 Lines: 22 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?] - 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/