From owner-freebsd-current@FreeBSD.ORG Wed Apr 30 08:19:54 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A500037B401 for ; Wed, 30 Apr 2003 08:19:54 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F059043FCB for ; Wed, 30 Apr 2003 08:19:53 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h3UFK09S019853; Wed, 30 Apr 2003 11:20:00 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 30 Apr 2003 11:19:59 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Lucky Green In-Reply-To: <004b01c30eb9$21a75960$6601a8c0@VAIO650> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: GBDE encrypted hard drive HOW-TO now available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 15:19:54 -0000 On Tue, 29 Apr 2003, Lucky Green wrote: > I wrote a new section for the FreeBSD Handbook with step-by-step > instructions for adding gbde-based hard drive encryption to a system. I > just submitted the SGML source using send-pr today. > > Until such time that the gbde section will be added to the Handbook by > the Doc Team, this gbde HOW-TO will be available at > http://www.cypherpunks.to/gbde.html > > Something that I didn't mentioned in the document, since in the long run > it will become less of an issue, is that I would highly recommend > running -CURRENT, not 5.0-RELEASE, when using gbde. Lucky, Thanks for this great submission. I've gone ahead and committed it to the handbook (will take a few hours to start popping up on web sites); the only change I had to make was that the $FreeBSD$ tag in the sample template lasting caused CVS to get unhappy; I've worked around it by stuffing a in it to disrupt CVS's detection of the tag. I'm not sure what the best approach to solving that problem is -- keeping the tag in the template will help keep the documentation in sync. I'm sure there's a better solution, and perhaps a doc committer can pick up that detail for me :-). Thanks again, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories