From owner-freebsd-geom@FreeBSD.ORG Sun Jun 9 20:12:56 2013 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D52384AE for ; Sun, 9 Jun 2013 20:12:56 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 9FFFA1F7C for ; Sun, 9 Jun 2013 20:12:56 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 1BBC4EA5; Sun, 9 Jun 2013 22:08:34 +0200 (CEST) Date: Sun, 9 Jun 2013 22:12:57 +0200 From: Pawel Jakub Dawidek To: Greg Rivers Subject: Re: geli external header (metadata) Message-ID: <20130609201257.GC2468@garage.freebsd.pl> References: <51B31D42.2010801@gmail.com> <20130609182457.GB2468@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qtZFehHsKgwS5rPz" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Andrew Romero , freebsd-geom@freebsd.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jun 2013 20:12:56 -0000 --qtZFehHsKgwS5rPz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 09, 2013 at 02:51:12PM -0500, Greg Rivers wrote: > On Sun, 9 Jun 2013, Pawel Jakub Dawidek wrote: >=20 > > On Sat, Jun 08, 2013 at 03:02:10PM +0300, Andrew Romero wrote: > > > Hi all > > > I made a patch to support of external header (metadata) on GEOM ELI (= geli) > > >=20 > > > System: FreeBSD 9-STABLE r250964 i386 > > >=20 > > > geli patch - http://pastebin.com/UGpnMN19 > > > regresion patch - http://pastebin.com/hJVkTpJZ > >=20 > > I don't mean to discourage you, but every additional complexity comes a= t=20 > > risk and it case of GELI this is security risk. What is missing in your= =20 > > work is explanation how it that useful for the users? How do you use it= ?=20 > > First I need to understand and be convinced that this functionality is= =20 > > generally useful and thus is worth additional complexity and risk. > > >=20 > I can't speak for Mr Romero, but I imagine what he's after is plausible= =20 > deniability. The GELI metadata on a volume unambiguously declares it to= =20 > be encrypted data. >=20 > Properly implemented, I think this could be a worthwhile enhancement for= =20 > certain applications or circumstances where one may not wish to invite=20 > further scrutiny. That was my first guest too, but in that case I'd much prefer to have this implemented without the need of storing metadata outside. I even started implementing it some time ago, but run out of time before it was done and dropped it. To ensure plausible deniability using proposed change one has to store metadata on removable device (like USB stick) and always remember to remove it once GELI provider is attached. This requirement can be avoided and avoiding it would significantly extend number of potential users. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://mobter.com --qtZFehHsKgwS5rPz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlG04ckACgkQForvXbEpPzQa3ACeJcsNTDhnqwui7dNcxUgZkUIf tiMAn38Ie9A9W+fEoFEkVxQCs0VAdCBr =T5KK -----END PGP SIGNATURE----- --qtZFehHsKgwS5rPz--