From owner-freebsd-geom@FreeBSD.ORG Mon Jan 14 12:12:11 2008 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D1A116A41A for ; Mon, 14 Jan 2008 12:12:11 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id DE01E13C4FB for ; Mon, 14 Jan 2008 12:12:10 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7c0c.q.ppp-pool.de [89.53.124.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 7F69812883F for ; Mon, 14 Jan 2008 13:12:01 +0100 (CET) Received: from cesar.sz.vwsoft.com (unknown [192.168.16.33]) by mail.vtec.ipme.de (Postfix) with ESMTP id 985E03F442; Mon, 14 Jan 2008 13:11:57 +0100 (CET) Message-ID: <478B5F8A.7090408@vwsoft.com> Date: Mon, 14 Jan 2008 13:11:38 +0000 From: Volker User-Agent: Thunderbird 2.0.0.9 (X11/20080113) MIME-Version: 1.0 To: RW References: <478A93BF.4070404@vwsoft.com> <20080114011412.33a91fac@gumby.homeunix.com.> In-Reply-To: <20080114011412.33a91fac@gumby.homeunix.com.> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1200917518.3217@PlA0+9754E/TrBVLe87iCw X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: freebsd-geom@freebsd.org Subject: Re: Re: how-to: encryption + journaling (geli + gjournal) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jan 2008 12:12:11 -0000 On 12/23/-58 19:59, RW wrote: > On Sun, 13 Jan 2008 23:42:07 +0100 > Volker wrote: > >> For the archives (as I haven't found a nice how-to on this topic): >> >> A short how-to to get geli + gjournal running smoothly (the lazy way, >> depending mostly on OS infrastructure, no script hacking needed). >> >> - set up your geli provider: >> geli load >> geli init /dev/ad0s1d # check geli(8) for this >> geli attach /dev/ad0s1d >> dd if=/dev/random of=/dev/ad0s1d.eli bs=1m # (use higher values bs=... >> for faster operation) > > It would probably be faster to fill /dev/ad0s1d from /dev/random before > doing the geli init - there's no point in encrypting the random numbers. > It would also ensure that the whole of ad0s1d is pre-filled, and not > just the part accessible as ad0s1d.eli. If you think it doesn't make sense or is a fault, please file a PR as filling the data provider with random data has been taken from the manpage geli(8). Otherwise I'm considering this being a bike shed. If you know it better, I'm wondering why you haven't written a how to in the past?